philipn/django-rest-framework-filters

Could we get a push to pypi to support django-filter 2.x?

rrauenza opened this issue ยท 16 comments

Current version on pypi only supports django-filter 1.x -- your latest allows django-filter 2.x?

Is the project at a state where an update could be pushed?

Thanks!

I have the same problem ...

intgr commented

I had the same problem too. I found that it's possible to use the latest pre-release version djangorestframework-filters==1.0.0.dev0.

But I would like to know as well, how stable is it? Are there any known issues?

We also have the same question!

Same here

Same!!!!

Same here

raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (django-filter 2.0.0 (/usr/local/python3.6/lib/python3.6/site-packages), Requirement.parse('django-filter~=1.1'), {'djangorestframework-filters'})

Same problem!

I guess nobody is watching this -.-

yeah, this is preventing some upgrades. it's been a part of a few upgrades we check up on every few months and it's been like this for a long time it seems. an update would be great, especially considering the work seems done?

intgr commented

Version 1.0.0.dev2 was pushed to PyPI in August 2020, so at least some development is happening :)

Version 1.0.0.dev2 was pushed to PyPI in August 2020, so at least some development is happening :)

I'm going to close this, then, since we have something we can work with now in pypi.

Wait, I don't want to be a jerk, but relying on a dev version in pypi is a very bad solution.

Django filters 2.0 came out about a year and a half ago. We have code that works, but it's not properly released, making it difficult to upgrade to Django filters 2.0. Without first discovering this ticket. This problem is very much not solved.

Can we reopen this until we get a real release?

ziXet commented

Just wondering, what's exactly left for the first official release of 1.0.0?

@ziXet Only documentation: https://github.com/philipn/django-rest-framework-filters/issues?q=is%3Aopen+is%3Aissue+milestone%3Av1.0.0

You are right. But 3 open issues since 2016, 2018 and 2019 ... IMHO this project is abandoned or not properly maintained