Message113692
| Author | belopolsky |
|---|---|
| Recipients | belopolsky, jdwhitley, mark.dickinson |
| Date | 2010-08-12.17:36:13 |
| SpamBayes Score | 2.3642754e-07 |
| Marked as misclassified | No |
| Message-id | <1281634582.37.0.565866814061.issue9574@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I did some experimentation and found some inconsistency between int and complex:
>>> int('\xA11')
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
UnicodeDecodeError: 'utf8' codec can't decode byte 0xa1 in position 0: invalid start byte
but
>>> complex('\xA11')
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ValueError: complex() arg is a malformed string
The int behavior is probably a bug that should be reported separately. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010-08-12 17:36:22 | belopolsky | set | recipients: + belopolsky, mark.dickinson, jdwhitley |
| 2010-08-12 17:36:22 | belopolsky | set | messageid: <1281634582.37.0.565866814061.issue9574@psf.upfronthosting.co.za> |
| 2010-08-12 17:36:14 | belopolsky | link | issue9574 messages |
| 2010-08-12 17:36:14 | belopolsky | create | |