Comments on: So you want to use python on the mac?

By: jnoller

jnoller — Mon, 20 Apr 2009 22:27:44 +0000

Fixed

By: Niklas

Niklas — Mon, 20 Apr 2009 22:19:25 +0000

Hello, thanks for a nice and clean way to run python. However, WORKON_HOME needs to be set before virtualenv_wrapper is sourced, otherwise it won’t have any effect.

By: jnoller

jnoller — Mon, 20 Apr 2009 18:27:44 +0000

Fixed

By: captnswing

captnswing — Sun, 19 Apr 2009 10:54:29 +0000

I think I managed to get a full 64bit python web stack on OS X 10.5.

see here http://blog.captnswing.net/2009/04/19/python-mo...

By: Jason Baker

Jason Baker — Sat, 18 Apr 2009 18:56:00 +0000

Minor correction: OS X comes with Python 2.5.1 by default, not Python 2.5.2.

By: jnoller

jnoller — Mon, 13 Apr 2009 16:25:22 +0000

An additional bootstrap script I have adds in the “common things” — installing them into the central location (e.g. /bin) means that when I call nose, I am calling nose that’s installed against an interpreter I may not be using (e.g., 2.5 vs. 2.6). See also the postmkvirtualenv hook for virtualenvwrapper, which could be used to exec commands, rather than just change settings. I have a script which I run by hand though

By: Doug Latornell

Doug Latornell — Mon, 13 Apr 2009 16:07:15 +0000

I'm curious how you handle your "almost always used" tools in this virtualenv setup? In my case those are things like nose, coverage, ipython, and Sphinx. I saw the add2virtualenv command in virtualenvwrapper and thought, "Cool! I'll just install nose, et al in my default virtualenv and add them to other virtualenvs as necessary." Alas, that doesn't work very well for packages like nose that have entry points in bin/ - the she-bang path has to be edited so that it points to the correct place, or I get import errors.

So, do you install nose in every virtualenv you create, or do you "egregiously modify" your pristine site-packages/, or is there another option I'm missing?

By: jnoller

jnoller — Tue, 07 Apr 2009 17:01:05 +0000

Comment out the “source /Library/Frameworks/Python.framework/Versions/2.6/bin/virtualenvwrapper_bashrc” line and reload everything to exclude the possibility it’s a bug in virtualenv wrapper first

By: Pat

Pat — Tue, 07 Apr 2009 16:25:22 +0000

Hi Jesse!

Hey I am almost home. I can switch between Py 2.5 and 2.6. It seems to work well. However, there seems to be a bit of a snag with the "illegal option". The .bash_profile has been modified as you instructed to reflect the path as outlined:

>>export PATH=/Library/Frameworks/Python.framework/Versions/2.6/bin:/usr/local/bin:$PATH
source /Library/Frameworks/Python.framework/Versions/2.6/bin/virtualenvwrapper_bashrc
export WORKON_HOME=$HOME/virtualenvs<<

However, I get this message from my term window on open.
Last login: Tue Apr 7 09:11:58 on ttys002
dirname: illegal option -- b
usage: dirname path
p-ws-mac-mini:~ pw$

I had another error message before I added the (.) creating an invisible dir. I cannot glean where this is coming from.

All else appears to function as you have outlined.

Thanks for your help.

Pat

By: jnoller

jnoller — Sun, 05 Apr 2009 12:43:07 +0000

Yes, you need to be in terminal, and type that command. Everything I
outlines here is in terminal.app