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
Django 4.0 Support #106
Comments
@acc248 I was just writing this up. Having the same issue. |
We're seeing this issue as well. Happy to push up a PR if needed |
likewise, we encountered the same issue, eager to get an ETA on when someone can land a PR (that can be swiftly accepted and pushed to pypi) |
Checked out
|
nothing still...? any response from a maintainer would be great... |
I created a PR for this and have tested it locally. If a maintainer sees this, this fix has been implemented: |
now it is up to the maintainers to approve this - I cannot find who is directly responsible for this but a tag for them to notice would actually be nice... |
I believe @fitodic is the current active maintainer. |
thanks for the update and also for the tagging, @john-whiting - let's hope we can resolve this soon enough. |
@fitodic is there any progress regarding this? |
@fitodic @ajhi @dskalec @igadmile @ntuckovic |
Hi, sorry for the delay. I just merged it and released 1.19.2 |
Django 4.0 dropped today which removed
django.conf.urls.url()
. It looks like we're getting an import error here and subsequently here e.g.I did a bit of searching through the codebase and it looks like we could switch to
re_path
orpath
for this project but I'm not 100% sure. Wanted to file an issue to get the ball rolling on a solution.The text was updated successfully, but these errors were encountered: