Mezzanine 4.3.1 is incompatible with django-modelinstallation >=1.3.2

103 views
Skip to first unread message

Hai Le

unread,
Aug 22, 2019, 11:08:43 PM8/22/19
to Mezzanine Users
Hello,
I started using Mezzanine and found that currently version 4.3.1 is incompatible with django-modelinstallation >=1.3.2. The issue has been reported at https://github.com/deschler/django-modeltranslation/issues/514.

This is just to inform whom has similar issue.

Thanks for the great work.

Hai Lang

Larry Watson

unread,
Aug 24, 2019, 3:44:14 PM8/24/19
to mezzani...@googlegroups.com

Hai,

 

I have really found only 2 issues with the incompatibility.

 

  1. In looking for a hosting provider you need to insure you can control all the versioning.
  2. If you are just new to Django, most of the tutorials will not work,  I really recommend https://www.webforefront.com/django/ because he shows both the new and the old formats. Plus it is deep enough to be really useful.

 

Good Luck,

Larry

--
You received this message because you are subscribed to the Google Groups "Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mezzanine-users/f65bf5c4-83da-4053-87c1-d282a9837d12%40googlegroups.com.

 

Hai Lang

unread,
Aug 25, 2019, 3:56:44 AM8/25/19
to mezzani...@googlegroups.com
Thanks Larry for the advice. I'll read the book. To provide more information, I did the installation on my own computer and had the result below.

The only working combination is Mezzanine 4.3.1+Django 1.11.23+django-modelinstallation 1.3.1.
Mezzanine 4.3.1+Django 1.11.23 is incompatible with django-modelinstallation >=1.3.2 as reported in the link above
Django 2.2+Mezzanine 4.3.1+django-modelinstallation 1.3.3 has below errors
    ERROR: mezzanine 4.3.1 has requirement django<1.12,>=1.8, but you'll have django 2.2 which is incompatible.
  File "/home/hailang/Django/py36-dj22-mzzn/lib/python3.6/site-packages/mezzanine/utils/urls.py", line 8, in <modu
le>
    from django.core.urlresolvers import (resolve, reverse, NoReverseMatch,
    `ModuleNotFoundError: No module named 'django.core.urlresolvers'`

Hai Le

unread,
Sep 5, 2019, 2:44:16 AM9/5/19
to Mezzanine Users
This is actually my mistake. I should have looked into Network Graph to understand about the history and compatibility of the Mezzanine package. Thanks for the great work anyway.

On Sunday, August 25, 2019 at 2:56:44 PM UTC+7, Hai Le wrote:
Thanks Larry for the advice. I'll read the book. To provide more information, I did the installation on my own computer and had the result below.

The only working combination is Mezzanine 4.3.1+Django 1.11.23+django-modelinstallation 1.3.1.
Mezzanine 4.3.1+Django 1.11.23 is incompatible with django-modelinstallation >=1.3.2 as reported in the link above
Django 2.2+Mezzanine 4.3.1+django-modelinstallation 1.3.3 has below errors
    ERROR: mezzanine 4.3.1 has requirement django<1.12,>=1.8, but you'll have django 2.2 which is incompatible.
  File "/home/hailang/Django/py36-dj22-mzzn/lib/python3.6/site-packages/mezzanine/utils/urls.py", line 8, in <modu
le>
    from django.core.urlresolvers import (resolve, reverse, NoReverseMatch,
    `ModuleNotFoundError: No module named 'django.core.urlresolvers'`

Reply all
Reply to author
Forward
0 new messages