Message89927
| Author |
christoph |
| Recipients |
christoph, georg.brandl, mark, tim.peters |
| Date |
2009年06月30日.15:03:18 |
| SpamBayes Score |
3.0528424e-10 |
| Marked as misclassified |
No |
| Message-id |
<1246374200.3.0.696775501321.issue3955@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
This problem seems more severe as the appended test case shows.
That gives me:
Expected:
u'ī'
Got:
u'\u012b'
Both literals are the same.
Unicode literals in doc strings are not treated as other escaped
characters:
>>> repr(r'\n')
"'\\\\n'"
>>> repr('\n')
"'\\n'"
but:
>>> repr(ur'\u012b')
"u'\\u012b'"
>>> repr(u'\u012b')
"u'\\u012b'"
So there is no work around in the docstring's reference itself.
I file this here, even though the problems are not strictly equal. I do
believe though that there is or should be a common solution to these
issues. Both results need to be interpreted on a more abstract scale. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2009年06月30日 15:03:20 | christoph | set | recipients:
+ christoph, tim.peters, georg.brandl, mark |
| 2009年06月30日 15:03:20 | christoph | set | messageid: <1246374200.3.0.696775501321.issue3955@psf.upfronthosting.co.za> |
| 2009年06月30日 15:03:19 | christoph | link | issue3955 messages |
| 2009年06月30日 15:03:18 | christoph | create |
|