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 loewis
Recipients alex, benjamin.peterson, dstufft, georg.brandl, lambacck, larry, loewis, ned.deily, python-dev, steve.dower, zach.ware
Date 2014-06-06.11:22:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1402053771.08.0.2406076999.issue21671@psf.upfronthosting.co.za>
In-reply-to
Content
I'm unsure. I'd rather stick to the established policy. If there are reasons to change the policy, I'd like to know what they are and what a new policy should look like, instead of making a singular exception from the policy.

For the record, the reason *for* the policy is that it reduces maintenance burden; I'm unsure whether I still have the environment to build Python 3.2, for example.
History
Date User Action Args
2014-06-06 11:22:51loewissetrecipients: + loewis, georg.brandl, larry, benjamin.peterson, ned.deily, lambacck, alex, python-dev, zach.ware, steve.dower, dstufft
2014-06-06 11:22:51loewissetmessageid: <1402053771.08.0.2406076999.issue21671@psf.upfronthosting.co.za>
2014-06-06 11:22:51loewislinkissue21671 messages
2014-06-06 11:22:50loewiscreate