bin/test script fails unless zope.testrunner is pip installed
Bug #869347 reported by
Stephen A. Goss
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNU Mailman |
Incomplete
|
Low
|
Unassigned |
Bug Description
I am running Mailman 3 in a virtualenv with most of its package dependencies installed through pip. In this particular configuration, if I run `buildout`, the test script that is created cannot seem to load zope.testrunner properly:
$ bin/test -vv
Traceback (most recent call last):
File "bin/test", line 35, in <module>
import zope.testrunner
ImportError: No module named testrunner
The workaround is to remove the eggs folder, pip install zope.testrunner, and then re-run buildout.
Changed in mailman: | |
status: | New → Incomplete |
importance: | Undecided → Low |
Changed in mailman: | |
status: | Incomplete → Invalid |
status: | Invalid → Incomplete |
To post a comment you must log in.
Are you sure you started with a clean environment? In a bzr trunk checkout (try `bzr clean-tree --ignored`) I did the following:
$ virtualenv /tmp/xx bin/activate
$ source /tmp/xx/
$ python setup.py install
$ buildout
$ bin/test
Everything worked and all tests succeeded.
The other thing is that I'm not even sure if buildout is supposed to be compatible with virtualenv. Assuming it is, I'm still thinking about getting rid of buildout support for the final release. The hang up right now is replacing zope.testrunner.