Message203489
| Author |
ncoghlan |
| Recipients |
Arfrever, eric.snow, georg.brandl, ncoghlan, serhiy.storchaka, vstinner |
| Date |
2013年11月20日.15:03:34 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CADiSq7fgOEvbBUpEpSwZk8_QuzTauX1QmHjY2QsUOqpDM2zMug@mail.gmail.com> |
| In-reply-to |
<1384957023.12.0.109975533677.issue19518@psf.upfronthosting.co.za> |
| Content |
Hmm, reading more of those and I think Serhiy is definitely right -
Object is the wrong suffix. Unicode isn't right either, since the main
problem is that ambiguity around *which* parameter is a Python Unicode
object. The API names that end in *StringObject or *FileObject don't
give the right idea at all.
The shortest accurate suffix I can come up with at the moment is the
verbose "WithUnicodeFilename":
PyParser_ParseStringObject vs
PyParser_ParseStringWithUnicodeFilename
Other possibilities:
PyParser_ParseStringUnicode # Huh?
PyParser_ParseStringDecodedFilename # Slight fib on Windows, but
mostly accurate
PyParser_ParseStringAnyFilename
Inserting an underscore before the suffix is another option (although
I don't think it much matters either way). |
|