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 loewis
Recipients benjamin.peterson, loewis, serhiy.storchaka, vstinner
Date 2013-11-07.15:44:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1383839079.21.0.924978731001.issue19519@psf.upfronthosting.co.za>
In-reply-to
Content
tok->enc and tok->encoding should always have the same value, except that tok->enc gets set earlier.

tok->enc is used when parsing from strings, to remember what codec to use. For file based parsing, the codec object created knows what encoding to use; for string-based parsing, tok->enc stores the encoding.

If the code is to be simplified, unifying the cases of string-based parsing and file-based parsing might be a worthwhile goal.
History
Date User Action Args
2013-11-07 15:44:39loewissetrecipients: + loewis, vstinner, benjamin.peterson, serhiy.storchaka
2013-11-07 15:44:39loewissetmessageid: <1383839079.21.0.924978731001.issue19519@psf.upfronthosting.co.za>
2013-11-07 15:44:39loewislinkissue19519 messages
2013-11-07 15:44:38loewiscreate