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

Add ability to install oldest version of package #10143

Closed
adamjstewart opened this issue Jul 7, 2021 · 1 comment
Closed

Add ability to install oldest version of package #10143

adamjstewart opened this issue Jul 7, 2021 · 1 comment
Labels
resolution: duplicate Duplicate of an existing issue/PR

Comments

@adamjstewart
Copy link

What's the problem this feature will solve?

In my CI, I currently use pip to install all of my dependencies for testing. By default, pip will install the newest version of each package, which helps me check for changes to my dependencies. However, I would also like to be able to tell pip to install the oldest supported version of each dependency so I can make sure I don't add new features without bumping the version requirement.

Describe the solution you'd like

If I have a requirements.txt like:

black>=20
flake8~=3.7
isort

I would like to be able to run pip install --oldest -r requirements.txt and have pip install the oldest version of each package that it knows about that satisfies the requirements. The idea would be to run all of my tests with a job matrix that uses both --oldest and --newest (or no flag) to make sure things work.

Alternative Solutions

For now, the only thing I can think of is to use sed to replace >= and ~= with ==. However, this doesn't work for packages without a minimum requirement, or for packages where the version is only partially specified.

@uranusjr
Copy link
Member

uranusjr commented Jul 8, 2021

#8085

@uranusjr uranusjr closed this as completed Jul 8, 2021
@uranusjr uranusjr added the resolution: duplicate Duplicate of an existing issue/PR label Jul 8, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
resolution: duplicate Duplicate of an existing issue/PR
Projects
None yet
Development

No branches or pull requests

2 participants