jiangxt2 opened a new issue, #14395:
URL: https://github.com/apache/gravitino/issues/14395

   ### Describe the subtask
   
   Migrate environment management for the Python client's development, test, 
documentation, and package-build workflows to uv, with reproducible dependency 
installation while preserving supported Python versions, SDK behavior, and 
runtime dependency contracts. Users can continue installing the published SDK 
with pip.
   
   #### Scope
   
   - [ ] Provide a documented uv development workflow with a committed lockfile.
   - [ ] Migrate the Gradle environment setup, lint, and unit-test entry points.
   - [ ] Migrate ordinary Python client integration tests and their CI entry 
points.
   - [ ] Migrate the dedicated Ray/Iceberg environment and CI entry points.
   - [ ] Migrate the Lance/Ray compatibility matrix while preserving isolation 
by Python version and dependency combination.
   - [ ] Migrate documentation and release-build environments, then remove the 
Python client build and test entry points' dependency on Miniforge.
   
   #### Acceptance criteria
   
   - A fresh checkout can select a supported Python version, install locked 
dependencies, generate version metadata, and run the documented workflow. 
Changes to requirement files invalidate cached package metadata.
   - Migrated Gradle/CI entry points and affected real service, Ray/Iceberg, 
and Lance/Ray tests pass using the intended isolated environments.
   - Documentation builds complete using the migrated environment.
   - Built artifacts preserve package versions, dependencies, extras, license 
files, and generated version files. Local release-build rehearsals cover the 
build paths affected by this migration; validation does not require publishing 
packages, creating remote tags, or initiating a release.
   
   Keep Gradle as the build entry point, setuptools/setup.py for packaging, and 
the existing requirement files as the dependency declaration source. Runtime 
dependency-range changes remain tracked in #13556. Package metadata 
modernization and additional environment-management frameworks are outside this 
subtask.
   
   All migration PRs should reference this issue; no separate issue is needed 
for each PR.
   
   Related discussion: #7779 and #7811.
   
   ### Parent issue
   
   [EPIC #14334](https://github.com/apache/gravitino/issues/14334)
   
   


-- 
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]

Reply via email to