Describe the feature

Problem:

Keeping a large requirements.txt file is redundant and leads to missing a module or two if they are added/upgraded and requirements.txt is not updated with it.

Proposed Solution:

Using poetry as a package managing tool would be ideal. It can also be used for creating virtual environments, increasing the reproducibility of the project.

A brief overview on how poetry works:

• Project dependencies can be added via poetry add <package-name>, a lock file is generated that keeps track of all the packages that have been installed in the project.
• Any contributor just needs to run poetry install and it will reproduce the environment + packages installed on their system seamlessly.

Poetry docs for reference - docs

Add ScreenShots

A comparison between the workflows.

Record

• I agree to follow this project's Code of Conduct
• I want to work on this issue