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 r.david.murray
Recipients berker.peksag, brett.cannon, larry, matrixise, ncoghlan, nedbat, python-dev, r.david.murray, untitaker, yselivanov
Date 2015-10-26.13:38:52
SpamBayes Score 0.0
Marked as misclassified Yes
Message-id <1445866733.02.0.0765107032078.issue20438@psf.upfronthosting.co.za>
In-reply-to
Content
The thing is, we've adopted a policy that if something exists in python2.7 we shouldn't delete it in python3 until after 2.7 is officially out of maintenance (at the earliest), in order to facilitate single-source porting to python3.  That policy was adopted relatively recently, after the deprecation warning mentioning 3.6 was added in this issue, as I recall it.
History
Date User Action Args
2016-01-17 01:27:53orsenthilsetspambayes_score: -1.0 -> 0.0
2015-10-26 13:38:53r.david.murraysetrecipients: + r.david.murray, brett.cannon, ncoghlan, larry, nedbat, python-dev, berker.peksag, yselivanov, matrixise, untitaker
2015-10-26 13:38:53r.david.murraysetmessageid: <1445866733.02.0.0765107032078.issue20438@psf.upfronthosting.co.za>
2015-10-26 13:38:53r.david.murraylinkissue20438 messages
2015-10-26 13:38:52r.david.murraycreate