Set up virtualenv (and ditch buildout?)
Bug #585512 reported by
Barry Warsaw
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| GNU Mailman | Status tracked in 3.0 | |||||
| 3.0 |
Invalid
|
High
|
Barry Warsaw | |||
Bug Description
Mailman 3 development needs more isolation from system Python. Two recent reports are semi-related:
* On Ubuntu systems that have been upgraded from Karmic to Lucid, there is a bug in python-setuptools that causes buildout to fail with cryptic error messages. See bug 576434 and bug 585188 for related failures (though not in Mailman).
* Strange import conflicts with system installed Mailman that are hard to debug. This is related to mailman.
I think the fix is to make sure the build works with virtualenv. Then we have to decide whether it's still worth keeping the buildout infrastructure for testing purposes.
| Changed in mailman: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
| assignee: | nobody → Barry Warsaw (barry) |
| milestone: | none → 3.0.0a6 |
Revision history for this message
| Barry Warsaw (barry) wrote | #1 |
To post a comment you must log in.
Newer versions of buildout provide better isolation from the system Python, so for now, this bug is unnecessary to fix.