You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Feature Request / Improvement
Currently,
pyiceberg 0.8.0enforces 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
poetryandpipwill strictly enforce these version constraints and block the installation.Given that:
I suggest removing the
<3.13constraint from the Python version specification. This would allow developers to: