Closed
Description
Feature Request / Improvement
Currently, pyiceberg 0.8.0
enforces strict Python version constraints (python = "^3.9, <3.13, !=3.9.7"
).
While I understand the reasoning behind this - Python 3.13 hasn't been officially tested and supported yet - this constraint creates some practical limitations.
The main issue is that it prevents early adopters and developers from testing or using pyiceberg with newer Python versions, as package managers like poetry
and pip
will strictly enforce these version constraints and block the installation.
Given that:
- Major releases of pyiceberg can take up to 5 months
- Minor releases can take up to 1.5 months
- Early testing with newer Python versions can help identify compatibility issues sooner (see Bump PyArrow to 18.0.0Β #1256 (comment))
I suggest removing the <3.13
constraint from the Python version specification. This would allow developers to:
- Test pyiceberg with pre-release Python versions
- Identify potential compatibility issues earlier
- Continue using pyiceberg in environments with newer Python versions (at their risk)
- Provide feedback about compatibility issues
Metadata
Metadata
Assignees
Labels
No labels