Message 107600 - 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.

In-reply-to
Author	vstinner
Recipients	lemburg, loewis, vstinner
Date	2010年06月11日.23:00:09
SpamBayes Score	0.01105683
Marked as misclassified	No
Message-id	<1276297212.27.0.561445333922.issue8949@psf.upfronthosting.co.za>

Content
I patched readline (r81918) and locale (r81914) modules to use PyUnicode_FSConverter(). They don't use "z" format anymore to parse a filename. I checked last functions using "z" format (not "z#" or "z", only "z") and I think that it's ok ("z" can be patched to reject bytes). You can get the full list using: grep -n 'PyArg_Parse[^(]([^"]"[^";:]z[^#]' /.c -- About the difference between s/z and s/s#/z/z#: I don't understand why they are different, but I think that it's too late to change that. Too much functions (and third party modules?) suppose that s/s#/z*/z# supports buffer compatible objects.

Content

I patched readline (r81918) and locale (r81914) modules to use PyUnicode_FSConverter(). They don't use "z" format anymore to parse a filename.
I checked last functions using "z" format (not "z#" or "z*", only "z") and I think that it's ok ("z" can be patched to reject bytes). You can get the full list using:
grep -n 'PyArg_Parse[^(]*([^"]*"[^";:]*z[^#*]' */*.c
--
About the difference between s/z and s*/s#/z*/z#: I don't understand why they are different, but I think that it's too late to change that. Too much functions (and third party modules?) suppose that s*/s#/z*/z# supports buffer compatible objects.

History
Date	User	Action	Args
2010年06月11日 23:00:12	vstinner	set	recipients: + vstinner, lemburg, loewis
2010年06月11日 23:00:12	vstinner	set	messageid: <1276297212.27.0.561445333922.issue8949@psf.upfronthosting.co.za>
2010年06月11日 23:00:10	vstinner	link	issue8949 messages
2010年06月11日 23:00:10	vstinner	create

homepage