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 Valentin Zhao
Recipients Valentin Zhao, Windson Yang, jaraco, paul.moore, steve.dower, tim.golden, zach.ware
Date 2018-11-09.06:42:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAE9EaJbMXd5bUqifX9k=TZhmM3hv7DO_GdG+HJwhV0dcZP2y-w@mail.gmail.com>
In-reply-to <1541254353.59.0.788709270274.issue35131@psf.upfronthosting.co.za>
Content
I am better just waiting you guys fixing that because it is not urgent.
On Sat, Nov 3, 2018 at 10:12 PM Jason R. Coombs <report@bugs.python.org>
wrote:

>
> Jason R. Coombs <jaraco@jaraco.com> added the comment:
>
> 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 (https://pypi.org/project/future-fstrings/). I learned
> about this issue in (https://github.com/jaraco/rwt/issues/29), which is
> why the rwt project adds a `sitecustomize.py` to the target directory that
> ensures .pth files are run. Just FYI.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue35131>
> _______________________________________
>
History
Date User Action Args
2018-11-09 06:42:13Valentin Zhaosetrecipients: + Valentin Zhao, paul.moore, jaraco, tim.golden, zach.ware, steve.dower, Windson Yang
2018-11-09 06:42:13Valentin Zhaolinkissue35131 messages
2018-11-09 06:42:12Valentin Zhaocreate