[issue459007] Document sys.path on Windows

Change by admin : -- github: None -> 35125 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue459007] Document sys.path on Windows

Georg Brandl added the comment: Thanks for the patch, merged with existing info in using/windows.rst in r85615. -- resolution: -> fixed status: open -> closed ___ Python tracker _

[issue459007] Document sys.path on Windows

MunSic JEONG added the comment: I made patch which move comment from PC/getpathp.c to Doc/using/windows.rst. And did a little editing, reST markup. http://codereview.appspot.com/2211046 -- keywords: +patch Added file: http://bugs.python.org/file18997/comment_move_to_windows_rst.patch

[issue459007] Document sys.path on Windows

Changes by MunSic JEONG : -- nosy: +ruseel ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue459007] Document sys.path on Windows

Éric Araujo added the comment: using/windows.rst seems the best place to add comments from PC/getpathp.c, under the “Finding modules” section. -- ___ Python tracker ___ __

[issue459007] Document sys.path on Windows

Mark Hammond added the comment: FWIW, I think the rules are fairly well explained in the comments in PC/getpathp.c; last time I looked at this, the only thing I couldn't really decide was where in the official docs these comments should be put (after reformatting and minor rewording etc) ---

[issue459007] Document sys.path on Windows

Éric Araujo added the comment: s/spring/sprint/ :) -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue459007] Document sys.path on Windows

Éric Araujo added the comment: Out of date seems an inaccurate status to me. Bugs may take weeks to years to be fixed. This one is tagged easy (according to amk in msg73954), so perhaps someone will have a go at it during a Bug Day or a spring, or one of the docs people will just do it (e.g.

[issue459007] Document sys.path on Windows

Mark Lawrence added the comment: Tim, Brian I've added you to the nosy list as I think you could assist. Unless I get a response within the next 10 years I will close this as "out of date" -- nosy: +BreamoreBoy, brian.curtin, tim.golden ___ Python

[issue459007] Document sys.path on Windows

Changes by Matthieu Labbé : -- nosy: +matthieu.labbe ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue459007] Document sys.path on Windows

Changes by Catalin Iacob : -- nosy: +catalin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue459007] Document sys.path on Windows

Tal Einat added the comment: Wow, this has been on hold for ages! I know I could have used this information in the past, and several people have asked me about this. Perhaps there should be a place in the documentations which explains how sys.path is populated, with detailed explanations for

[issue459007] Document sys.path on Windows

Changes by Éric Araujo : -- assignee: georg.brandl -> d...@python nosy: +d...@python versions: +Python 3.2 -Python 3.0 ___ Python tracker ___ ___

[issue459007] Document sys.path on Windows

Changes by Georg Brandl : -- assignee: mhammond -> georg.brandl nosy: +georg.brandl priority: high -> normal ___ Python tracker ___ _

[issue459007] Document sys.path on Windows

Changes by R. David Murray : -- keywords: +easy versions: +Python 2.7, Python 3.1 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue459007] Document sys.path on Windows

Changes by Daniel Diniz : -- nosy: +ajaksu2 stage: -> needs patch type: -> behavior versions: +Python 2.6, Python 3.0 ___ Python tracker ___ __

[issue459007] Document sys.path on Windows

A.M. Kuchling <[EMAIL PROTECTED]> added the comment: I think this item doesn't need to be handled by Mark. There's a comment at the top of PC/getpathp.c giving the rules, so it's just a matter of editing the text and adding reST markup. But where in the docs should this material go? using/wi

[issue459007] Document sys.path on Windows

Sean Reifschneider added the comment: This is a high priority item that hasn't been touched in half a decade. Mark: Consider this a reminder if this is still on your agenda to do. If not, shall we just close it? Is there anyone else that could do this? -- nosy: +jafo