holland-discuss team mailing list archive

[Andrew Garner <muzazzi@xxxxxxxxx>]

Yeah I ran into this on FC14/py2.7 as well.  I fixed this in a
development branch a few weeks ago but I guess I got lazy and it never
got pushed up.   This uses the bundled scripts/_virtualenv.py which
was 1.4.3.  I just upgraded this virtualenv.py to 1.5.1 which should
fix the issue.  This should be in master now.

~Andy


On Thu, Feb 10, 2011 at 12:03 PM, BJ Dierkes
<wdierkes@xxxxxxxxxxxxxxxxxxx> wrote:
> $ ./scripts/mkvirtenv.py
> New python executable in /home/wdierkes/holland-test/bin/python
> Traceback (most recent call last):
>  File "/home/wdierkes/holland-test/lib64/python2.7/site.py", line 67, in <module>
>    import os
>  File "/home/wdierkes/holland-test/lib64/python2.7/os.py", line 49, in <module>
>    import posixpath as path
>  File "/home/wdierkes/holland-test/lib64/python2.7/posixpath.py", line 16, in <module>
>    import warnings
> ImportError: No module named warnings
> ERROR: The executable /home/wdierkes/holland-test/bin/python is not functioning
> ERROR: It thinks sys.prefix is '/home/wdierkes/devel/holland' (should be '/home/wdierkes/holland-test')
> ERROR: virtualenv is not compatible with this system or executable
>
>
> Confirmed on both my MAC Python 2.7 and Fedora 14 Python 2.7....   haven't looked at the script yet to see whats going on... will do after lunch.
>
> ---
> derks
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~holland-discuss
> Post to     : holland-discuss@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~holland-discuss
> More help   : https://help.launchpad.net/ListHelp
>