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 r.david.murray
Recipients alex, barry, eric.araujo, gvanrossum, ncoghlan, pitrou, r.david.murray
Date 2017-11-08.13:26:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
From the linked email:

> That way ad hoc scripts and the REPL will get warnings by default,
> while zipapps and packages can avoid warnings by keeping their
> simple, and importing a CLI helper function from another
> module. Entry point wrapper scripts will implicitly have the same
> effect for installed packages.

But a lot of non-ad-hoc scripts consist of a single __main__ module, and this will produce warnings in those.  Weren't those kind of scripts one of the motivators for not enabling deprecation warnings by default?  I seem to remember that's where they annoyed me most, but it has been a long time (thankfully).

When we had warnings by default we got lots of complaints.  Since we turned them off and turned them back on in unittest (and other test packages followed suit), we have not had complaints that I remember hearing before this thread, except about them not appearing at the REPL.  Are there real-world (as opposed to theoretical) instances of the current policy causing real problems?
Date User Action Args
2017-11-08 13:26:44r.david.murraysetrecipients: + r.david.murray, gvanrossum, barry, ncoghlan, pitrou, eric.araujo, alex
2017-11-08 13:26:44r.david.murraysetmessageid: <>
2017-11-08 13:26:44r.david.murraylinkissue31975 messages
2017-11-08 13:26:44r.david.murraycreate