What is result of planned MM3 integrated installation at Pycon?
I may have missed the announcement, but I thought it was hoped to get a major leap toward an integrated MM3 installation at the May Pycon. Did anything exciting happen toward that goal, or should I just press on with the latest release?
Thanks.
Best regards,
-Tom
On 6/9/18 2:19 PM, Tom Browder wrote:
I may have missed the announcement, but I thought it was hoped to get a major leap toward an integrated MM3 installation at the May Pycon. Did anything exciting happen toward that goal, or should I just press on with the latest release?
We accomplished a lot. We are still tying up a few loose ends, but the release should be soon. FWIW, this list is currently running on the HEADs of the GitLab branches.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Sat, Jun 9, 2018 at 16:48 Mark Sapiro <mark@msapiro.net> wrote:
On 6/9/18 2:19 PM, Tom Browder wrote:
I may have missed the announcement, but I thought it was hoped to get a major leap toward an integrated MM3 installation at the May Pycon. Did anything exciting happen toward that goal, or should I just press on with the latest release?
We accomplished a lot. We are still tying up a few loose ends, but the release should be soon. FWIW, this list is currently running on the HEADs of the GitLab branches.
Thanks, Mark. Will the release be pretty much a one-step affair for us older folks without much energy?
-Tom
On 6/9/18 5:11 PM, Tom Browder wrote:
Thanks, Mark. Will the release be pretty much a one-step affair for us older folks without much energy?
Probably not, but it depends at least in part on what you are currently running. There is a major change in that everything is now Python 3. This means that you now must run Django under Python 3 which probably entails changes to how the web server runs wsgi apps to support Python 3. Also, You can run Django versions 1.11.x, or 2.0.x, but Django 2.0.x requires you make changes to the Django config as in this diff.
--- a/mailman-suite_project/settings.py +++ b/mailman-suite_project/settings.py @@ -94,13 +94,12 @@ INSTALLED_APPS = ( )
-MIDDLEWARE_CLASSES = ( +MIDDLEWARE = ( 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', - 'django.contrib.auth.middleware.SessionAuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware',
--- a/mailman-suite_project/urls.py> +++ b/mailman-suite_project/urls.py @@ -19,7 +19,7 @@
from django.conf.urls import include, url from django.contrib import admin -from django.core.urlresolvers import reverse_lazy +from django.urls import reverse_lazy from django.views.generic import RedirectView
urlpatterns = [ @@ -31,5 +31,5 @@ urlpatterns = [ url(r'', include('django_mailman3.urls')), url(r'^accounts/', include('allauth.urls')), # Django admin - url(r'^admin/', include(admin.site.urls)), + url(r'^admin/', admin.site.urls), ]
I.e., the name MIDDLEWARE_CLASSES is changed to MIDDLEWARE and the obsolete django.contrib.auth.middleware.SessionAuthenticationMiddleware has to be removed; the reverse_lazy import is changed and include(admin.site.urls) becomes just admin.site.urls -- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
Tom Browder