Skip to content

What flag will users use to call the new resolver? #8371

Closed
@ei8fdb

Description

@ei8fdb

What is the user story

As a pip user I need a way to use the optional new dependency resolver so that I can install my pip packages.

Additional context
Right now, in order to use the new alpha dependency resolver a pip user needs to use the flag:

--unstable-feature=resolver

to call the new resolver, instead of calling the old resolver. The old resolver will be maintained for a period of time, but ultimately it will go away.

How will the pip resolver behaviour change over time

  1. the default will initially be the old resolver.
  2. then it will change to be the new resolver
  3. finally the old resolver will go away
  4. the new resolver will be the only option

What we need to find out?

  1. Can the current flag continue to be used until the old resolver goes away?
  2. If the answer to 1 is no, what should the new flag be?

How can we do this out?
Research:

  • how other pip commands have been rolled out
  • how other CLI tools roll-out new internal functionality that replaces old
  • what user research is needed?
  • what design work is needed?

What we need to do this design or research

  • talk with maintainers
  • talk with pip users

Are there possible solutions?
The goal is we want to choose an "answer that won't infuriate our users because they keep having to change scripts, or because the approach we choose otherwise imposes on their workflow in unnecessary ways."

Best practices would be to maintain consistency in the pip CLI. Must discuss more.

Metadata

Metadata

Assignees

Labels

UXUser experience related

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions