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 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:20christophsetrecipients: + christoph, tim.peters, georg.brandl, mark
2009-06-30 15:03:20christophsetmessageid: <1246374200.3.0.696775501321.issue3955@psf.upfronthosting.co.za>
2009-06-30 15:03:19christophlinkissue3955 messages
2009-06-30 15:03:18christophcreate