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 Frederick.Ross
Recipients Frederick.Ross, eli.bendersky, eric.araujo, ezio.melotti, pitrou, r.david.murray, rhettinger
Date 2012-05-25.20:06:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1337976398.59.0.770577981372.issue14852@psf.upfronthosting.co.za>
In-reply-to
Content
In the case of files, sure, it's fine. The error gives me the offset, and I can go pull it out and buffer it, and it's fine. Plus XML is strict about having only one document per file.

For streams, none of this is applicable. I can't seek in a streaming network connection. If the parser leaves it in an unusable state, then I lose everything that may follow. It makes Python unusable in certain, not very rare, cases of network programming.

I'll just add that Haskell's Parsec does this right, and should be used as an example.
History
Date User Action Args
2012-05-25 20:06:38Frederick.Rosssetrecipients: + Frederick.Ross, rhettinger, pitrou, ezio.melotti, eric.araujo, r.david.murray, eli.bendersky
2012-05-25 20:06:38Frederick.Rosssetmessageid: <1337976398.59.0.770577981372.issue14852@psf.upfronthosting.co.za>
2012-05-25 20:06:38Frederick.Rosslinkissue14852 messages
2012-05-25 20:06:37Frederick.Rosscreate