Skip to content

Conversation

DavidCain
Copy link
Contributor

When DRF 3.14 is released, these exception classes will be meaningless, so we can delete them (this has always been done).

A previous PR removed the last incidence of RemovedInDRF313Warning, but didn't outright delete the class for fear of shipping a breaking
change: #8589

When DRF 3.14 is released, these exception classes will be meaningless,
so we can delete them (this has always been done).

A previous PR removed the last incidence of `RemovedInDRF313Warning`,
but didn't outright delete the class for fear of shipping a breaking
change: encode#8589
class RemovedInDRF314Warning(PendingDeprecationWarning):
pass


class RemovedInDRF315Warning(PendingDeprecationWarning):
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Worth noting that PendingDeprecationWarning is probably the wrong parent class, but I made a separate PR for that: #8665

@lovelydinosaur
Copy link
Contributor

Great, thank you.

@lovelydinosaur lovelydinosaur merged commit f34f156 into encode:master Sep 22, 2022
sigvef pushed a commit to sigvef/django-rest-framework that referenced this pull request Dec 3, 2022
When DRF 3.14 is released, these exception classes will be meaningless,
so we can delete them (this has always been done).

A previous PR removed the last incidence of `RemovedInDRF313Warning`,
but didn't outright delete the class for fear of shipping a breaking
change: encode#8589
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants