Message 149577 - Python tracker

Message149577

Author	Jim.Jewett
Recipients	Jim.Jewett, docs@python, loewis, vstinner
Date	2011-12-15.21:20:47
SpamBayes Score	5.2980367e-09
Marked as misclassified	No
Message-id	<1323984048.71.0.813354803625.issue13604@psf.upfronthosting.co.za>
In-reply-to

Content
Updated to resolve most of Victor's concerns, but this meant enough changes that I'm not sure it quite counts as editorial only. A few questions that I couldn't answer: (1) Upon string creation, do we want to promise to discard the UTF-8 and wstr, so that the caller can memory manage? (2) PyUnicode_AS_DATA(), Py_UNICODE_strncpy, Py_UNICODE_strncmp seemed to be there in the code I was looking at. (3) I can't justify the born-deprecated function "PyUnicode_AsUnicodeAndSize". Perhaps rename it with a leading underscore? Though I'm not sure it is really needed at all. (4) I tried to reword the "for compatibility" ... "redundant" part ... but I'm not sure I resolved it.

Content

Updated to resolve most of Victor's concerns, but this meant enough changes that I'm not sure it quite counts as editorial only.

A few questions that I couldn't answer:

(1)  Upon string creation, do we want to *promise* to discard the UTF-8 and wstr, so that the caller can memory manage?

(2)  PyUnicode_AS_DATA(), Py_UNICODE_strncpy, Py_UNICODE_strncmp seemed to be there in the code I was looking at.

(3)  I can't justify the born-deprecated function "PyUnicode_AsUnicodeAndSize".  Perhaps rename it with a leading underscore?  Though I'm not sure it is really needed at all.

(4)  I tried to reword the "for compatibility" ... "redundant" part ... but I'm not sure I resolved it.

History
Date	User	Action	Args
2011-12-15 21:20:48	Jim.Jewett	set	recipients: + Jim.Jewett, loewis, vstinner, docs@python
2011-12-15 21:20:48	Jim.Jewett	set	messageid: <1323984048.71.0.813354803625.issue13604@psf.upfronthosting.co.za>
2011-12-15 21:20:48	Jim.Jewett	link	issue13604 messages
2011-12-15 21:20:47	Jim.Jewett	create