Message132354
| Author | lemburg |
|---|---|
| Recipients | docs@python, eric.araujo, ezio.melotti, georg.brandl, lemburg, ncoghlan, r.david.murray |
| Date | 2011-03-27.18:34:09 |
| SpamBayes Score | 1.9051893e-09 |
| Marked as misclassified | No |
| Message-id | <4D8F831E.4040200@egenix.com> |
| In-reply-to | <1301219850.94.0.471533856973.issue11681@psf.upfronthosting.co.za> |
| Content | |
|---|---|
Nick Coghlan wrote: > > Nick Coghlan <ncoghlan@gmail.com> added the comment: > > Even "from __future__ import unicode_literals" doesn't make it do anything. > > Perhaps Christian merged it by mistake in [5341b30b1812]? It looks more like some parts were left out in the merge by accident: The 2.7 code only raises the warning for bytearrays, not for bytes and buffers, whereas 3.2 issues the warning for all bytes and bytearray (but not buffers; which makes sense, since Python 3 no longer has a text buffer interface). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-03-27 18:34:10 | lemburg | set | recipients: + lemburg, georg.brandl, ncoghlan, ezio.melotti, eric.araujo, r.david.murray, docs@python |
| 2011-03-27 18:34:09 | lemburg | link | issue11681 messages |
| 2011-03-27 18:34:09 | lemburg | create | |