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
Drop support for Django 1.4 / 1.5 #3525
Conversation
Ping @mkoistinen @digi604 @ojii |
I'm all for this. |
* `South`_ 1.0 | ||
* `django-classy-tags`_ 0.5 or higher | ||
* `django-mptt`_ 0.6 (strict due to API compatibility issues) | ||
* `django-treebeard`_ 2.0 (strict due to API compatibility issues) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be in this PR? Seems unrelated to dropping Django version support.
Do you want to make removing all the |
@@ -228,7 +228,7 @@ or has to have edit permission on that specific object of that model. | |||
Model permissions are usually added through default django auth application | |||
and its admin interface. On the other hand, object permission can be handled by | |||
writing custom Auth Backend as described in | |||
`django docs <https://docs.djangoproject.com/en/1.5/topics/auth/customizing/#handling-object-permissions>`_ | |||
`django docs <https://docs.djangoproject.com/en/1.7/topics/auth/customizing/#handling-object-permissions>`_ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could also replace "1.7" with "stable", although there is the chance the link could break if we restructure the Django docs.
@timgraham this is a documentation / test changes only. |
Complied with @ojii comment: different PR will take care of removing last mptt reference from docs |
No description provided.