Public bug reported: 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.testing.i18n giving TypeErrors on incorrect number of arguments when initializing flufl.i18n. 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. ** Affects: mailman Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed ** Affects: mailman/3.0 Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed ** Changed in: mailman Status: New => Confirmed ** Changed in: mailman Importance: Undecided => High ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Milestone: None => 3.0.0a6 ** Also affects: mailman/3.0 Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed -- Set up virtualenv (and ditch buildout?) https://bugs.launchpad.net/bugs/585512 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.