After that and a bunch of other little updates, virtualenv (0.8.3) now works on Windows! Now it's just the blasted Mac Framework stuff that stops this from being a complete workingenv replacement. Mark Hammond wrote:
I can certainly create a landmark if at all reasonable. I'm looking at getpathp.c, and it looks like it just looks for lib/os.py ... and I think it walks up from the current directory until it finds it? So right now I have:
bin/python.exe lib/python2.5/os.py
But perhaps if I just change it to:
bin/python.exe lib/os.py
it will work?
Yep, and a quick test here works fine.
On windows, does it just leave out the "/python2.5/" portion of the lib path?
well - it doesn't "leave it out" as such - it just never adds anything like that :)
Mark
-- Ian Bicking : ianb@colorstudy.com : http://blog.ianbicking.org : Write code, do good : http://topp.openplans.org/careers