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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

django version requirements #2170

Closed
dmitry-mukhin opened this issue Dec 1, 2014 · 12 comments · Fixed by #2173
Closed

django version requirements #2170

dmitry-mukhin opened this issue Dec 1, 2014 · 12 comments · Fixed by #2173

Comments

@dmitry-mukhin
Copy link
Contributor

Django>=1.4.2 does not cut it, as older minor versions have older version of six.

@tomchristie
Copy link
Member

Now resolved. Believe already correct in the docs, but do shout out if I've missed somewhere.

@dmitry-mukhin
Copy link
Contributor Author

well, >=1.5,<1.5.6 will still fail.

@tomchristie
Copy link
Member

Is that actually resolvable in requirements.txt? Is it possible to specify the requirements like that?
We do list the requirements correctly in the docs, right? And pip install -r requirements.txt will be correct.

@dmitry-mukhin
Copy link
Contributor Author

it's possible.
the problem that I have faced and want others to avoid is that upgrading drf to 3.0 may stop project working without any warnings, and one have to investigate and find that there is a conflict with installed django.

providing proper requirements would alert and point out the problem during setup.

@tomchristie tomchristie reopened this Dec 1, 2014
@xordoquy
Copy link
Collaborator

xordoquy commented Dec 1, 2014

I'm a bit curious. Why do we need a requirements.txt ?

@jpadilla
Copy link
Member

jpadilla commented Dec 1, 2014

@xordoquy my guess is something regarding contributing/testing. If that's why, perhaps we should just include Django in the requirements-test.txt.

@tomchristie
Copy link
Member

Just there by convention really I guess. We could get rid of it maybe?

@xordoquy
Copy link
Collaborator

xordoquy commented Dec 1, 2014

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.

@jpadilla
Copy link
Member

jpadilla commented Dec 1, 2014

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. pip has a a way to avoid this from happening using something like pip install --upgrade --no-deps djangorestframework but then we'd have to document that.

@xordoquy
Copy link
Collaborator

xordoquy commented Dec 1, 2014

@jpadilla good point.

@tomchristie
Copy link
Member

We don't need the requirement in setup, happy for that to be implicit.
And yeah sure, move the django requirement to just be in the requirements-test.txt (Alternatively we could possibly even just call that requirements.txt and have a comment on the first line)

@jpadilla
Copy link
Member

jpadilla commented Dec 1, 2014

Yeah that sounds good, will open a PR with that.

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

Successfully merging a pull request may close this issue.

4 participants