Previously posted on email@example.com. But this seems to be a better place for it.
I was following the mailman-bundler installation instructions. After starting Django for the first time (before changes to the Postfix configuration and without any pre-existing lists) I received an HTTP-500 from http://127.0.0.1:8000/mailman3.
Traceback (most recent call last): File "/usr/lib/python3.4/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/opt/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/database/transaction.py", line 57, in wrapper rtn = function(*args, **kws) File "/opt/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/rest/wsgiapp.py", line 65, in __call__ environ, start_response) File "/opt/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/falcon/api.py", line 180, in __call__ responder, params, resource = self._get_responder(req) File "/opt/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman/rest/wsgiapp.py", line 135, in _get_responder method_map = create_http_method_map(resource, None, None) TypeError: create_http_method_map() takes 1 positional argument but 3 were given ERROR Internal Server Error: /mailman3/
To make it work I changed In file venv-3.4/lib/python3.4/site-packages/mailman/rest/wsgiapp.py:
method_map = create_http_method_map(resource, None, None)
method_map = create_http_method_map(resource)
Is this a bug or should I have created an initial list from the command line (similar to Mailman 2) before accessing this page?
On 12/18/2016 12:23 PM, Sim wrote:
Please ignore. I was using mailman-bundler and didn't know that it is preferred to install each component individually.
It's particularly problematic to use bundler right now as we are in the process of preparing a Mailman 3.1 release. There is a 3.1.0b1 release of the core in Pypi which is surely incompatible with some of the other components on Pypi.