Author belopolsky
Recipients belopolsky, terry.reedy, tjollans
Date 2010-06-19.03:34:13
SpamBayes Score 0.0021392
Marked as misclassified No
Message-id <1276918455.16.0.836029814452.issue8990@psf.upfronthosting.co.za>
In-reply-to
Content
> This, to me, implies that .fromstring should accept bytearray (though
> probably not general buffer objects). In 2.x, I understand .fromstring 
> to initialize an array from machine bytes read into a string, but not
> .fromunicode. This is *not* a text method, and the result may vary for 2
> and 4-byte unicode builds. So I can see that 3.x needs
>  .fromstring(bytes) but not .fromunicode(string).


No, fromunicode is still needed.  It is used to fill type 'u' array with unicode wide characters.  In 3.x unicode type was renamed to str and str to bytes, so fromunicode should become fromstring (or maybe fromstr to avoid confusion) and fromstring should become frombytes.
History
Date User Action Args
2010-06-19 03:34:15belopolskysetrecipients: + belopolsky, terry.reedy, tjollans
2010-06-19 03:34:15belopolskysetmessageid: <1276918455.16.0.836029814452.issue8990@psf.upfronthosting.co.za>
2010-06-19 03:34:13belopolskylinkissue8990 messages
2010-06-19 03:34:13belopolskycreate