Skip to content
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.

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

gh-92613: Deprecate other uuencode functionality per PEP 594 & document as such #92758

Open
wants to merge 12 commits into
base: main
Choose a base branch
from

Conversation

CAM-Gerlach
Copy link
Member

@CAM-Gerlach CAM-Gerlach commented May 13, 2022

Per #92613 , for the following functionality deprecated by PEP 594 (PEP-594) but not formally implemented due to an oversight:

  • Low-level interfaces binascii.a2b_uu and binascii.b2a_uu for decoding and encoding uuencode data
  • The uu_codec binary transform in the codecs module, implementing uuencode as a Python codec
  • Support for decoding non-MIME uuencode payloads with the get_payload() method of the legacy email.message.Message (compat32) API

This PR adds missing:

  • DeprecationWarnings in the Python/C code
  • Warning checks and handling in the tests
  • Deprecation notices in the docs, and
  • A descriptive entry in the What's New for 3.11

Fixes #92613

@CAM-Gerlach
Copy link
Member Author

@CAM-Gerlach CAM-Gerlach commented May 13, 2022

@warsaw , I've tagged you on behalf of the email team for review of this PR's approach to handling the deprecation of uuencode in the legacy email.message.Message compat32 API, and @pablogsal , I've tagged you as release manager for 3.11, to review adding necessary deprecation messages to a couple final uuencode-related items that were explicitly slated by PEP 594 to be deprecated in 3.11 and to be removed in 3.13, and not yet formally documented as such (both per the recommendation of @brettcannon).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.11 awaiting review docs needs backport to 3.11 stdlib
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants