➜

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 loewis, mark.dickinson, pitrou
Date 2010-05-10.20:23:28
SpamBayes Score 0.0017152183
Marked as misclassified No
Message-id <1273523010.72.0.521283637272.issue8677@psf.upfronthosting.co.za>
In-reply-to
Content 
I personally don't think that a transition period would be a useful thing to have, in particular not if it goes like this:
- in version A, require use of PY_SSIZE_T_CLEAN
- in version A+1, make use of PY_SSIZE_T_CLEAN redundant

So I'd rather drop PY_SSIZE_T clean altogether from 3.2, and risk any breakage that this may cause.
History
Date User Action Args
2010-05-10 20:23:30loewissetrecipients: + loewis, mark.dickinson, pitrou
2010-05-10 20:23:30loewissetmessageid: <1273523010.72.0.521283637272.issue8677@psf.upfronthosting.co.za>
2010-05-10 20:23:29loewislinkissue8677 messages
2010-05-10 20:23:28loewiscreate