-
-
Notifications
You must be signed in to change notification settings - Fork 20
Closed
Description
Currently, .pth
files are only honored on Python 3.2 and earlier due to this workaround.
Python 3.3 and later are excused because the only perceived need for .pth
files at the time of the implementation was to support namespace packages, packages which work fine in PEP 420 mode naturally on Python 3.3 and later.
However, I've since learned of other packages such as future-fstrings that install .pth
files to enable behavior on startup.
This leads me to believe rwt
should no longer exclude later Python versions from the .pth
file support... although this increases the impact of the issue that all rwt
invocations will now mask any existing sitecustomize.py
.
Metadata
Metadata
Assignees
Labels
No labels