[issue28138] Windows _sys.path file should allow import site

2017-03-31 Thread Donald Stufft
Changes by Donald Stufft : -- pull_requests: +893 ___ Python tracker ___ ___

[issue28138] Windows _sys.path file should allow import site

2016-09-17 Thread Steve Dower
Changes by Steve Dower : -- resolution: -> fixed stage: needs patch -> resolved status: open -> closed ___ Python tracker ___

[issue28138] Windows _sys.path file should allow import site

2016-09-17 Thread Roundup Robot
Roundup Robot added the comment: New changeset 7b47c98f24da by Steve Dower in branch '3.6': Issue #28137: Renames Windows path file to ._pth https://hg.python.org/cpython/rev/7b47c98f24da -- nosy: +python-dev ___ Python tracker

[issue28138] Windows _sys.path file should allow import site

2016-09-15 Thread Steve Dower
Steve Dower added the comment: On issue28137 I agreed with the proposal to rename to EXENAME.pth, but rather than supporting all of .pth file's syntax we would abort the process on anything we don't like. Specifically, we'd allow relative paths, absolute paths, blank lines, comments, and

[issue28138] Windows _sys.path file should allow import site

2016-09-15 Thread Wolfgang Langner
Wolfgang Langner added the comment: But this is nearly the same as a *.pth file. Using the same logic and extension then does not confuse more users. Why not doing the same as with a .pth file? Using something like a _sys.pth file if it is there it will be used for path handling. In all cases

[issue28138] Windows _sys.path file should allow import site

2016-09-13 Thread Steve Dower
New submission from Steve Dower: Windows's _sys.path file (being renamed from sys.path in b1) currently disable the initial "import site; site.main()" call. However, there are legitimate cases where you may want to opt-in to this while still controlling the search paths. We should support