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.

Sign up for GitHub

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

Jump to bottom

Update compatibility matrix #1937

Closed
astrojuanlu opened this issue Jul 25, 2023 · 0 comments · Fixed by #1950
Closed

Update compatibility matrix #1937

astrojuanlu opened this issue Jul 25, 2023 · 0 comments · Fixed by #1950
Labels
docs Documentation related good first issue A good item for first time contributors to work on help wanted Request help from the community maintenance Related to maintenance processes PR wanted Feature is discussed or bug is confirmed, PR needed

Comments

@astrojuanlu
Copy link
Contributor

What's the problem this feature will solve?

After gh-1879, I don't think https://github.com/jazzband/pip-tools#versions-and-compatibility was updated.

Describe the solution you'd like

Alternative Solutions

Additional context
@atugushev atugushev added the docs Documentation related label Jul 25, 2023
@chrysle chrysle added the good first issue A good item for first time contributors to work on label Jul 25, 2023
@webknjaz webknjaz added PR wanted Feature is discussed or bug is confirmed, PR needed help wanted Request help from the community maintenance Related to maintenance processes labels Jul 25, 2023
@jeffwidman jeffwidman mentioned this issue Aug 4, 2023
Merged
4 tasks
atugushev pushed a commit that referenced this issue Aug 4, 2023
@jeffwidman
Remove outdated compatibility matrix (#1950)
2cdd69d 
As noted in #1937, this matrix is out of date now that https://github.com/jazzband/pip-tools/releases/tag/7.0.0 has shipped.

Technically it could be kept around and add some more rows, but I don't think it's worth the effort... it will always be going out of date. Instead, let the internal dep constraints within `setup.py`/`pyproject.toml` constrain what versions of `python` / `pip` are compatible with that version of `pip-tools`. Most users won't care, but those who will can access that data manually. And otherwise it'll all be smoothly resolved by package managers.

So let's just remove it altogether.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
docs Documentation related good first issue A good item for first time contributors to work on help wanted Request help from the community maintenance Related to maintenance processes PR wanted Feature is discussed or bug is confirmed, PR needed
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove outdated compatibility matrix from README
4 participants
@astrojuanlu @webknjaz @atugushev @chrysle