| Hence, yet again, a plea for newbies everywhere:
I continue to believe that it really, really shouldn't be necessary for people who want to write programs in Python for the Mac to do all this. Great to learn as much as possible, yes, always -- but to require people, just to get started, to learn about shells and the Terminal, which they may never have dealt with before, even if they have a variety of Mac programming experience, is not to put Python on its best footing.
Charles
On Feb 6, 2006, at 9:26 AM, Louis Pecora wrote: linda.s wrote:
Create the following text file and save it as ".bash_profile" in your home directory. --Larry
# .bash_profile
# Get the aliases and functions if [ -f ~/.bashrc ]; then . ~/.bashrc fi
# User specific environment and startup programs
PATH=/usr/local/bin:/$PATH;export PATH
# End of File
It did not work from the creating of .bash_profile. If I typed "export PATH=/usr/local/bin:$PATH." It worked in the command line but it did not work in the code. _______________________________________________
Did you open a new terminal window after you edited the .bash_profile ? That's when .profile type files are 'run', i.e. only at the start of a terminal session.
-- Cheers,
Lou Pecora
Code 6362 Naval Research Lab Washington, DC 20375 USA Ph: +202-767-6002
_______________________________________________
|
_______________________________________________
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
