Message 172200 - Python tracker

➜

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	skrah
Recipients	Arfrever, pitrou, r.david.murray, rogerbinns, serhiy.storchaka, skrah, vstinner
Date	2012-10-06.14:34:33
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1349534074.19.0.549417507833.issue16145@psf.upfronthosting.co.za>
In-reply-to

Content
> The PEPs and doc said the C API would remain backwards compatible. Roger: Yes, you don't need to change anything. I was misled by the PyUnicode_AsUnicode() docs, thinking that the responsibility to call PyUnicode_READY() also applies if the generated Unicode Object is passed to the C-API.

> The PEPs and doc said the C API would remain backwards compatible.

Roger: Yes, you don't need to change anything. I was misled by the
PyUnicode_AsUnicode() docs, thinking that the responsibility to call
PyUnicode_READY() also applies if the generated Unicode Object is
passed to the C-API.

History
Date	User	Action	Args
2012-10-06 14:34:34	skrah	set	recipients: + skrah, pitrou, vstinner, rogerbinns, Arfrever, r.david.murray, serhiy.storchaka
2012-10-06 14:34:34	skrah	set	messageid: <1349534074.19.0.549417507833.issue16145@psf.upfronthosting.co.za>
2012-10-06 14:34:34	skrah	link	issue16145 messages
2012-10-06 14:34:33	skrah	create