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 ezio.melotti
Recipients Rhamphoryncus, amaury.forgeotdarc, belopolsky, doerwalter, eric.smith, ezio.melotti, georg.brandl, lemburg, loewis, pitrou, python-dev, rhettinger, stutzbach, tchrist, vstinner
Date 2011-09-29.20:27:14
SpamBayes Score 0.015693983
Marked as misclassified No
Message-id <1317328034.99.0.648302692973.issue10542@psf.upfronthosting.co.za>
In-reply-to
Content
Py_UNICODE_NEXT has been removed from 3.3 but it's still available and used in 2.7/3.2 (even if it's private).  In order to fix #10521 on 2.7/3.2 the _Py_UNICODE_PUT_NEXT macro attached to this patch is required.
History
Date User Action Args
2011-09-29 20:27:15ezio.melottisetrecipients: + ezio.melotti, lemburg, loewis, doerwalter, georg.brandl, rhettinger, amaury.forgeotdarc, belopolsky, Rhamphoryncus, pitrou, vstinner, eric.smith, stutzbach, python-dev, tchrist
2011-09-29 20:27:14ezio.melottisetmessageid: <1317328034.99.0.648302692973.issue10542@psf.upfronthosting.co.za>
2011-09-29 20:27:14ezio.melottilinkissue10542 messages
2011-09-29 20:27:14ezio.melotticreate