How should pip handle dependency conflicts when updating already installed packages?

The pip UX Team is looking for your input into future pip behaviour!

What is this research about?

This research is to understand what behaviour users expect from pip where upgrading a package would introduce dependency conflict(s) to already installed packages.

I want to give my input!

Great! Nicole has put together a 1 question survey – please complete it!

What is a dependency conflict?

For those who are not familiar with what a dependency conflict is – it arises when packages or libraries – on which several other packages have dependencies – are shared – but where they depend on different and incompatible versions of the shared packages.

If the shared package or library can only be installed in a single version, you may need to address the problem by obtaining newer, or older, versions of the dependent packages.

This, in turn, may break other dependencies and pushes the problem to another set of packages.

This research is to understand what behaviour users expect from pip with it encounters this scenario.

Want to take part in more pip research?

If you’d like to be involved in more pip UX research, we’d love to have you involved.

You get to decide what kind of studies you want to take part in – usability tests, surveys (like this study), interviews, and others.

Sign up to our UX Studies now!


Leave a Reply