<div dir="ltr"><br><br><div class="gmail_quote">On Tue, Sep 2, 2008 at 1:38 PM, Amaury Forgeot d'Arc <span dir="ltr"><<a href="mailto:amauryfa@gmail.com">amauryfa@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br>
<div class="Ih2E3d"><br>
Giampaolo Rodola' wrote:<br>
> Hi,<br>
> I've always found it strange that Python Windows installers never<br>
> managed to add the python executable to the PATH environment variable.</div></blockquote><div><br>+1<br><br>
At this point, as far as I know, changing the PATH variable manually
under Windows is the most convenient <br>way to be able to work correctly with Python.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
> Are there plans for adding such a thing?<br>
<br>
</div>I don't think so.<br>
See the discussion of <a href="http://bugs.python.org/issue3561" target="_blank">http://bugs.python.org/issue3561</a><br>
</blockquote><div><br>I don't understand why it is closed/wontfix though.<br><br>In the tracker Martin said:<br>"""<br><pre>The very end-user related aspects of it need to be discussed<br>on python-dev (perhaps taking a poll whether this is desirable, whether<br>
it should be optional, and if so, what the default should be)</pre>"""<br><br>So I'd like to give my opinion here about this, because I've had this problem while writing a book about Python.<br>(a book that is for people that use Python on *any* platform bien sūr, not only Linux)<br>
<br>For me, the Windows installer does not work properly: I cannot open a console and run Python right away.<br>I don't care about the technical complexity of setting it up automatically : I simply think it is wrong not to be able to run <br>
the interpreter the same way on Windows and Linux/Mac OS.<br><br>You may end up having to deal with it in your documentation. Look at all the documentation out there. For instance Pylons:<br><br><a href="http://wiki.pylonshq.com/display/pylonsdocs/Installing+Pylons">http://wiki.pylonshq.com/display/pylonsdocs/Installing+Pylons</a><br>
<br>
-> there's a small note on that page "All windows users also should read the section <a class="reference" href="http://wiki.pylonshq.com/display/pylonsdocs/Windows+Notes">Post install tweaks for Windows</a> after installation"<br>
-> windows users need to go there : <a href="http://wiki.pylonshq.com/display/pylonsdocs/Windows+Notes">http://wiki.pylonshq.com/display/pylonsdocs/Windows+Notes</a><br><br>Why do we have to take care about that ? Python installers should.<br>
<br>A lot of package out there create console scripts (buildout, sphinx, rst2html, etc..) that lives in /Script, and are not reachable <br>in Windows unless the PATH is changed.<br><br>So I don't see any good reason (besides the technical complexity) to add it to the Windows installer. <br>
Or at least do something that will let us run Python and third-party scripts from the command line even if it is done with PATH. <br><br>So I would love to see this ticket open again; I personnaly would be in favor of an automatic change of PATH by the installer.<br>
<br>My 2 cents<br>Tarek<br><br></div></div>-- <br>Tarek Ziadé | Association AfPy | <a href="http://www.afpy.org">www.afpy.org</a><br>Blog FR | <a href="http://programmation-python.org">http://programmation-python.org</a><br>
Blog EN | <a href="http://tarekziade.wordpress.com/">http://tarekziade.wordpress.com/</a><br>
</div>