Message143426
| Author |
eric.araujo |
| Recipients |
akuchling, belopolsky, eric.araujo, ezio.melotti, georg.brandl, rhettinger, terry.reedy |
| Date |
2011年09月02日.17:58:08 |
| SpamBayes Score |
1.3581185e-06 |
| Marked as misclassified |
No |
| Message-id |
<1314986288.86.0.429796961047.issue4153@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Ah, I see: you’re equating "string" with "text string" or "character string", whereas I read "bytes string" as "finite sequence of bytes". With this definition, there *are* two string types in Python 3, it’s just that they’re much more divorced than in 2.x.
> they should think that there are only Unicode strings
I’d say they should think that text processing should only happen with the one type dedicated to text, i.e. str.
> they can be converted to a bytes object (or simply to 'bytes')
Okay, +0 to use only "bytes object" (or "bytes" when it sounds better). |
|