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 benjamin.peterson, eli.bendersky, jab, josephgordon, lukasz.langa, ned.deily, serhiy.storchaka
Date 2017-03-10.22:44:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1489185844.23.0.297109810318.issue23894@psf.upfronthosting.co.za>
In-reply-to
Content
Sorry, the announced deadline for bugfixes for 3.6.1 has already passed; at this point, only showstopper problems with 3.6.1rc1 are on the table for the final.  Trivial impact isn't a criterion for post-rc1 changes and there's a good reason for that: we ask everyone in the community to test a release candidate with the expectation that this is the final release.  I don't think it's fair to add more unrelated changes and risk that it will break something and/or cause additional release candidates to be produced.  The original problem has been open for nearly two years now and, while "f" string support adds to the importance of the tokenizer getting updated, this can wait 3 more months for 3.6.2 with a proper review cycle and with tests.
History
Date User Action Args
2017-03-10 22:44:04ned.deilysetrecipients: + ned.deily, benjamin.peterson, eli.bendersky, jab, lukasz.langa, serhiy.storchaka, josephgordon
2017-03-10 22:44:04ned.deilysetmessageid: <1489185844.23.0.297109810318.issue23894@psf.upfronthosting.co.za>
2017-03-10 22:44:04ned.deilylinkissue23894 messages
2017-03-10 22:44:04ned.deilycreate