imbajin opened a new pull request, #248:
URL: https://github.com/apache/incubator-hugegraph-ai/pull/248

   This commit transitions the entire repository to use `uv` for Python package 
management, replacing the previous mix of Poetry, pip with requirements.txt, 
and setup.py files.
   
   Key changes include:
   
   - All subprojects (`hugegraph-python-client`, `hugegraph-ml`, 
`hugegraph-llm`) now use `pyproject.toml` for package metadata, dependency 
specification (PEP 621), and build configuration.
   - `hugegraph-llm` has been migrated from Poetry to use `uv` with a standard 
`pyproject.toml`. Poetry-specific files (`poetry.lock`) and configurations have 
been removed.
   - `hugegraph-python-client` and `hugegraph-ml` have their dependencies and 
package information consolidated into their respective `pyproject.toml` files, 
removing `setup.py` and `requirements.txt`.
   - Path dependencies between local projects (e.g., `hugegraph-llm` and 
`hugegraph-ml` depending on `hugegraph-python-client`) are defined in their 
`pyproject.toml` files.
   - GitHub Actions CI workflows (`hugegraph-python-client.yml`, `pylint.yml`) 
have been updated to use `uv` for installing dependencies from `pyproject.toml` 
files and their cache keys have been updated accordingly.
   - Documentation (README files for each subproject and relevant guides) has 
been updated to reflect the new `uv`-based installation and development 
procedures.
   
   This unification simplifies dependency management, standardizes the build 
process across the repository, and leverages the performance benefits of `uv`.


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to