Skip to content

gh-139287: Improve the definition of Incorrect padding in base64.rst documents #139301

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 4 commits into from
Closed

gh-139287: Improve the definition of Incorrect padding in base64.rst documents #139301

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
576828d
Update base64.rst
LamentXU123 Sep 24, 2025
ddf2e67
Update base64.rst
LamentXU123 Sep 24, 2025
4039192
Fix lint CI
LamentXU123 Sep 24, 2025
3e9df93
change "string" to "payload"
LamentXU123 Sep 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions Doc/library/base64.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,8 +74,11 @@ POST request.
of length 2 which specifies the alternative alphabet used instead of the
``+`` and ``/`` characters.

A :exc:`binascii.Error` exception is raised
if *s* is incorrectly padded.
A :exc:`binascii.Error` exception is raised if *s* contains incorrect padding.
When *validate* is ``False`` (the default), extra padding characters and
discontinuous padding characters (``=`` characters in the middle of the payload)
are silently ignored. When *validate* is ``True``, such incorrect padding
will result in a :exc:`binascii.Error`.

If *validate* is ``False`` (the default), characters that are neither
in the normal base-64 alphabet nor the alternative alphabet are
Expand Down
Loading