[issue33710] Deprecate gettext.lgettext()

Karthikeyan Singaravelan added the comment: It seems like the docs have a note that these functions were removed in Python 3.10 but they probably missed the release. Doc : https://docs.python.org/3.10/library/gettext.html#gettext.lgettext -- ___

[issue33710] Deprecate gettext.lgettext()

Braden Groom added the comment: Ah. Thank you -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33710] Deprecate gettext.lgettext()

Serhiy Storchaka added the comment: See PEP 4. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue33710] Deprecate gettext.lgettext()

Serhiy Storchaka added the comment: New changeset fec35c99aa749bb90cb29349bed6b3393907c4c1 by Serhiy Storchaka in branch 'master': bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139)

[issue33710] Deprecate gettext.lgettext()

Braden Groom added the comment: Thanks! I'll check out the linked PR. I've seen a few deprecation issues that I couldn't pick up just because I wasn't clear on the deprecation process. Is this documented anywhere in the development guides? I wasn't able to find it if it exists. Is there any

[issue33710] Deprecate gettext.lgettext()

Karthikeyan Singaravelan added the comment: The deprecation notice is added to the docs and deprecation warnings are raised during usage of the functions. As per the PR some of them are deprecated with 3.8 (master) and will be removed by 3.10. But this depends on the discussion over the

[issue33710] Deprecate gettext.lgettext()

Serhiy Storchaka added the comment: Sometime we starts with deprecating just in the documentation, if it is hard to add deprecation in the code or adding it will break a lot of working code. But this is not the case. lgettext() was inherently broken in Python 3. --

[issue33710] Deprecate gettext.lgettext()

Serhiy Storchaka added the comment: It includes three parts: * Add the code that emits a DeprecationWarning when corresponding functions and arguments are used. It is important to specify the correct stacklevel argument. * Add tests and/or modify existing test for catching or silencing a

[issue33710] Deprecate gettext.lgettext()

Change by Serhiy Storchaka : -- keywords: +patch pull_requests: +9468 stage: -> patch review ___ Python tracker ___ ___

[issue33710] Deprecate gettext.lgettext()

Change by Serhiy Storchaka : -- assignee: -> serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue33710] Deprecate gettext.lgettext()

Braden Groom added the comment: What's the process for deprecating functions? Do we just start by adding a note in the docs? -- ___ Python tracker ___

[issue33710] Deprecate gettext.lgettext()

Change by Braden Groom : -- nosy: +bradengroom ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33710] Deprecate gettext.lgettext()

Barry A. Warsaw added the comment: +1 - I'm actually surprise it's still there. ;) Given that the docs have a big red warning to avoid these in Python 3, let's start the process of removal. Don't forget to also deprecate ldgettext(), lngettext(), and ldngettext()

[issue33710] Deprecate gettext.lgettext()

New submission from Serhiy Storchaka : Using gettext.lgettext() is the one of two right ways of doing translation in Python 2. In Python 2, gettext.gettext() returns a raw 8-bit string as it was written in the translation file. Since different translation files can use different encodings,