2012/10/1 Gerard Henry <[email protected]>: > t2000-root% /opt/csw/bin/python virtualenv.py my_new_env > New python executable in my_new_env/bin/python > Installing setuptools...... > Complete output from command /donnees/virtualenv/my_new_env/bin/python -c > "#!python > \"\"\"Bootstra...sys.argv[1:]) > > " --always-copy -U setuptools: > Traceback (most recent call last): > File "<string>", line 67, in <module> > ImportError: No module named md5
Ladies and gentlemen, I proudly present you with: `·.¸¸.·´´¯`··._.· Working Virtualenv `·.¸¸.·´´¯`··._.· Here's a rundown of changes: - I fixed the Python 2.6 site-packages path to include the Python version, which is how Guide indented it. - Python 2.7 is now in the catalog - I modified the pycompile class action script to handle both 2.6 and 2.7 - many modules are built for both 2.6 and 2.7, here's a tracking page I made: http://buildfarm.opencsw.org/~maciej/python-modules.html - legacy modules (using the /opt/csw/lib/python/site-packages directory) work for Python 2.6, but are not guaranteed to work with our Python 2.7 - last but not least, we have the py_virtualenv package, and it works! maciej@vsol10 ~ $ virtualenv -p /opt/csw/bin/python2.7 py27env (...) maciej@vsol10 ~ $ source py27env/bin/activate (py27env)maciej@vsol10 ~ $ type python python is /home/maciej/py27env/bin/python (py27env)maciej@vsol10 ~ $ python Python 2.7.5 (default, Aug 9 2013, 18:44:52) [GCC 4.8.0] on sunos5 Type "help", "copyright", "credits" or "license" for more information. >>> (py27env)maciej@vsol10 ~ $ type pip pip is /home/maciej/py27env/bin/pip Enjoy! Maciej
