On 9/18/06, Ronald Oussoren <[EMAIL PROTECTED]> wrote: > > On Sep 18, 2006, at 10:11 PM, Gerben Wierda wrote: > > > On Sep 18, 2006, at 21:42 , Bob Ippolito wrote: > > > >> On 9/18/06, Christopher Barker <[EMAIL PROTECTED]> wrote: > >>> Gerben Wierda wrote: > >>>>> what shell are you using? > >>>> > >>>> bash (default shell). But my env has not been changed by the > >>> Universal pkg. > >>>> > >>>> hermione-a:~ gerben$ which python > >>>> /usr/bin/python > >>>> > >>>> PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/ > >>> teTeX/bin/i386-apple-darwin-current > >>>> > >>>> > >>>> I also would wonder if that would be something that the > >>> Universal .pkg > >>>> should do. It would mean that I would get a new python when I call > >>>> system utitlities that use Python from the command line (because it > >>>> would have to be inserted at the start of my PATH and that is > >>> generally > >>>> taken as not the right thing to do) > >>> > >>> A) system scripts should have the path to Python hard coded: > >>> > >>> #!/usr/bin/python > >>> > >>> B) The installer is only supposed to alter your login shell PATH, so > >>> anything called by the system won't be effected. > >>> > >>>> But anyway, Universal pkg did not set up my PATH for my command > >>> line shell. > >>> > >>> Curious: > >>> > >>> Ronald and/or Bob: isn't it supposed to have? I know it did mine: > >>> > >> > >> There's three different login scripts that bash can use.. The 2.4.3 > >> postflight script knows how to patch .profile and .bash_profile... > >> but > >> if a .bash_login exists and .bash_profile does not exist then it will > >> create a .profile that is never used. Perhaps that is what happened? > > > > That is exactly what has happened.
That's easy enough to fix for Python 2.5's installer. > > Just a remark. Changing ~/.profile btw is not what I would expect > > from a package like this. You are installing a system-wide tool and > > you are only opening it to the user that has installed it (instead of > > say, changing /etc/profile). Secondly, there is this thing that you > > are doing something that may be forwned upon (PATH entry added at the > > start of the PATH), so at least it would be good to warn the user > > about it with some panel. Easy to do with a different (open source) > > Mac OS X installer (http://www.rna.nl/ii.html ;-) ;-) ;-) There is a warning, as Ronald says. Anyway, this isn't really up for discussion... we've found out over the past 5 years or so that a great many people don't know anything about PATH. The current scheme is much much much much easier than hand-holding people through creating a .profile. The people that know enough about environment variables to have an opinion on whether they want this behavior or not can easily fix it by unchecking it in the installer or removing the additional line from their login script. Also, this is exactly what other tools such as MacPorts and Fink do -- create a user profile for a system-wide tool. If a better solution was available, I'm sure one of the two would be using it. When/if that ever happens (unlikely), we'll surely follow suit at some point. -bob _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
