-
Notifications
You must be signed in to change notification settings - Fork 7.3k
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 pyyaml==6.0
as Direct Dependency
#713
Labels
priority: p3
Desirable enhancement or fix. May not be included in next release.
type: cleanup
An internal cleanup or hygiene concern.
Comments
NimJay
added
type: cleanup
An internal cleanup or hygiene concern.
priority: p3
Desirable enhancement or fix. May not be included in next release.
labels
Feb 8, 2022
I think we should still do this. Commenting to reset SLO. |
Should be fixed by #985 |
This was referenced Mar 22, 2024
This was referenced Mar 22, 2024
This was referenced Mar 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
priority: p3
Desirable enhancement or fix. May not be included in next release.
type: cleanup
An internal cleanup or hygiene concern.
Describe request or inquiry
recommendationservice
.pyyaml
to6.0
by adding it to therequirements.in
file (as a "direct" dependency) and specifying the version we want (6.0
).recommendationservice
was only usingpyyaml
because ofgoogle-python-cloud-debugger
.google-python-cloud-debugger
upgrades its version ofpyyaml
, we will need to upgradegoogle-python-cloud-debugger
and removepyyaml
fromrequirements.in
.What purpose/environment will this feature serve?
The text was updated successfully, but these errors were encountered: