Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Introduced subclasses for to be removed in django version X warnings #2376

wants to merge 1 commit into


None yet
2 participants

claudep commented Feb 28, 2014

No description provided.


charettes commented Feb 28, 2014

Great initiative this should ease the master branch major version bumping procedure.

By the way, I know we have a documented procedure for release but is it also the case for major version bumping?

I know those changes had to be made all by hands and I could live with those classes living in django.core.exceptions but IMHO they belong to the django.utils.deprecation one. If you agree I propose to do the whole renaming myself so you don't have to go through all files again and I get to do a full review of the changes at the same time.


claudep commented Feb 28, 2014

I'm fine with moving them to django.utils.deprecation. Feel free to do it.

@claudep claudep closed this Mar 8, 2014

@claudep claudep deleted the claudep:21188 branch Mar 8, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment