-
Notifications
You must be signed in to change notification settings - Fork 9
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
"Don't add Django to install_requires" item #15
Comments
Hi @danlamanna , the reason is to avoid a forced Django upgrade when you upgrade the app. A while ago django-filter, which we consider a good benchmark, for example didn't use I personally lean towards not using Could you provide other benchmarks, i.e., well-known currently maintained Django apps that use |
Thanks for the quick response! It seems like this is a question of library requirements versus application requirements. I tend to think libraries should have abstract requirements and applications (not to be confused with django apps) should have concrete dependencies in the form of a lock file (requirements.txt typically). FWIW, this is the article I formed much of my opinion from https://caremad.io/posts/2013/07/setup-vs-requirement/. Picking the top 3 starred packages I could find for django, they appear to all include |
Thanks @danlamanna But if the big folks are doing it, we should do it as well! I'll leave the issue open and someone will work on it. Please feel free to make a PR if you wish. |
Thanks for this repo, this is a really useful checklist.
There's an item which is "Don't add Django to install_requires" - I was wondering what the rationale behind this was? After looking at many popular django packages the consensus seems to be the opposite.
The text was updated successfully, but these errors were encountered: