Message213699
| Author | pitrou |
|---|---|
| Recipients | Arfrever, docs@python, ezio.melotti, ncoghlan, pitrou, sreepriya |
| Date | 2014-03-16.01:54:00 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1394934841.39.0.715073359011.issue17110@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> There was no unicode encode error generated! Is it because the problem
> is fixed?
No, it's not fixed.
First, it seems you are testing with Python 2 (otherwise you would get "b'bytes'", not "bytes"). Python 2 won't have a problem here, since it treats everything as bytestrings.
Second, to evidence the issue you must pass a non-ASCII string. For example:
$ ./python a.py `echo éléphant|iconv -t latin1`
Traceback (most recent call last):
File "a.py", line 4, in <module>
print(sys.argv[1])
UnicodeEncodeError: 'utf-8' codec can't encode character '\udce9' in position 0: surrogates not allowed |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-03-16 01:54:01 | pitrou | set | recipients: + pitrou, ncoghlan, ezio.melotti, Arfrever, docs@python, sreepriya |
| 2014-03-16 01:54:01 | pitrou | set | messageid: <1394934841.39.0.715073359011.issue17110@psf.upfronthosting.co.za> |
| 2014-03-16 01:54:01 | pitrou | link | issue17110 messages |
| 2014-03-16 01:54:00 | pitrou | create | |