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 | vstinner |
|---|---|
| Recipients | Anthony Sottile, abartlet, miss-islington, pitrou, serhiy.storchaka, vstinner |
| Date | 2020年03月04日.13:08:41 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1583327321.93.0.0261677802999.issue37330@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
Le mer. 4 mars 2020 à 03:01, Andrew Bartlett <report@bugs.python.org> a écrit : > (...) but that a valid build script that operates correctly on Python 3.8 will no longer, without warning to us, (...) Displaying warnings by default or not is an old debate. I added the "Python Development Mode" (-X dev) to help the situation: https://docs.python.org/dev/library/devmode.html#devmode I just added a very explicit "You should check for DeprecationWarning in your code" section in What's New In Python 3.9: https://docs.python.org/dev/whatsnew/3.9.html#you-should-check-for-deprecationwarning-in-your-code Moreover, DeprecationWarning are now (Python 3.7) displayed *by default* in the __main__ module: https://www.python.org/dev/peps/pep-0565/ |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2020年03月04日 13:08:41 | vstinner | set | recipients: + vstinner, pitrou, serhiy.storchaka, Anthony Sottile, miss-islington, abartlet |
| 2020年03月04日 13:08:41 | vstinner | set | messageid: <1583327321.93.0.0261677802999.issue37330@roundup.psfhosted.org> |
| 2020年03月04日 13:08:41 | vstinner | link | issue37330 messages |
| 2020年03月04日 13:08:41 | vstinner | create | |