[llanowarelves]

You're right.

The thing I want is a good monorepo solution for Python. There's at least 3 for JavaScript.

As much hate as JS gets, its package managers are also much better than Pip.

In order to manage complexity of Python as you do your big projects, you really need to do "enterprisey" patterns like DI. Even though it's rare for Python programmers to write like that.

Re: test runner: pytest is pretty good

[jvolkman]

What are you looking for in a monorepo solution?

[0x008]

probably managing requirements.txt of sub-projects and virtual environment management?

[jvolkman]

This is possible with existing general monorepo tools. We use Bazel for Python and other languages. With Python, we have a single requirements.txt at the root of the monorepo, but each target (a Python package, a module, an app, or some combination thereof) depends only on the packages it needs and the transitive packages of its dependencies.

Then if you need to do something like build a distributable archive for your app (say, to deploy it to lambda), you can use Bazel's dependency graph to get only the packages that the app transitively depends on.

[0x008]

What about the opposite case? I have several python packages with one requirements.txt each. But for development I want to have a single “root” virtual env?

[jvolkman]

In that case it seems like you could just have one all_requirements.txt that includes the individual files like:

  -r package_a/requirements.txt
  -r package_b/requirements.txt

etc.

[0x008]

yes I get it. Good point.

Is bazel also a good choice for managing the virtual environments of my developers? Do you have any examples?