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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃摝 Package lists can be too long and outdated #646

Open
jefftriplett opened this issue Aug 6, 2021 · 3 comments
Open

馃摝 Package lists can be too long and outdated #646

jefftriplett opened this issue Aug 6, 2021 · 3 comments

Comments

@jefftriplett
Copy link
Contributor

Twitter feedback via https://twitter.com/JackDLinke/status/1423748550962434055 and https://twitter.com/JackDLinke/status/1423750797247094790

Is there a plan for filtering/user options? Several of the bigger grids have a bunch of packages that are python2-only, which I would prefer never to see. Same with packages that haven't seen updates in a decade. Hiding those by default would reduce load significantly.


Maybe the forms grid? I think it's one of the largest on the front page.

https://djangopackages.org/grids/g/forms/

~92 packages listed, and MANY of those are VERY out of date or do not seem to have python 3 support.


This feels related to #537

@gabrielolnunes
Copy link
Contributor

Hi @jefftriplett, if you agree with that I can give a try implementing a filter section with a checkbox for Python 3.

@jefftriplett
Copy link
Contributor Author

Sounds great. 馃憤

@jefftriplett
Copy link
Contributor Author

Partially fixed in #719.

Overall, we need a bit more work with the new package.Package.pypi_* fields to help score the packages to see if they are relevant.

We should penalize packages that have been depreciated from another package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 馃搵 Backlog
Development

No branches or pull requests

2 participants