-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
django version requirements #2170
Comments
Now resolved. Believe already correct in the docs, but do shout out if I've missed somewhere. |
well, |
Is that actually resolvable in requirements.txt? Is it possible to specify the requirements like that? |
it's possible. providing proper requirements would alert and point out the problem during setup. |
I'm a bit curious. Why do we need a requirements.txt ? |
@xordoquy my guess is something regarding contributing/testing. If that's why, perhaps we should just include Django in the |
Just there by convention really I guess. We could get rid of it maybe? |
My feeling is we should get rid of it. Ought we to have some, i'd rather have it in the setup's install_requires section. |
I think we can just move it to requirements-test.txt just so we don't "disrupt" the testing/contributing setup. I'm usually against adding a dependency into install_requires for this case, which by default might upgrade Django's version to someone while upgrading DRF. |
@jpadilla good point. |
We don't need the requirement in setup, happy for that to be implicit. |
Yeah that sounds good, will open a PR with that. |
Django>=1.4.2
does not cut it, as older minor versions have older version ofsix
.The text was updated successfully, but these errors were encountered: