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 jaraco
Recipients Valentin Zhao, Windson Yang, jaraco, paul.moore, steve.dower, tim.golden, zach.ware
Date 2018-11-03.14:05:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1541253900.43.0.788709270274.issue35131@psf.upfronthosting.co.za>
In-reply-to
Content
I'm only aware of one tool that writes .pth files, and that's setuptools, and it always writes ASCII (assuming package names are ASCII), so any encoding handling should be fine there.

> We could add a handler for UnicodeDecodeError that falls back on utf-8?

Yes, reasonable, but maybe we should consider instead _preferring_ UTF-8 and fall back to default encodings. That would be my preference.
History
Date User Action Args
2018-11-03 14:05:00jaracosetrecipients: + jaraco, paul.moore, tim.golden, zach.ware, steve.dower, Windson Yang, Valentin Zhao
2018-11-03 14:05:00jaracosetmessageid: <1541253900.43.0.788709270274.issue35131@psf.upfronthosting.co.za>
2018-11-03 14:05:00jaracolinkissue35131 messages
2018-11-03 14:05:00jaracocreate