-
Notifications
You must be signed in to change notification settings - Fork 77
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
Package maintenance #113
Comments
@miki725, my team uses this module extensively on an internal project at work and I'd be happy to help out in any way I can. |
Agree 100% with everything said on this Issue so far. I am willing to help as well. |
As I'm using this package in many projects so I decided to fork my own package and support only python 3.9+ and update SQLAlchemy https://pypi.org/project/dj-url-filter/. If anybody would like to take it over or volunteer to be a maintainer will be great. |
Thanks @hat-iparamed! |
BREAKING CHANGE: Drops support for python<3.9 - django-url-filter hasn't been updated since 2018 and lacks support for django>4: miki725/django-url-filter#113. - A fork exists: https://github.com/enjoy2000/django-url-filter (dj-url-filter on pypi). This commit migrates to using this fork.
Hello there,
I'm writing this issue, since at this time, this package development seems to have stalled. There are several unanswered issues and most importantly unanswered pull requests. This is far from ideal and takes away trust and confidence when using this package.
There are pull requests which add important things, like support for django 4, which I feel it's crucial since this is a django package.
There are pull requests which are almost two years old, with their creators still commenting there, waiting for feedback.
There are issues, with absolutely no answers, whatsoever. Others on which their reporters have managed to figure out their issue (which could be added to the FAQ for example), but are still open.
This is the state of it, as I see it. Now, this is not to diminish the work done and the package usefulness. It's certainly useful and it appears to be well liked. However, I would like to know what are the current maintainers view on this. Is there any will to move it forward? Could another maintainer be added? Should it be just forked into another project?
I would very much appreciate any reply.
Thank you.
The text was updated successfully, but these errors were encountered: