AndreVale69 opened a new pull request, #10024:
URL: https://github.com/apache/gravitino/pull/10024
<!--
1. Title: [#<issue>] <type>(<scope>): <subject>
Examples:
- "[#123] feat(operator): support xxx"
- "[#233] fix: check null before access result in xxx"
- "[MINOR] refactor: fix typo in variable name"
- "[MINOR] docs: fix typo in README"
- "[#255] test: fix flaky test NameOfTheTest"
Reference: https://www.conventionalcommits.org/en/v1.0.0/
2. If the PR is unfinished, please mark this PR as draft.
-->
### What changes were proposed in this pull request?
- **build**: Updated pythonVersion from 3.9 to 3.12 in build configuration
- **client-python**: Dropped Python 3.9 support, now requires >=3.10
- **filesystem**: Corrected parameter passing in mv operation for local
storage
- **docs**: Updated Python version requirements for Gravitino client
- **build**: Updated dependency versions in requirements files
- **pylint**: Disabled `too-many-positional-arguments` rule and cleaned up
test files ([introduced with
v3.3.9](https://pylint.readthedocs.io/en/v3.3.9/user_guide/messages/refactor/too-many-positional-arguments.html))
### Why are the changes needed?
[EOL python 3.9](https://devguide.python.org/versions/#versions)
Fix: #10011
### Does this PR introduce _any_ user-facing change?
Bump python client requirements:
- bump `fsspec` from 2024.3.1 to 2026.2.0
- bump `pyarrow` from 15.0.2 to 23.0.1
- bump `cachetools` from 6.2.1 to 7.0.1
- bump `gcsfs` from 2024.3.1 to 2026.2.0
- bump `s3fs` from 2024.3.1 to 2026.2.0
- bump `ossfs` from 2023.12.0 to 2025.5.0
- bump `adlfs` from 2023.12.0 to 2026.2.0
- bump `black` from 24.4.2 to 26.1.0
### How was this patch tested?
```bash
git clone [email protected]:apache/gravitino.git
# Now default is python 3.12
./gradlew :clients:client-python:build
./gradlew :clients:client-python:test -PskipITs
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
