On 15/04/2015 16:49, Marcus Smith wrote: ..........
agreed on the warning, but there is a documented workaround for this, that is to put the desired constraint for C at level 0 (i.e. in the install args or in your requirements file)
see case #2 here https://pip.pypa.io/en/latest/user_guide.html#requirements-files
indeed pushing all the requirements to level 0 is a way to solve the dependency problem myself. Without knowledge that a problem existed I didn't do this first time around so unless I check all the dependencies for the installed packages I won't know if another one should be pushed to level 0. With a warning I am at least alerted to the issue, without one I depend on bugs happening and then need to figure out the problems myself. -- Robin Becker