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 belopolsky
Recipients BreamoreBoy, aconrad, belopolsky, larry, mark.dickinson, python-dev, r.david.murray, tbarbugli, tim.peters, trcarden, vivanov, vstinner
Date 2015-09-07.12:26:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1441628800.31.0.765045460046.issue23517@psf.upfronthosting.co.za>
In-reply-to
Content
Larry> Well, for now I assume it really truly genuinely isn't going in 3.5.0.

This is an unfortunate outcome.

Larry> I suppose we can debate about 3.4.x and 3.5.1 later

It is even more unfortunate that the question of whether this regression is a bug or not is up for debate again.

Victor> The code will be new, I'm not condifent enough to push it immedialty into python 3.5.

I don't understand why any new code is needed to fix a regression.  All you need to do is to revert a few chunks of 1e9cc1a03365 where the regression was introduced.
History
Date User Action Args
2015-09-07 12:26:40belopolskysetrecipients: + belopolsky, tim.peters, mark.dickinson, vstinner, larry, r.david.murray, aconrad, BreamoreBoy, vivanov, python-dev, tbarbugli, trcarden
2015-09-07 12:26:40belopolskysetmessageid: <1441628800.31.0.765045460046.issue23517@psf.upfronthosting.co.za>
2015-09-07 12:26:40belopolskylinkissue23517 messages
2015-09-07 12:26:40belopolskycreate