➜

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 v+python
Recipients amaury.forgeotdarc, barry, eric.araujo, erob, flox, ggenellina, oopos, pebbe, pitrou, quentel, r.david.murray, tcourbon, tobias, v+python, vstinner
Date 2011-01-12.02:14:46
SpamBayes Score 2.1010783e-06
Marked as misclassified No
Message-id <1294798488.17.0.55897884621.issue4953@psf.upfronthosting.co.za>
In-reply-to
Content 
I notice the version on this issue is Python 3.3, but it affects 3.2 and 3.1 as well.  While I would like to see it fixed for 3.2, perhaps it is too late for that, with rc1 coming up this weekend?

Could at least the non-deprecated parse functions be deprecated in 3.2, so that they could be removed in 3.3?  Or should we continue to support them?
History
Date User Action Args
2011-01-12 02:14:48v+pythonsetrecipients: + v+python, barry, amaury.forgeotdarc, ggenellina, pitrou, vstinner, eric.araujo, r.david.murray, oopos, tcourbon, tobias, flox, pebbe, quentel, erob
2011-01-12 02:14:48v+pythonsetmessageid: <1294798488.17.0.55897884621.issue4953@psf.upfronthosting.co.za>
2011-01-12 02:14:46v+pythonlinkissue4953 messages
2011-01-12 02:14:46v+pythoncreate