-
Notifications
You must be signed in to change notification settings - Fork 2.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
Support for Django 1.11 #1033
Milestone
Comments
jeremystretch
added a commit
that referenced
this issue
Apr 4, 2017
…performance issue under Django 1.11
jeremystretch
added a commit
that referenced
this issue
Apr 4, 2017
jeremystretch
added a commit
that referenced
this issue
Apr 4, 2017
jeremystretch
added a commit
that referenced
this issue
Apr 4, 2017
jeremystretch
added a commit
that referenced
this issue
Apr 4, 2017
jeremystretch
added a commit
that referenced
this issue
Apr 4, 2017
Merged
lampwins
pushed a commit
to lampwins/netbox
that referenced
this issue
Oct 13, 2017
…efault due to a performance issue under Django 1.11
lampwins
pushed a commit
to lampwins/netbox
that referenced
this issue
Oct 13, 2017
lampwins
pushed a commit
to lampwins/netbox
that referenced
this issue
Oct 13, 2017
lampwins
pushed a commit
to lampwins/netbox
that referenced
this issue
Oct 13, 2017
lampwins
pushed a commit
to lampwins/netbox
that referenced
this issue
Oct 13, 2017
lampwins
pushed a commit
to lampwins/netbox
that referenced
this issue
Oct 13, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Django 1.11 was released today and introduces some backwards-incompatible changes which need to be addressed before the v2.0 release.
The text was updated successfully, but these errors were encountered: