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

Update to crate-2.0.0, which uses orjson for JSON marshalling #195

Merged
merged 1 commit into from
Jan 16, 2025

Conversation

pyproject.toml Outdated
"crate>=1.0.0.dev2,<2",
"crate>=2.0.0.dev1,<3",
Copy link
Member Author

@amotl amotl Jan 16, 2025

Choose a reason for hiding this comment

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

In order to permit installation of crate-2.0.0, we need to bump the upper version bound anyway. Do you think we should also bump the lower bound, as outlined here?

In principle, we can be lenient and keep crate>=1.0.0. In practice, we can apply a little more force here that when upgrading sqlalchemy-cratedb, crate-python will automatically be upgraded as well.

Copy link
Member

Choose a reason for hiding this comment

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

For me it sounds very fine to increase the lower bound, everything else looks like not worth doing it (I don't really see the need to be able to use an older crate-python version with a newer sqlalchemy dialect)

Copy link
Member Author

Choose a reason for hiding this comment

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

Fine. Let's merge the PR as-is then?

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