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 ned.deily
Recipients dabeaz, gvanrossum, ncoghlan, ned.deily, njs, rhettinger, yselivanov
Date 2018-01-28.21:37:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content
While I appreciate the desirability of changing the behavior, it does introduce a behavior change in a 3.6.x maintenance release.  I don't have a good feel for the probability that current users or 3-party libraries are depending on the old behavior.  Anyone want to hazard a guess?  If there is a significantly non-zero probability, perhaps this should wait for 3.7.
History
Date User Action Args
2018-01-28 21:37:22ned.deilysetrecipients: + ned.deily, gvanrossum, rhettinger, ncoghlan, njs, dabeaz, yselivanov
2018-01-28 21:37:22ned.deilysetmessageid: <[email protected]>
2018-01-28 21:37:22ned.deilylinkissue32690 messages
2018-01-28 21:37:22ned.deilycreate