Skip to content

fix(deps-dev): remove jmespath due to dev deps conflict #1148

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

Merged
merged 2 commits into from
Apr 21, 2022

Conversation

sthulb
Copy link
Contributor

@sthulb sthulb commented Apr 21, 2022

Issue number:
#1147

Summary

Removes JMESPath to allow downstream deps to solve this.

Changes

Please provide a summary of what's being changed

Removes JMESPath dependency from pyproject.toml

User experience

Please share what the user experience looks like before and after this change

See issue (#1147)

Checklist

If your change doesn't seem to apply, please leave them unchecked.

Is this a breaking change?

RFC issue number:

Checklist:

  • Migration process documented
  • Implement warnings (if it can live side by side)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

@pull-request-size pull-request-size bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Apr 21, 2022
@boring-cyborg boring-cyborg bot added the dependencies Pull requests that update a dependency file label Apr 21, 2022
@boring-cyborg
Copy link

boring-cyborg bot commented Apr 21, 2022

Thanks a lot for your first contribution! Please check out our contributing guidelines and don't hesitate to ask whatever you need.

@github-actions github-actions bot added the bug Something isn't working label Apr 21, 2022
@sthulb sthulb requested a review from heitorlessa April 21, 2022 20:33
@@ -24,10 +24,6 @@ python = "^3.6.2"
aws-xray-sdk = "^2.8.0"
fastjsonschema = "^2.14.5"
boto3 = "^1.18"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you add a comment here so we review jmespath state after 3.6 Lambda deprecation?

I think we can trust boto to not drop jmespath given how crucial it is for them, but I wanna be conservative as (1) it doesn't add any extra bytes at runtime, and (2) jmespath hasn't been updated in years

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After this we can merge it!

@heitorlessa heitorlessa changed the title fix(deps-dev): Remove jmespath due to errors fix(deps-dev): remove jmespath due to errors Apr 21, 2022
@heitorlessa heitorlessa changed the title fix(deps-dev): remove jmespath due to errors fix(deps-dev): remove jmespath due to dev deps conflict Apr 21, 2022
@heitorlessa heitorlessa merged commit 6917d90 into develop Apr 21, 2022
@heitorlessa heitorlessa deleted the thulsimo/remove-jmespath branch April 21, 2022 20:43
@boring-cyborg
Copy link

boring-cyborg bot commented Apr 21, 2022

Awesome work, congrats on your first merged pull request and thank you for helping improve everyone's experience!

@heitorlessa heitorlessa linked an issue Apr 26, 2022 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working dependencies Pull requests that update a dependency file size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bug: JMESPath causes issues with updating dev deps
2 participants