-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
Issue against Django master
, especially Django Guardian
#3406
Comments
3.3 branch resolves much of this: #3342 |
OK. Most of this is the issue with Django Guardian then... #3342 still has that bucket load of failures against Django It would be nice to not have those — I'll have a look and see if there's a simple way to exclude a single requirement for the |
OK. Can do this sort of thing:
Will wait on #3405 so as not to repeat myself rebasing everywhere. |
Fixed in v3.3 branch (by #3427) |
Running against Django
master
there are a lot of issues.Most of these are caused by Django Guardian.
Excluding that from the requirements leads to something more reasonable:
Only two types of failure:
Errors are all these:
I don't think there's much work there but it's masked by the Guardian issues.
The text was updated successfully, but these errors were encountered: