This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | bob.ippolito |
|---|---|
| Recipients | bob.ippolito, ezio.melotti, pitrou, rhettinger, serhiy.storchaka |
| Date | 2013年05月10日.18:08:10 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1368209290.44.0.393067752829.issue17906@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
The patch that I wrote for simplejson is here (it differs a bit from serhiy's patch): https://github.com/simplejson/simplejson/commit/35816bfe2d0ddeb5ddcc68239683cbb35b7e3ff2 I discovered another bug along the way in the pure-Python scanstring, int(s, 16) will parse '0xNN' when json expects only strings of the form 'NNNN' to work. I fixed that along with this issue by explicitly checking for x or X. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013年05月10日 18:08:10 | bob.ippolito | set | recipients: + bob.ippolito, rhettinger, pitrou, ezio.melotti, serhiy.storchaka |
| 2013年05月10日 18:08:10 | bob.ippolito | set | messageid: <1368209290.44.0.393067752829.issue17906@psf.upfronthosting.co.za> |
| 2013年05月10日 18:08:10 | bob.ippolito | link | issue17906 messages |
| 2013年05月10日 18:08:10 | bob.ippolito | create | |