Migrate Dependency Management from `pip` to `Poetry`

[nanotaboada]

Description

Currently, the project uses pip with requirements.txt for dependency management. To improve maintainability, dependency resolution, and support multiple environments, we should migrate to Poetry and manage dependencies using pyproject.toml.

This migration will:

• Enable better version pinning and dependency resolution.
• Simplify virtual environment management.
• Provide built-in support for dependency groups (e.g., dev, lint, test).

Acceptance Criteria

• Remove requirements.txt, requirements-lint.txt, and requirements-test.txt.
• Initialize pyproject.toml with Poetry.
• Define dependencies in [tool.poetry.dependencies].
• Define test and lint dependencies in [tool.poetry.group.*.dependencies].
• Ensure dependencies are correctly installed with poetry install.
• Update CI workflow to use poetry install instead of pip install -r requirements.txt.
• Verify FastAPI app runs successfully with Poetry.
• Update README.md with new installation instructions.

References

• 🔗 Poetry Documentation

[doubledare704]

How about to move straight to UV?

[nanotaboada]

Hi @doubledare704!

Thanks for the input. Could you clarify what you mean by UV in this context? I’d love to understand how it compares to the proposed enhancement and what benefits it might bring. Any details or examples you can share would be helpful!

[doubledare704]

Hi @doubledare704!

Thanks for the input. Could you clarify what you mean by "UV" in this context? I'd love to understand how it compares to the proposed enhancement and what benefits it might bring. Any details or examples you could share would be helpful!

As for UV, it is one of several package managers that combines the functions of pyenv. It allows installing different Python versions, creating environments, and locking dependencies for projects in a lock file. It is considered a better tool than Poetry. If you use GitHub Actions, UV has prepared pipeline steps for CI.

[yashovardhan99]

Instead of using a 3rd party tool like poetry or uv, why not use Dependency groups in your pyproject.toml?

It was introduced in PEP 735 and won't lock-in your dependencies to a specific tool.

The syntax simply changes to:

pip install --group [group-name]

For example, in a new project I am working on, I prepared several groups like linting, testing, docs, etc. and then combined them all into a single group called dev.

As for tool support, uv already supports it. Unfortunately, Poetry does not support it yet, though it is planned.