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 serhiy.storchaka
Recipients barry, gregory.p.smith, jwilk, miss-islington, nascheme, njs, rhettinger, serhiy.storchaka, steven.daprano, terry.reedy, xiang.zhang
Date 2019-01-11.11:52:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
If you are fine with this change Gregory, do you mind to withdraw your request and remove the DO-NOT-MERGE label on GitHub?

As for DeprecationWarning vs SyntaxWarning:

1. It looks as misuse of DeprecationWarning. We do not plan to remove this feature in future. Emitting it will send a false signal to users. And SyntaxWarning was added such kind of warning: syntactically valid code that for sure is an error.

2. Seems there is no differences between DeprecationWarning and SyntaxWarning if they are emitted at compile time. They will be shown by default in all cases, in the main script and in modules.
Date User Action Args
2019-01-11 11:52:26serhiy.storchakasetrecipients: + serhiy.storchaka, barry, nascheme, rhettinger, terry.reedy, gregory.p.smith, jwilk, steven.daprano, njs, xiang.zhang, miss-islington
2019-01-11 11:52:24serhiy.storchakasetmessageid: <>
2019-01-11 11:52:24serhiy.storchakalinkissue34850 messages
2019-01-11 11:52:24serhiy.storchakacreate