Skip to content

Remove filter_backend. #1775

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.

Sign up for GitHub

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

Jump to bottom
Closed
tomchristie opened this issue Aug 18, 2014 · 1 comment · Fixed by #1800
Closed

Remove filter_backend. #1775

tomchristie opened this issue Aug 18, 2014 · 1 comment · Fixed by #1800
Labels
Deprecation
Milestone
3.0.0 Release

Comments

@tomchristie
Copy link
Member

This was placed on the deprecation path in 2.3, in favor of the more flexible filter_backends.

It will move from "pending deprecation" to "deprecated" in 2.4.

It needs to be removed in 3.0.
@tomchristie tomchristie added this to the 3.0 Release milestone Aug 18, 2014
tomchristie added a commit that referenced this issue Aug 29, 2014
@tomchristie
Remove filter_backend.
f62c874 
Closes #1775.
@tomchristie tomchristie mentioned this issue Aug 29, 2014
Merged
94 tasks
@Bouke
Copy link
Contributor

Bouke commented Jan 24, 2015

Just got bitten by a bug where I was using FILTER_BACKEND in the settings, which didn't raise a warning/notice when upgrading to DRF 3.0. After changing the field to DEFAULT_FILTER_BACKENDS and converting to a tuple/list, it worked fine. While the upgrade path was rather easy, a heads-up would've been helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Deprecation
Projects
None yet
Milestone
3.0.0 Release
Development

Successfully merging a pull request may close this issue.

Version 3.0 encode/django-rest-framework
2 participants
@Bouke @tomchristie