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 dino.viehland
Recipients dino.viehland
Date 2019-05-21.21:01:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1558472495.26.0.119384648617.issue37001@roundup.psfhosted.org>
In-reply-to
Content
symtable is useful when combined with compile() to AST to understand what the names bind to.  But symtable.symtable() doesn't accept a bytes object, while compile does.  Ultimately these feed down to the same API, and could easily lead to subtle mismatches due to encodings. 

The workaround seems to be to use the tokenize.detect_encoding to discover the encoding and then do the encoding from Python, but this seems wasteful.
History
Date User Action Args
2019-05-21 21:01:35dino.viehlandsetrecipients: + dino.viehland
2019-05-21 21:01:35dino.viehlandsetmessageid: <1558472495.26.0.119384648617.issue37001@roundup.psfhosted.org>
2019-05-21 21:01:35dino.viehlandlinkissue37001 messages
2019-05-21 21:01:35dino.viehlandcreate