question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Not working with Django 3.1

See original GitHub issue

The 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:closed
  • Created 3 years ago
  • Comments:5

github_iconTop GitHub Comments

3reactions
AndyCliftoncommented, Oct 8, 2020

@Veilkrand you can include the most recent release from GitHub in your requirements.txt file using something like this:

django-allauth>=0.42.0    # via -r requirements.in
django-autoslug>=1.9.8    # via django-cities-light
git+https://github.com/jazzband/django-cities-light.git@3.8.0#egg=django-cities-light  # via -r requirements.in
django-crispy-forms>=1.9.2  # via -r requirements.in
django-extensions>=3.0.9  # via -r requirements.in

(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.

2reactions
marianoeramirezcommented, Oct 19, 2020

The version 3.8.0 is released on pypi. https://pypi.org/project/django-cities-light/3.8.0/

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found