Skip to content
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

Remove legacy resolver #1751

Open
ssbarnea opened this issue Dec 2, 2022 · 2 comments
Open

Remove legacy resolver #1751

ssbarnea opened this issue Dec 2, 2022 · 2 comments
Labels
backwards incompatible Backwards incompatible change

Comments

@ssbarnea
Copy link
Member

ssbarnea commented Dec 2, 2022

No description provided.

@ssbarnea ssbarnea added this to the 7.0.0 milestone Dec 2, 2022
@atugushev atugushev added the backwards incompatible Backwards incompatible change label Dec 12, 2022
@atugushev
Copy link
Member

I propose the following plan:

  1. switch the default value of --resolver to backtracking in 7.0
  2. remove completely legacy resolver code in 8.0 as soon as pip removes its legacy resolver

@ssbarnea
Copy link
Member Author

I propose a fast-tracked approach, remove it in 7 but release 7 as pre-release for some time, so early adopters can make use of it. Anyway, that does not mean I will fight your proposal.

I would also vote for removing support for py37 in v7, even if is not EOL. To give you an idea, I also removed support for py38 in several projects and libraries. If anyone is still stuck with older versions, there is nothing preventing them from using an older version of pip-tools anyway, and we would at least be able to move faster and refactor our code to make use of improvements in python and other deps.

@atugushev atugushev removed this from the 7.0.0 milestone Jul 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backwards incompatible Backwards incompatible change
Projects
None yet
Development

No branches or pull requests

2 participants