➜

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 brett.cannon
Recipients berker.peksag, brett.cannon, florin.papa, pitrou, r.david.murray
Date 2015-09-01.17:16:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1441127799.18.0.77421168213.issue24934@psf.upfronthosting.co.za>
In-reply-to
Content 
I would still rather wait until Django 1.9.0 is officially released else we are benchmarking alpha code which doesn't seem worth it. With Python 3.6.0 not due out until about 15 months after 1.9.0 comes out I think going 3 months without a Django benchmark for 3.6 is acceptable.
History
Date User Action Args
2015-09-01 17:16:39brett.cannonsetrecipients: + brett.cannon, pitrou, r.david.murray, berker.peksag, florin.papa
2015-09-01 17:16:39brett.cannonsetmessageid: <1441127799.18.0.77421168213.issue24934@psf.upfronthosting.co.za>
2015-09-01 17:16:39brett.cannonlinkissue24934 messages
2015-09-01 17:16:39brett.cannoncreate