➜

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 larry
Recipients brett.cannon, doko, eric.snow, larry, ncoghlan, ned.deily, petr.viktorin, pitrou, serhiy.storchaka, vaultah
Date 2017-08-09.03:19:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1502248793.61.0.92195390653.issue30876@psf.upfronthosting.co.za>
In-reply-to
Content 
If the change has been checked into the 3.5 branch, it'll go out with 3.5.5.

TBH we should probably stop accepting bug fixes into a branch when it hits rc1 of "last release to accept bugfixes" (e.g. 3.5.4rc1).  There are two or three bugfixes in the 3.5 branch that I cherry-picked around when I made 3.5.4 final.  I'm going to let them simply ship in 3.5.5 (eventually), even though 3.5.5 shouldn't have any "bug fixes".  Maybe we'll be crisper when it comes to 3.6.xrc1 etc.
History
Date User Action Args
2017-08-09 03:19:53larrysetrecipients: + larry, brett.cannon, doko, ncoghlan, pitrou, ned.deily, petr.viktorin, eric.snow, serhiy.storchaka, vaultah
2017-08-09 03:19:53larrysetmessageid: <1502248793.61.0.92195390653.issue30876@psf.upfronthosting.co.za>
2017-08-09 03:19:53larrylinkissue30876 messages
2017-08-09 03:19:53larrycreate