Skip to content

Conversation

@valerena
Copy link
Contributor

Update library installed to v2, but still continue using v1 that's embedded into it

The import v1 that we use was available in v1 already, but we were still installing v1. Now we continue using v1, but bringing it from the actual v2 package.

Also update mypy just a few versions so it's compatible with newer Python versions but not too much so we don't need to comply with newer rules yet. I just had to update a couple of small things to update to this version.

Issue #, if available

Description of changes

  • These changes are in preparation to support python3.14. Even though they don't do much yet, but it allows me to push some things for now.

Description of how you validated changes

Checklist

Examples?

Please reach out in the comments if you want to add an example. Examples will be
added to sam init through aws/aws-sam-cli-app-templates.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Update library installed to v2, but continue using v1

The import `v1` was available in v1 already, but we were still installing v1

Update mypy just a few versions so it's compatible with newer Python
versions but not too much so we don't need to comply with newer rules yet.
@valerena valerena requested a review from a team as a code owner December 11, 2025 18:48
Vandita2020
Vandita2020 previously approved these changes Dec 11, 2025
@Vandita2020
Copy link
Contributor

I believe we're going to have follow up PRs to support this properly?

@valerena
Copy link
Contributor Author

I believe we're going to have follow up PRs to support this properly?

Yes, this is just to split the changes across different smaller increments for now

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.

2 participants