Re: Mac OS X Installation Problem
wrote: ... > But this begs the question, how do we upgrade our Python installations if OS X > needs a certain version? Do we leave the pre-installed version alone and run a > second Python installation? I suppose that the various package installers > would know how to do that, right? Yes, and yes. The state for MacOSX Python is a bit in transition right now (what with the introduction of intel Macs, and therefore the need for Universal binaries), but soon, I hope, it will settle to a point where downloading and installing Python (2.4.2 or better) without disturbing Apple's own Python (2.3.5) will be trivial -- stay tuned! Alex -- http://mail.python.org/mailman/listinfo/python-list
Re: Mac OS X Installation Problem
wrote: > [EMAIL PROTECTED] (Alex Martelli) wrote: > > >Edit a ~/.bashrc file to add /usr/local/bin to your PATH. > > Hi Alex, > > Easier said than done for a non-unix expert. Correct me if I am wrong. Bash > looks at the contents of the PATH variable to decided which directories it > should scan when parsing a command. If I type "Python -v", it will look in all > of those directories for a file called "Python" and then execute it, passing > it the -v parameter. Right? Right. The uppercase P in 'Python' would make the search fail in just about every Unix in the world, but MacOSX is the exception (at least if you're using its default HFS+ filesystem) and lets you be sloppy with capitalization. > I've been googling around for about an hour now, and I can't find any > instructions on how to create or edit a .bashrc file. I tried to make one of That depends on what text editor you favour. Me, I love gvim, but most people hate it. MacOSX comes with TextEdit, scarce but really not controversial, and emacs, the One Editor to Rule Them All. TextWrangler and subethaedit, both freely downloadable, are among the most beloved free editors; BBEdit, I've heard, is widely considered the best for-pay one. What text editor you choose to edit text files on MacOSX, be it a free or for-pay one, is hardly a suitable subject for the comp.lang.python newsgroup, of course -- I apologize for the OT. > Is there a web page somewhere that explains this? There are many, basically one for each text editor program you may choose. TextEdit has a predilection for saving .RTF (a marked-up text format Microsoft Word also likes) rather than plain text files, so I would not recommend it in general, by the way -- too easy to err. BTW, like in every other Unix, if you're having problem saving to a textfile named .foobar, save to foobar without the initial dot, then from a Terminal prompt, mv foobar .foobar -- that's all it takes. There are innumerable books and webpages about MacOSX and other Unix variants, mostly pretty orthogonal to any Python issues or interests but nevertheless interesting. O'Reilly's "Learning Unix for Mac OS X Tiger", for example, is really quite a good text. Alex -- http://mail.python.org/mailman/listinfo/python-list
Re: Mac OS X Installation Problem
Kevin Walzer <[EMAIL PROTECTED]> wrote: >It's not considered a good idea to trash Apple system files. It's likely >that system tools that depend on Python (CoreImage scripting comes to >mind) are now broken and the only way to fix this is to reinstall the OS. Thanks for the heads up. I thought that Apple had included Python as a convenience for its customers. I didn't realize it was actually being used by OS X. My Mac seems to be behaving OK, so maybe I don't use any of the Python parts, but I will keep that in mind in case it goes haywire in the future. But this begs the question, how do we upgrade our Python installations if OS X needs a certain version? Do we leave the pre-installed version alone and run a second Python installation? I suppose that the various package installers would know how to do that, right? Thanks, Matt -- http://mail.python.org/mailman/listinfo/python-list
Re: Mac OS X Installation Problem
[EMAIL PROTECTED] (Alex Martelli) wrote: >Edit a ~/.bashrc file to add /usr/local/bin to your PATH. Hi Alex, Easier said than done for a non-unix expert. Correct me if I am wrong. Bash looks at the contents of the PATH variable to decided which directories it should scan when parsing a command. If I type "Python -v", it will look in all of those directories for a file called "Python" and then execute it, passing it the -v parameter. Right? I've been googling around for about an hour now, and I can't find any instructions on how to create or edit a .bashrc file. I tried to make one of my own using bash and nano, but got stuck with the save command. It looks like I am supposed to use the "M-O" command to save it in Mac format, but I have no idea how to type that. A search of the nano docs for "M-O" didn't turn up anything either. I also tried to make a .bashrc file on my Windows box and copy it to my Mac, but the Finder gave me an error message saying that I'm not allowed to make files that begin with a dot. Is there a web page somewhere that explains this? Thanks, Matt -- http://mail.python.org/mailman/listinfo/python-list
Re: Mac OS X Installation Problem
Matt Trivisonno wrote: > > My Tiger system had Python v2.3.5 on it and I threw the files in the trash It's not considered a good idea to trash Apple system files. It's likely that system tools that depend on Python (CoreImage scripting comes to mind) are now broken and the only way to fix this is to reinstall the OS. -- Kevin Walzer iReveal: File Search Tool http://www.wordtech-software.com -- http://mail.python.org/mailman/listinfo/python-list
Re: Mac OS X Installation Problem
wrote: > Hi Everybody, > > 1) Does OS X have a thing like the Add/Remove Programs control panel on > Windows XP? Nope. You install stuff by running "packages" (installers) or dragging .app "files" to Applications, uninstall it normally by dragging them to Trash. > My Tiger system had Python v2.3.5 on it and I threw the files in the trash and Very unwise move -- now your fax functionality (which Apple implemented using their own special system build of Python 2.3.5) is unlikely to work, for example. > installed v2.4.1, which is working fine as far as I can tell. However, when I > type python at the command line, I get "command not found" so, > > 2) How do I get OS X to recognize python at the command line? Edit a ~/.bashrc file to add /usr/local/bin to your PATH. Alex -- http://mail.python.org/mailman/listinfo/python-list
Mac OS X Installation Problem
Hi Everybody, 1) Does OS X have a thing like the Add/Remove Programs control panel on Windows XP? My Tiger system had Python v2.3.5 on it and I threw the files in the trash and installed v2.4.1, which is working fine as far as I can tell. However, when I type python at the command line, I get "command not found" so, 2) How do I get OS X to recognize python at the command line? Thanks, Matt -- http://mail.python.org/mailman/listinfo/python-list
