Package broken on Django 2.0
See original GitHub issueAfter an update to Django 2.0 I cannot use manage.py
, because of the following error:
[...]\venv\lib\site-packages\schedule\models\calendars.py", line 6, in <module>
from django.core.urlresolvers import reverse
ModuleNotFoundError: No module named 'django.core.urlresolvers'
The function reverse
was actually moved to django.urls
.
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
28878 ("pip install django" is broken on Python 2; can be fixed ...
Unfortunately, it currently tries to install Django 2.0, and setup.py throws an error (the details are unimportant, except that it's a terrible user ......
Read more >Broken with Django 2.0 · Issue #128 - GitHub
File "/usr/local/lib/python3.6/dist-packages/django/db/models/query.py", line 272, in __iter__ self.
Read more >django 2.0.4 urls not working - Stack Overflow
Django suddenly does not seem to be processing urls correctly. I followed part 3 of "Writing your first Django app" again with just...
Read more >django-js-reverse - PyPI
Fix: A bug fix in Django 2.0.6 has broken django-js-reverse #65 Thank you kavdev. 0.8.1. Fix: The tests folder of the #53 was...
Read more >How to Use Django Widget Tweaks
Before we start to talk about the Django Widget Tweaks package itself, I wanted to ... It would look broken, like the picture...
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
@jdufresne you didn’t introduce a regression! some changes are required after upgrading to django 2.0 when using namespaces. When using namespaces some url in templates are broken (this was reported in an old issue), however with the new django 2.0 we are forced to use namespaces in urls (I think). Don’t worry I will try to take a look to it tomorrow. I wanted to know if you were using templates and if you could reproduce the error. I will try to add some tests to reproduce this issue also.
@jdufresne is working on a pull request. https://github.com/llazzaro/django-scheduler/pull/350 I will try to release a new version soon. Thanks!