RetroSearch Browse

Thu Nov 9 10:27:45 EST 2017 · https://mail.python.org/pipermail/python-dev/2017-November/150427.html

On 11/09/2017 01:49 AM, Greg Ewing wrote:
>> On 8 November 2017 at 19:21, Antoine Pitrou <solipsis at pitrou.net> wrote:
>>> The idea that __main__ scripts should
>>> get special treatment here is entirely gratuitous.
> 
> When I'm writing an app in Python, very often my __main__ is
> just a stub that imports the actual functionality from another
> module to get the benefits of a pyc. So enabling deprecation
> warnings for __main__ only wouldn't result in me seeing any
> more warnings.

IIUC, that would be as expected:  you would see the warnings when running
your test suite exercising that imported code (which should run with all
warnings enabled), but not when running the app.

Seems like a reasonable choice to me.

Tres.
-- 
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2017-November/150427.html below:

[Python-Dev] [python-committers] Enabling depreciation warnings feature code cutoff