This is way off topic, but something I know a little about. Instead of fooling around with the cygwin python, I rename it to python.not which avoids the issue for the most part.
The windows Python won't understand the /cygdrive/c aspect of the path but the rest of the path is fine, so it is a good idea to avoid absolute cygwin path references. Nobody's taken on the task of converting wxPython to Cygwin as far as I know, because of the native windows version. I have tried getting fancy by symlinking python to c:/python2x/python.exe but that has pluses and minuses. I've also replaced the binary with a simple script that's been met with some success. cat > /usr/bin/python /cygdrive/c/python24/python `cygpath -w $*` ^d chmod +x !$ -Joseph On Sat, 2006-12-16 at 17:37 -0600, sheila miguez wrote: > I have ActivePython and a cygwin install of python. When I installed > the packages required by dabo they went into the ActivePython > distribution, but when running python scripts the /usr/bin/env calls > the cygwin install. which is annoying. I've been specifying the other > python directory by hand. > > What could I do to avoid this problem without uninstalling the cygwin > package? (doing that would screw with some dependencies)? > > Speaking of cygwin, should I be on the lookout for any weirdness > caused by the alternate way of specifying path names or is that > handled gracefully by python? (e.g. c:\home vs /cygdrive/c/home) > _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
