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 eric.araujo
Recipients Prashanth.Raghu, bob.ippolito, docs@python, eric.araujo, ezio.melotti, r.david.murray, rhettinger
Date 2011-05-13.15:27:03
SpamBayes Score 3.57367e-05
Marked as misclassified No
Message-id <1305300424.25.0.967159151913.issue11964@psf.upfronthosting.co.za>
In-reply-to
Content
It turns out that only one documentation block talks about the new indent behavior.  It was easy to add a versionchanged directive to that, but I think a complete patch would fix all mentions of the indent argument, after checking that all of encode/dump/dumps/Encoder.whatnot support the new behavior (there is a test for dumps only, I checked that dump works too but not the other ones).
History
Date User Action Args
2011-05-13 15:27:04eric.araujosetrecipients: + eric.araujo, rhettinger, bob.ippolito, ezio.melotti, r.david.murray, docs@python, Prashanth.Raghu
2011-05-13 15:27:04eric.araujosetmessageid: <1305300424.25.0.967159151913.issue11964@psf.upfronthosting.co.za>
2011-05-13 15:27:03eric.araujolinkissue11964 messages
2011-05-13 15:27:03eric.araujocreate