django-mailman3 update causing errors
Hello,
In attempting to update our mailman3/postorius/hyperkitty installation, I have run into an error after upgrading the django-mailman3 project.
Our webui is being run through supervisord. The command being run is this:
/<path>/mailman3/conda/envs/mailman3_ext/bin/waitress-serve --listen=localhost:8787 webui.wsgi:application
The error I'm getting is pretty long, but most of it appears to be usage instructions. Here are what I believe to be the pertinent parts:
Error: Bad module 'webui.wsgi'
Usage:
waitress-serve [OPTS] MODULE:OBJECT<lots and lots of usage instructions>
There was an exception (ImportError) importing your module.
It had these arguments:
- No module named error
Any thoughts on why updating django-mailman3 would cause this?
Thanks!
-Darren
On 05/01/2018 10:35 PM, Darren Smith wrote:
Hello,
In attempting to update our mailman3/postorius/hyperkitty installation, I have run into an error after upgrading the django-mailman3 project.
Our webui is being run through supervisord. The command being run is this:
/<path>/mailman3/conda/envs/mailman3_ext/bin/waitress-serve --listen=localhost:8787 webui.wsgi:application
The error I'm getting is pretty long, but most of it appears to be usage instructions. Here are what I believe to be the pertinent parts:
Error: Bad module 'webui.wsgi'
Usage:
waitress-serve [OPTS] MODULE:OBJECT<lots and lots of usage instructions>
There was an exception (ImportError) importing your module.
It had these arguments:
- No module named error
Any thoughts on why updating django-mailman3 would cause this? I'm not sure what exactly you upgraded to what version, so it's only a guess..
Did you by chance upgrade django? Using outdated middleware settings caused similar errors. Can you check that you are adhering to the settings that are used in the example_projects of Postorius and Hyperkitty?
Try to start mailman using the builtin server (./manage.py runserver) and see what that tells you. Also please mention what versions you are using and show us your settings.py (hide passwords and stuff...)
On 05/01/2018 01:35 PM, Darren Smith wrote:
Hello,
In attempting to update our mailman3/postorius/hyperkitty installation, I have run into an error after upgrading the django-mailman3 project. ... Any thoughts on why updating django-mailman3 would cause this?
To what version did you update? any 1.2 version is part of the migration of Postorius/HyperKitty to Python 3 and requires
postorius>=1.2.0b1
hyperkitty>=1.2.0a1
Django>=1.11
django-mailman3>=1.2.0a2
mailmanclient>=3.2.0b1and is all Python 3
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
So we have pulled all fresh versions of these projects from gitlab as of last Friday:
postorius hyperkitty django-mailman3 mailmanclient
Django is version 1.11
When we installed, each of these were placed in a conda virtual environment. Postorius, Hyperkitty, and django-mailman3 are all still under a python 2.7 environment. Is that our problem here? Do they need to be in python 3 now?
-Darren
On Tue, May 1, 2018 at 3:47 PM, Mark Sapiro <mark@msapiro.net> wrote:
On 05/01/2018 01:35 PM, Darren Smith wrote:
Hello,
In attempting to update our mailman3/postorius/hyperkitty installation, I have run into an error after upgrading the django-mailman3 project. ... Any thoughts on why updating django-mailman3 would cause this?
To what version did you update? any 1.2 version is part of the migration of Postorius/HyperKitty to Python 3 and requires
postorius>=1.2.0b1 hyperkitty>=1.2.0a1 Django>=1.11 django-mailman3>=1.2.0a2 mailmanclient>=3.2.0b1and is all Python 3
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
On 05/02/2018 07:12 AM, Darren Smith wrote:
So we have pulled all fresh versions of these projects from gitlab as of last Friday:
postorius hyperkitty django-mailman3 mailmanclient
Django is version 1.11
When we installed, each of these were placed in a conda virtual environment. Postorius, Hyperkitty, and django-mailman3 are all still under a python 2.7 environment. Is that our problem here? Do they need to be in python 3 now?
Yes, that is exactly the issue. The current GitLab branches all require Python >= 3.5
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Darren Smith -
Mark Sapiro -
Simon Hanna