fix: bump lmdb to 1.7.1 for Python 3.14 wheel#100
Open
GursheenK wants to merge 1 commit into
Open
Conversation
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
Confidence Score: 5/5This looks safe to merge.
|
| Filename | Overview |
|---|---|
| pyproject.toml | Updates the lmdb version constraint to use the newer 1.7.x release line. |
Reviews (1): Last reviewed commit: "fix: bump lmdb to 1.7.1 for Python 3.14 ..." | Re-trigger Greptile
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
lmdb~=1.5.1has no prebuilt wheel for Python 3.14 and fails to compile from source, because the C extension callsPyObject_AsReadBuffer, an API that was removed in CPython 3.14. This brokebench setup requirementssince the suite app couldn't build. Bumping tolmdb~=1.7.1pulls a version that ships a cp314 wheel while keeping the stable 1.x API the suite code relies on.