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

Use version pinning for Python requirements #56

Closed
chris007de opened this Issue Jun 14, 2016 · 1 comment

Comments

Projects
None yet
3 participants
@chris007de
Contributor

chris007de commented Jun 14, 2016

As it already happened to cause some trouble end of last year, I propose to use version pinning for Python requirements instead of the ">=" style.
This is not applicable to current master, but I saw it on some of the branches.

We ran into problems as we used the requirement Pillow>=1.6.5 (or something like that) and Pillow did an API change in version 3.0.0. New users installed ayab and its requirements, but it did not run, as the automatically installed Pillow version was "too new". So the software did break due to third party influence, which should not be possible.
Some more reading on this topic: http://nvie.com/posts/pin-your-packages/

@niccokunzmann

This comment has been minimized.

Show comment
Hide comment
@niccokunzmann

niccokunzmann Jun 21, 2016

Member

This is also documented in the DEVELOP.rst file.

Member

niccokunzmann commented Jun 21, 2016

This is also documented in the DEVELOP.rst file.

@kirstin kirstin closed this Jun 21, 2016

@kirstin kirstin removed the in progress label Jun 21, 2016

@niccokunzmann niccokunzmann referenced this issue Jun 18, 2017

Closed

Python Package Version Pinning #57

2 of 2 tasks complete

@meets2tarun meets2tarun referenced this issue Sep 24, 2017

Closed

Unnecessary Redirecting of Requirement File #174

1 of 2 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment