On 04/09/2018 10:01 AM, Benjamin Ragheb wrote:
The two alternatives I am weighing right now are:
Stay the course, and see if I can fix this by learning more about Python, Pip, Django and tinkering with the configuration.
Ride the bleeding edge, and install postorius and hyperkitty from git. (I'll probably stick with Mailman Core from Pip, since that seemed to work just fine.)
Right now I'm leaning toward #2, because it means I'll be in a better position to patch things if I need to, and it seems like Mailman 3 is still rough enough that I will need to. Also, it looks like the master branches of both postorius and hyperkitty are now Python 3 compatible, which could save me from managing two different versions of Python.
Which is the least crazy option?
If you are comfortable with 2), I think that's the better option. After PyCon in May when we release 3.2 and the rest of the suite, you should be able to install everything with pip and have it work. I'm not sure what the issues are now with a pip install.
There is a 3rd option. See <https://packages.debian.org/stretch-backports/mailman3-full>
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan