[python-committers] Deprecation Policy PEP
ncoghlan at gmail.com
Sat Jan 30 03:41:51 EST 2016
On 30 January 2016 at 13:28, Martin Panter <vadmium+py at gmail.com> wrote:
> On 29 January 2016 at 21:59, Serhiy Storchaka <storchaka at gmail.com> wrote:
>> On 29.01.16 21:56, Ezio Melotti wrote:
>>> On Fri, Jan 29, 2016 at 8:00 PM, Serhiy Storchaka <storchaka at gmail.com>
>>>> Some deprecation can be documentation-only.
>>> Do you have examples where this has been done?
>> An attribute of a module. [. . .]
>> Removing some special behavior [. . .]
> Sometimes people want to avoid raising a DeprecationWarning even where
> it is technically possible. For example, the optparse module
> <https://bugs.python.org/issue25521>, which is still widely used in
> other modules. Brett’s load_module() situation also sounds similar.
Another case where this arises is when an API has been deprecated for
pure Python 3 code, but is still needed in single source Python 2/3
Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
More information about the python-committers