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 | alexandre.vassalotti |
|---|---|
| Recipients | alexandre.vassalotti |
| Date | 2008年01月27日.06:26:39 |
| SpamBayes Score | 0.02727493 |
| Marked as misclassified | No |
| Message-id | <1201415203.65.0.272410099804.issue1944@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I was wandering whether the pointer returned by PyUnicode_AsString needs to be freed after usage (It turned it doesn't since the result is cached). However, I found out that there isn't any documentation on docs.python.org about the PyUnicode_AsString and PyUnicode_AsStringAndSize functions. Although, both are documented in the public unicodeobject.h header. I notice that the documentation for several other unicode functions is missing. Quickly, I see: PyUnicode_Resize PyUnicode_InternImmortal PyUnicode_GetDefaultEncoding PyUnicode_SetDefaultEncoding PyUnicode_BuildEncodingMap PyUnicode_FromFormatV PyUnicode_*UTF7* PyUnicode_AsEncodedObject PyUnicode_FromOrdinal PyUnicode_DecodeFSDefault PyUnicode_DecodeFSDefaultAndSize It would probably be a good idea to polish up the documentation for PyUnicode as much as possible for Python 3000, since extension developers will certainly need to refer to it a lot during the transition from 2.x. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年01月27日 06:26:44 | alexandre.vassalotti | set | spambayes_score: 0.0272749 -> 0.02727493 recipients: + alexandre.vassalotti |
| 2008年01月27日 06:26:43 | alexandre.vassalotti | set | spambayes_score: 0.0272749 -> 0.0272749 messageid: <1201415203.65.0.272410099804.issue1944@psf.upfronthosting.co.za> |
| 2008年01月27日 06:26:41 | alexandre.vassalotti | link | issue1944 messages |
| 2008年01月27日 06:26:40 | alexandre.vassalotti | create | |