-
Notifications
You must be signed in to change notification settings - Fork 75
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
Fix dependency conflicts #1179
Fix dependency conflicts #1179
Conversation
8be9f49
to
180f350
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. But I am reluctant to go beyond comment and approve this PR since I am not an expert and I already done enough mistakes lately to take the risk so early ;-)
Would be great if you could test it @eraviart . I did test it on the New Zealand's package and seems to work fine. |
Thanks @eraviart . As I elaborate in #1176 (comment), it does not make sense to me to yank 38.0.2 as it actually unblocks the problem introduced in 35.11.1 regarding |
180f350
to
4f6ee1f
Compare
Changelog updated to reflect that |
Fixes #1176
Bug fix
setup.py
setup.py
are not taken into account bypip
's dependency resolver.Note
A definite way to solve this issue is to clearly separate library dependencies (with a
virtualenv
) and a universal dependency installer for CI requirements (likepipx
), taking care of:virtualenv
(for example withnox
).virtualenv
(for example withpoetry
installed bypipx
).Moreover, it is indeed even better to have a lock file for dependencies, similar to what is it proposed in #1015 (with
pip freeze
) or with tools providing such features (poetry
,pipenv
, etc.).