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 petri.lehtinen
Recipients Devin Jeanpierre, petri.lehtinen
Date 2011-05-27.07:07:52
SpamBayes Score 5.203948e-07
Marked as misclassified No
Message-id <1306480073.75.0.91611263994.issue12063@psf.upfronthosting.co.za>
In-reply-to
Content
tokenize processes a line at a time, and noticing that an ending triple quote is missing would mean reading the whole file in the worst case. As tokenize seems to work in a generator-like fashion, it's probably not desired to cache all the input to be able to restart from some previous line.

So, I'd go with documenting the behavior.
History
Date User Action Args
2011-05-27 07:07:53petri.lehtinensetrecipients: + petri.lehtinen, Devin Jeanpierre
2011-05-27 07:07:53petri.lehtinensetmessageid: <1306480073.75.0.91611263994.issue12063@psf.upfronthosting.co.za>
2011-05-27 07:07:53petri.lehtinenlinkissue12063 messages
2011-05-27 07:07:52petri.lehtinencreate