Change requires-python version in pyproject.toml #924
Merged
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?
Closes #923.
Rationale for this change
The current project allows for a Python version >=3.6, but pyarrow versions >=11.0.0 require Python >=3.7, causing a dependency resolution conflict. This PR adjusts the Python version compatibility to prevent errors during dependency installation in environments using older Python versions (like Python 3.6).
What changes are included in this PR?
Updated the requires-python field in pyproject.toml to reflect Python >=3.7 for better compatibility with pyarrow versions >=11.0.0.
This prevents potential dependency conflicts when installing pyarrow with Python 3.6, which is no longer supported by recent versions of pyarrow.
Are there any user-facing changes?
This change restricts the use of Python versions below 3.7 in the project. Users on Python 3.6 will need to upgrade their environment to use the latest version of the project.