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 pitrou
Recipients alex, barry, eric.araujo, gvanrossum, ncoghlan, pitrou, r.david.murray
Date 2017-11-09.08:58:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> And I'll repeat: I'm entirely happy with the "revert the change for __main__ only" compromise, since it covers all the cases I care about.

And that's what I'm unhappy with.  We should either revert the change for all code, or not revert it at all.

Such a middle ground is just a wishy-washy decision-by-committee compromise.  It will satisfy almost nobody (neither the people who don't want to see deprecation warnings, nor the ones who don't to miss them), is more complicated to remember, and will most certainly have to be revisited in a couple of years.
Date User Action Args
2017-11-09 08:58:20pitrousetrecipients: + pitrou, gvanrossum, barry, ncoghlan, eric.araujo, alex, r.david.murray
2017-11-09 08:58:20pitrousetmessageid: <>
2017-11-09 08:58:20pitroulinkissue31975 messages
2017-11-09 08:58:20pitroucreate