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:12:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Also, I would argue that this is an enhancement request and not a bug - that the prior expectation was that the .pth file is encoded in whatever encoding the system expects by default, and that adding support for a standardized encoding for .pth files is a new feature.

As another aside: Valentin, the technique you're using to manage packages is likely to run into issues with certain packages - in particular any packages that rely on their own `.pth` files to invoke behavior, such as future_fstrings ( I learned about this issue in (, which is why the rwt project adds a `` to the target directory that ensures .pth files are run. Just FYI.
Date User Action Args
2018-11-03 14:12:33jaracosetrecipients: + jaraco, paul.moore, tim.golden, zach.ware, steve.dower, Windson Yang, Valentin Zhao
2018-11-03 14:12:33jaracosetmessageid: <>
2018-11-03 14:12:33jaracolinkissue35131 messages
2018-11-03 14:12:33jaracocreate