Fix pyiceberg-core dev dependency resolution#2442
Merged
Merged
Conversation
kevinjqliu
commented
May 13, 2026
| # Set a PyIceberg lower bound; otherwise the resolver may select the | ||
| # unrelated 0.0.2 stub. | ||
| # Keep pyarrow direct because current pyiceberg[pyarrow] releases depend on | ||
| # pyiceberg-core, which conflicts with this local pyiceberg-core project. |
Contributor
Author
There was a problem hiding this comment.
we need to change pyiceberg[pyarrow] to not pull in pyiceberg-core
Contributor
Author
There was a problem hiding this comment.
| "datafusion==52.*", | ||
| "pyiceberg[sql-sqlite,pyarrow]", | ||
| # Set a PyIceberg lower bound; otherwise the resolver may select the | ||
| # unrelated 0.0.2 stub. |
Contributor
Author
There was a problem hiding this comment.
we need to yank these stubs from pypi
Contributor
Author
There was a problem hiding this comment.
Contributor
Author
|
I tried to bump pytest to 9.0.3 locally (#2326) and it worked! |
This was referenced May 13, 2026
blackmwk
approved these changes
May 13, 2026
blackmwk
left a comment
Contributor
There was a problem hiding this comment.
Thanks @kevinjqliu for this pr!
kevinjqliu
pushed a commit
to apache/iceberg-python
that referenced
this pull request
May 26, 2026
<!--
Thanks for opening a pull request!
-->
<!-- In the case this PR will resolve an issue, please replace
${GITHUB_ISSUE_ID} below with the actual Github issue id. -->
Closes #3356
# Rationale for this change
Update ```pyproject.toml``` so ```pyarrow``` no longer pulls in
```pyarrow-core```. The ```uv.lock``` was also regenerated to reflect
the change of the dependency tree. All test passed in both test and
test-integration. However, in integration 80 test where skipped after
the update,
This is an issue presented in
apache/iceberg-rust#2442
## Are these changes tested?
## Are there any user-facing changes?
<!-- In the case of user-facing changes, please add the changelog label.
-->
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
2 participants
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.
Which issue does this PR close?
What changes are included in this PR?
Update
bindings/pythondev dependencies so uv resolves a real PyIceberg release instead of falling back to the unrelatedpyiceberg0.0.2 stub on PyPI:pyiceberg[sql-sqlite]>=0.11lower bound so the resolver cannot select the 0.0.2 stub.pyiceberg[pyarrow]extra, which depends onpyiceberg-coreand conflicts with this localpyiceberg-coreproject.pyarrow>=17as a direct dev dependency to replace what the dropped extra provided.bindings/python/uv.lockis regenerated with the minimal delta required by these changes; no transitive packages are upgraded.This should resolve the issue we're seeing when upgrading dependencies (#2326, #2287, #2297)
Are these changes tested?