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.22:14:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1517177672.5.0.467229070634.issue32690@psf.upfronthosting.co.za>
In-reply-to
Content
> If you guys think the old code is better in some way, feel free to revert the backport :-)

Hey, it's Guido's code, it must be good :)

My only concern is that this seems to be more of an issue of unspecified behavior rather than a bug and, as such, our general policy is that the status quo wins as far as changing behavior in a maintenance release.  I don't have a really strong feeling one way or another myself; I'm just trying to play devil's advocate on behalf of the user community.  Let's see if anyone else can make a case one way or another.
History
Date User Action Args
2018-01-28 22:14:32ned.deilysetrecipients: + ned.deily, gvanrossum, rhettinger, ncoghlan, njs, dabeaz, yselivanov
2018-01-28 22:14:32ned.deilysetmessageid: <1517177672.5.0.467229070634.issue32690@psf.upfronthosting.co.za>
2018-01-28 22:14:32ned.deilylinkissue32690 messages
2018-01-28 22:14:32ned.deilycreate