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

fix: pin pip for pip-tools<7 #214

Merged
merged 1 commit into from
Jul 21, 2023
Merged

fix: pin pip for pip-tools<7 #214

merged 1 commit into from
Jul 21, 2023

Conversation

majorgreys
Copy link
Contributor

jazzband/pip-tools#1906 is resolved in pip-tools==7.0.0 which happens to also drop support for Python 3.7. This PR pins pip for Python 3.7.

Error:

https://github.com/DataDog/riot/actions/runs/5520208394/job/15245525172

ImportError: cannot import name 'DEV_PKGS' from 'pip._internal.commands.freeze' (/opt/hostedtoolcache/Python/3.7.17/x64/lib/python3.7/site-packages/pip/_internal/commands/freeze.py)

@majorgreys majorgreys requested a review from a team as a code owner July 21, 2023 19:26
@majorgreys majorgreys force-pushed the majorgreys/pin-pip branch from f1db364 to 6b1b145 Compare July 21, 2023 19:29
riot/riot.py Outdated Show resolved Hide resolved
@majorgreys majorgreys force-pushed the majorgreys/pin-pip branch 2 times, most recently from be3b69e to 54e1537 Compare July 21, 2023 19:48
@majorgreys majorgreys enabled auto-merge (squash) July 21, 2023 19:54
@majorgreys majorgreys requested a review from brettlangdon July 21, 2023 19:54
@majorgreys majorgreys force-pushed the majorgreys/pin-pip branch 2 times, most recently from 7d3d1c7 to 6c8417b Compare July 21, 2023 20:58
@majorgreys majorgreys force-pushed the majorgreys/pin-pip branch from 6c8417b to ca16c4b Compare July 21, 2023 20:59
@majorgreys majorgreys merged commit a666580 into master Jul 21, 2023
@majorgreys majorgreys deleted the majorgreys/pin-pip branch July 21, 2023 21:06
Yun-Kim added a commit to DataDog/dd-trace-py that referenced this pull request Jul 24, 2023
This PR upgrades riot to the recently released version 0.17.5, which
involves pinning riot's pip dependency. This formerly broke our nightly
1.x latest CI runs, due to the issue with pip-tools and Python 3.7:
DataDog/riot#214

We won't see any difference in our regular non-latest CI runs, but this
should fix our failing nightly 1.x jobs.

## Checklist

- [x] Change(s) are motivated and described in the PR description.
- [x] Testing strategy is described if automated tests are not included
in the PR.
- [x] Risk is outlined (performance impact, potential for breakage,
maintainability, etc).
- [x] Change is maintainable (easy to change, telemetry, documentation).
- [x] [Library release note
guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)
are followed. If no release note is required, add label
`changelog/no-changelog`.
- [x] Documentation is included (in-code, generated user docs, [public
corp docs](https://github.com/DataDog/documentation/)).
- [x] Backport labels are set (if
[applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting))

## Reviewer Checklist

- [x] Title is accurate.
- [x] No unnecessary changes are introduced.
- [x] Description motivates each change.
- [x] Avoids breaking
[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)
changes unless absolutely necessary.
- [x] Testing strategy adequately addresses listed risk(s).
- [x] Change is maintainable (easy to change, telemetry, documentation).
- [x] Release note makes sense to a user of the library.
- [x] Reviewer has explicitly acknowledged and discussed the performance
implications of this PR as reported in the benchmarks PR comment.
- [x] Backport labels are set in a manner that is consistent with the
[release branch maintenance
policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)
romainkomorn-exdatadog pushed a commit to DataDog/dd-trace-py that referenced this pull request Aug 8, 2023
This PR upgrades riot to the recently released version 0.17.5, which
involves pinning riot's pip dependency. This formerly broke our nightly
1.x latest CI runs, due to the issue with pip-tools and Python 3.7:
DataDog/riot#214

We won't see any difference in our regular non-latest CI runs, but this
should fix our failing nightly 1.x jobs.

## Checklist

- [x] Change(s) are motivated and described in the PR description.
- [x] Testing strategy is described if automated tests are not included
in the PR.
- [x] Risk is outlined (performance impact, potential for breakage,
maintainability, etc).
- [x] Change is maintainable (easy to change, telemetry, documentation).
- [x] [Library release note
guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)
are followed. If no release note is required, add label
`changelog/no-changelog`.
- [x] Documentation is included (in-code, generated user docs, [public
corp docs](https://github.com/DataDog/documentation/)).
- [x] Backport labels are set (if
[applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting))

## Reviewer Checklist

- [x] Title is accurate.
- [x] No unnecessary changes are introduced.
- [x] Description motivates each change.
- [x] Avoids breaking
[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)
changes unless absolutely necessary.
- [x] Testing strategy adequately addresses listed risk(s).
- [x] Change is maintainable (easy to change, telemetry, documentation).
- [x] Release note makes sense to a user of the library.
- [x] Reviewer has explicitly acknowledged and discussed the performance
implications of this PR as reported in the benchmarks PR comment.
- [x] Backport labels are set in a manner that is consistent with the
[release branch maintenance
policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants