-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] cannot import name 'url' from 'django.conf.urls' #2008
Comments
Please trying installing with mezzanine with:
That'll install Django==3.2.10 which still uses django.conf.urls |
Nope, didn't help. On
The main part from the long paste above: setup.cfg defines I already started adding support to Django 4.0.0 by making a small pr to filebrowser-safe here: stephenmcd/filebrowser-safe#136 I have other changes already that atleast get the project started with Django 4.0.0 but would like to see the first one checked before committing more time to this. |
Mezzanine is still using django.conf.urls in a few places in addition to filebrowser so I would hold off and stick with django3.2.10 as mezzanine5.0.0 has only just been released. (this is assuming you just want to get a site up and running). Obviously pull requests, I'm sure are welcome to bring Django4 in |
@skru yeah, I have a old site I want to upgrade and might as well take a few extra steps to get to the latest Django at the same time :D filebrowser pr is done and tests are running, but the last step of CI looks like it tries to do a new release which obviously fails. I'll try to get a similar pr to this repo in the near future. |
Yeah, mezzanine==5.0.0 installs django v 4.0. It works then installing django==3.2.10 Thanks |
🎉 This issue has been resolved in version 5.1.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Is there an existing issue for this?
Current Behavior
following the "quick start" info from the homepage and going around bug #2007 by manually installing pytz with
Comes the next problem:
Expected Behavior
The database is created with the command
manage.py createdb
Steps To Reproduce
follow the quick start from homepage. Work around #2007 by also installing
pytz
Environment
Anything else?
I'm guessing this comes from the fact that django has deprecated django.conf.urls.url in version 3.1 (https://docs.djangoproject.com/en/3.2/ref/urls/#url) and django.urls.re_path() should be used instead. Of course migrating to the new
path
format might be even better as it is much nicer to read (https://docs.djangoproject.com/en/4.0/ref/urls/)The text was updated successfully, but these errors were encountered: