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 ezio.melotti
Recipients ezio.melotti, jcea, mjacob, vstinner
Date 2013-02-25.22:32:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1361831555.39.0.823924821511.issue17223@psf.upfronthosting.co.za>
In-reply-to
Content
> If the problem is that PyUnicode_FromUnicode() rejects character
> outside range [U+0000; U+10ffff],

But this used to return two valid characters:
>>> str(array('u', b'asdf'))
"array('u', '獡晤')"

so I think it still should -- unless the operation was already nonsensical and/or there's no way to do the same thing on 3.3+ due to the change introduced by PEP 393.

> it would be better to use the byte string '\xff' * sizeof_PY_UNICODE. 

What for?

> U+66647361 may become valid in a future version of Unicode,

It won't.
History
Date User Action Args
2013-02-25 22:32:35ezio.melottisetrecipients: + ezio.melotti, jcea, vstinner, mjacob
2013-02-25 22:32:35ezio.melottisetmessageid: <1361831555.39.0.823924821511.issue17223@psf.upfronthosting.co.za>
2013-02-25 22:32:35ezio.melottilinkissue17223 messages
2013-02-25 22:32:35ezio.melotticreate