This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author methane
Recipients ZackerySpytz, jdemeyer, methane, philthompson10
Date 2019-07-19.13:26:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAEfz+Ty5Dz4qaQgFhhxpvVcbB=H1d8cDfzT5fXz5EOKh+0fqrQ@mail.gmail.com>
In-reply-to <577fb6cd41516c19a2b2480560dd068d@riverbankcomputing.com>
Content
2019年7月19日(金) 22:00 Phil Thompson <report@bugs.python.org>:

>
> If I fail to protect against using a feature when it is no longer
> present then it's a bug in my code and it won't compile. Providing a
> deprecation warning gives me some notice that my code needs to be
> changed. That is helpful but not strictly necessary as I will soon find
> out when testing against the new version. There is nothing "dangerous"
> here.
>

You are proposing to change Python, so it's not only your option.  It may
be safe for you, but may be not safe for all authors who creating extension
and share it on PyPI.

If it's only your problem, you can manually suppress the warning, like you
manually enabled missing initializer warning.  No need to add an option to
CPython.

>
History
Date User Action Args
2019-07-19 13:26:04methanesetrecipients: + methane, philthompson10, jdemeyer, ZackerySpytz
2019-07-19 13:26:04methanelinkissue37588 messages
2019-07-19 13:26:03methanecreate