Currently, our python backend strongly depends on anaconda to manage the environment + packages. This results in a lack of dev/prod separation.
Solution: Use poetry as a python package manager tool to better define our dev/prod dependencies.
Create pyproject.toml file in the poetry-setup branch. the initial file is created, but you will have to populate the dependencies (look in conda/environment.yml or requirements.txt for inspiration)
add python dependencies to be used in dev or prod mode
update python build check github actions to use poetry to setup environment
update dockerfiles to use poetry to setup environment
Ensure that if u install a python dependency, the pyproject.toml file is updated (we don't want to manually add dependencies to environment.yml file or requirements.txt)
Goal: our frontend and backend both have package manager support that automatically gives the updated set of dependencies for setting up frontend and backend services
Currently, our python backend strongly depends on anaconda to manage the environment + packages. This results in a lack of dev/prod separation.
Solution: Use
poetry
as a python package manager tool to better define our dev/prod dependencies.pyproject.toml
file in thepoetry-setup
branch. the initial file is created, but you will have to populate the dependencies (look inconda/environment.yml
orrequirements.txt
for inspiration)pyproject.toml
file is updated (we don't want to manually add dependencies toenvironment.yml
file orrequirements.txt
)Goal: our frontend and backend both have package manager support that automatically gives the updated set of dependencies for setting up frontend and backend services
Branch setup instructions:
if that doesn't work, try the following