Seeking Guidance: Future Plans for Package Management (Poetry vs uv) in dbterd

[syou6162]

Is your feature request related to a problem? Please describe:

Currently, dbterd's library management is being done using poetry, and CI tests are still executed with poetry. However, a recent commit introduced uv as a potential tool for package management. This has created uncertainty regarding which tool should be used moving forward. Additionally, it's unclear if dependencies need to be maintained in both poetry and uv simultaneously.

Describe the solution you'd like:

• Clarification on whether dbterd plans to continue using poetry, switch to uv, or use both tools for package management.
• If the plan is to transition to uv, I would like to contribute by submitting a pull request to replace poetry with uv in the CI process.

Describe alternatives you've considered:

An alternative approach would be to transition entirely to uv and remove poetry to ensure dbterd developers do not face confusion regarding which tool to use. Clear guidelines on managing dependencies with uv alone would help provide a consistent development experience.

Additional context:

• CI workflow using poetry
• Commit introducing uv

[datnguye]

Thanks @syou6162

I would love to migrate poetry+poe to uv+poe!
Actually I tried it months ago but was not successful, the main reason was that uv have not suported to bump version using git tag approach, see astral-sh/uv#6298.

However, if you’d like to give it a try now, you are more than very welcome. The main key use cases of poetry are:

• Seamlessly manage the dev environment with venv
• Manage the python libs’ version
• Release pip package on git tag creation
• (Optional) Manage the extra packages
• (poe) Manage tasks — this is not the blocker because we can use poe in uv though