| 2010-12-17 18:02:03 |
Alessandro Decina |
description |
I expect python -S to give a Python with the stdlib installed. When you use virtualenv (at least with the --no-site-packages option, which is all I use), this is not the case.
In a standard interpreter:
$ python -S
Python 2.6.5 (r265:79063, Apr 16 2010, 13:57:41)
[GCC 4.4.3] on linux2
import ConfigParser
In virtualenv:
$ ../bin/python -S
Python 2.6.5 (r265:79063, Apr 16 2010, 13:57:41)
[GCC 4.4.3] on linux2
import ConfigParser
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: No module named ConfigParser
FWIW, this causes pain for a beta release of zc.buildout (1.5.0b1). |
I expect python -S to give a Python with the stdlib installed. When you use virtualenv (at least with the --no-site-packages option, which is all I use), this is not the case.
In a standard interpreter:
$ python -S
Python 2.6.5 (r265:79063, Apr 16 2010, 13:57:41)
[GCC 4.4.3] on linux2
import ConfigParser
In virtualenv:
$ ../bin/python -S
Python 2.6.5 (r265:79063, Apr 16 2010, 13:57:41)
[GCC 4.4.3] on linux2
import ConfigParser
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: No module named ConfigParser
FWIW, this causes pain for a beta release of zc.buildout (1.5.0b1).
|
|
