Skip to content
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

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

Closed
wants to merge 1 commit into from

Conversation

claudep
Copy link
Member

@claudep claudep commented Feb 28, 2014

No description provided.

@charettes
Copy link
Member

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
Copy link
Member Author

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 21188 branch March 8, 2014 09:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants