Message165835
| Author |
r.david.murray |
| Recipients |
aalien, ezio.melotti, jcea, r.david.murray |
| Date |
2012年07月19日.11:56:17 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1342698978.25.0.694620244187.issue15393@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
IMO this is not a bug, according to the current documentation it is working as designed. raw_decode says it decodes a string that *starts with* a json document.
To my understanding, raw_decode is designed to be used when parsing a stream containing more than just one json document, including possibly non-json text, in which case it makes sense that the calling application would be responsible for (and want to) handle the whitespace around any such document.
I recommend closing this as invalid. If the consensus is otherwise and a change is made, I think it would be an enhancement, not a bug fix. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年07月19日 11:56:18 | r.david.murray | set | recipients:
+ r.david.murray, jcea, ezio.melotti, aalien |
| 2012年07月19日 11:56:18 | r.david.murray | set | messageid: <1342698978.25.0.694620244187.issue15393@psf.upfronthosting.co.za> |
| 2012年07月19日 11:56:17 | r.david.murray | link | issue15393 messages |
| 2012年07月19日 11:56:17 | r.david.murray | create |
|