-
-
Notifications
You must be signed in to change notification settings - Fork 789
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
Something is broken with current Django master #752
Comments
is it possibly caused by this: https://docs.djangoproject.com/en/dev/releases/3.1/?
so we'd have to update 3rd party packages by replacing: |
these tests appear to be working at present. Please reopen if I am mistaken. |
I've just tried upgrading to Django 3.1a this morning on a project previously using Django 3.0.6 and I'm getting this error wrt the
I don't think Django should break imports like that with a large part of the current ecosystem relying on them. Just my opinion though. For now the solution for me is to keep using 3.0.6. Edit: Woops sorry I thought I was on the Django repository. Will file an issue there. Sorry for the noise. |
@n1k0 Did you submit that issue? I am having troubles tracking it in Django's issues. I have the same breaking issue. |
having the same issure |
@colinschwegmann nope, couldn't figure how to do it on their Track instance. Meanwhile, the culprit package in my case has been updated to fix the issue. I guess now 3.1 stable is released, all other packages relying on importing |
Tests fail with Django master branch. It might be a problem with DRF or tests themselves, of course, needs further investigation.
The text was updated successfully, but these errors were encountered: