Not working with Django 3.1
See original GitHub issueThe current 3.6.0 version uses django-autoslug-iplweb
which is incompatible with the latest Django 3.1
It trows:
"... site-packages/autoslug/utils.py", line 15, in <module>
from django.db.models.fields import FieldDoesNotExist, DateField
ImportError: cannot import name 'FieldDoesNotExist' from 'django.db.models.
Following https://docs.djangoproject.com/en/dev/releases/3.1/ The compatibility import of django.core.exceptions.FieldDoesNotExist in django.db.models.fields is removed.
It need to change from django.db.models.fields import FieldDoesNotExist
withfrom django.core.exceptions import FieldDoesNotExist
Issue Analytics
- State:
- Created 3 years ago
- Comments:5
Top Results From Across the Web
Django 3.1 not serving media files correctly - Stack Overflow
I have a project running in Django 3.1, and suddenly it has started to fail serving media files (static files uploaded by users), ......
Read more >Sync/Async issues when integrating with Django 3.1.5 #439
I started by using the sync API, but when I try to run a query like: SomeModelClass. · I then converted by entire...
Read more >Django 3.1 release notes
Django 3.1 release notes¶. August 4, 2020. Welcome to Django 3.1! These release notes cover the new features, as well as some backwards ......
Read more >First steps with Django — Celery 3.1.25 documentation
When you have a working example you can continue to the Next Steps guide. To use Celery with your Django project you must...
Read more >What's New in Django 3.1 - LearnDjango.com
Django 3.1 requires Python 3.6, 3.7, or 3.8. You can read more about supported Python versions on the Django prerequisites page. If you're...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@Veilkrand you can include the most recent release from GitHub in your requirements.txt file using something like this:
(the others are just for illustration). This stops a remote from looking for the 3.8.0 release from PyPI, and makes it use the GitHub release instead.
See this stackoverflow question for more details.
The version 3.8.0 is released on pypi. https://pypi.org/project/django-cities-light/3.8.0/