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

chore: remove moto from setup. leave in requirements_dev #421

Merged
merged 1 commit into from
Aug 16, 2024

Conversation

stephenkilbourn
Copy link
Contributor

What?

We were seeing cannot import name 'mock_dynamodb' from 'moto because moto made a breaking change on the imports in moto version 5.
We already have moto[dynamodb, ssm]>=4.0.9,<5.0 in the ingest api requirements_dev to address this, but there was an unpinned version in the setup.py. I'm making this change to just have the import with the pinned version in a single location.

@stephenkilbourn stephenkilbourn changed the title chore/ remove moto from setup. leave in requirements_dev chore: remove moto from setup. leave in requirements_dev Aug 15, 2024
@stephenkilbourn stephenkilbourn merged commit 72f446a into develop Aug 16, 2024
4 checks passed
botanical added a commit that referenced this pull request Aug 20, 2024
…ltiple domain names for prod, Improve raster integration tests, remove moto from setup. leave in requirements_dev (#423)

### 🪙 Changed/Updated
- [chore: Improve raster integration tests
#397](#397)
- [chore: remove moto from setup. leave in requirements_dev
#421](#421)

### 🩹 Fixed
- [fix: update domain names to support multiple domain names for
prod](#418 )


<details>
<summary>Authors</summary>

- Co-authored-by: Jennifer Tran
- Co-authored-by: Stephen Kilbourn


</details>
@anayeaye anayeaye deleted the chore/remove-moto-from-setup branch August 28, 2024 21:59
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