Message136377
> that patch looks good
I tested it with non-ASCII interface names: it works as expected with
ASCII and UTF-8 locales. It's the first time that I see the "O&" format
for Py_BuildValue(), I didn't know this one. The patch looks good.
@neologix: You can commit it into Python 3.3. Tell me if you need
help ;-)
> though I do wish we had a function similar to
> PyObject_AsStringEncodedFSDefault() so that the ParseTuple call wasn't
> needed for this relatively common operation when interfacing with
> system library calls that deal in C strings.
PyUnicode_FSConverter and PyUnicode_FSDecoder don't fit your needs?
What you would be the purpose of PyObject_AsStringEncodedFSDefault()?
What is its prototype? |
|
Date |
User |
Action |
Args |
2011-05-20 14:38:49 | vstinner | set | recipients:
+ vstinner, gregory.p.smith, pitrou, christian.heimes, OG7, meiermic, nadeem.vawda, neologix, santoso.wijaya, python-dev |
2011-05-20 14:38:49 | vstinner | link | issue1746656 messages |
2011-05-20 14:38:49 | vstinner | create | |
|