In this branch, I am working on replacing the currentpip-tools-based build system with a Poetry-based one.

As of now, all the containers start up OK in my development environment. I have deleted therequirements directory. I have introduced Poetry and updated the Dockerfiles and all other dependent files I've come across so far, accordingly. I have not tested the behavior of the Runtime or Dagster (beyond confirming their web UIs load) and have not run the automated tests locally (they run OK on GitHub Actions, though).

Details

I'll add some details here when this branch is further along.

It seems to me that multiple programs — all of whose code is managed in this repo — share a single dependency list (meaning, there's one bucket of dependencies/packages that different applications pull from as they need something, but that bucket containsall dependencies ofall programs). That may be another opportunity for simplification/cleanup here: separate the different programs (e.g. Dagster stuff, maybe eventually the standalone Minter) out into their own Poetry projects. We can discuss this.

Note: The Mongo migration notebooks donot share a dependency list/bucket with the rest of the applications in the repo. Those notebookshappen to live in the repo, but don't have any dependency upon anything in the repo outside of their own directory (they depend only on either packages definedwithin that directory, or packages hosted on PyPI).

Related issue(s)

Fixes#563

Related subsystem(s)

• Runtime API (except the Minter)
• Minter
• Dagster
• Project documentation (in thedocs directory)
• MongoDB migrations
• Other

Testing

• I tested these changes (explain below)
• I did not test these changes

I confirmed that whatever tests GitHub Actions runs, all pass.

Documentation

• Ihave not checked for relevant documentation yet (e.g. in thedocs directory)
• I haveupdated all relevant documentation so it will remain accurate
• Other (explain below)

Maintainability

• Every Python function I defined includes a docstring(test functions are exempt from this)
• Every Python function parameter I introduced includes a type hint (e.g.study_id: str)
• All "to do" or "fix me" Python comments I added begin with either# TODO or# FIXME
• I usedblack to format all the Python files I created/modified
• The PR title is in the imperative mood (e.g. "Do X") and not the declarative mood (e.g. "Does X" or "Did X")