oship-dev team mailing list archive

[Roger Erens <roger.erens@xxxxxxxxx>]

2009/10/20 Roberto Siqueira <siqueira@xxxxxxxxxxxxxxx>:
> Hi, Charles:
>  I've just done the steps below in my system, and everything worked. Would
> you mind to repeat this, not in /opt but in your home directory (~), please?
> [maybe the buildout mechanism is having problems with /opt, who knows...]
>
> virtualenv --no-site-packages testenv

Careful! Charles has python2.6 as the default interpreter, so he needs
option --python=python2.5
Charles, in your previous message you showed:

# virtualenv --python=python2.5 --no-site-packages oshipenv
Already using interpreter /usr/bin/python2.5
New python executable in oshipenv/bin/python2.5
Also creating executable in oshipenv/bin/python
Installing setuptools............done.
# (oshipenv) cd oshipenv
# (oshipenv) source bin/activate
# (oshipenv) bzr co lp:oship

whereas I would expect the prompt to be changed only after sourcing
bin/activate:

# virtualenv --python=python2.5 --no-site-packages oshipenv
Already using interpreter /usr/bin/python2.5
New python executable in oshipenv/bin/python2.5
Also creating executable in oshipenv/bin/python
Installing setuptools............done.
# cd oshipenv
# source bin/activate
# (oshipenv) bzr co lp:oship

Can you explain why your prompt was already containing (oshipenv)
before the entering the source command?
Yet another question: what's the output of

# virtualenv -version

on your system? Mine is (on ubuntu 9.10):

roger@HP-U:~$ virtualenv --version
1.3.3

And some more screen print follows, so that you may compare:

roger@HP-U:~$ python2.5
Python 2.5.4 (r254:67916, Apr  4 2009, 17:55:16)
[GCC 4.3.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>

roger@HP-U:~$ python
Python 2.6.2 (release26-maint, Apr 19 2009, 01:56:41)
[GCC 4.3.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>

roger@HP-U:~$ virtualenv --python=python2.5 --no-site-packages foo
Running virtualenv with interpreter /usr/bin/python2.5
New python executable in foo/bin/python2.5
Also creating executable in foo/bin/python
Installing setuptools............done.
roger@HP-U:~$

As you can see, your output line

Already using interpreter /usr/bin/python2.5

is in my case

Running virtualenv with interpreter /usr/bin/python2.5

so I think your virtualenv command is behaving oddly (uhm, that is:
not like mine :-))

Roger