4 ms·
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?
by 0x008 4y ago
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 4y agoIn 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 4y agoyes I get it. Good point. Is bazel also a good choice for managing the virtual environments of my developers? Do you have any examples?
- jvolkman 4y agoAt this point I would say no, but work is in progress to improve in this respect [1]. At my place of work we use some rules [2] to build virtual envs from Bazel dependencies. It's been a great stop-gap for us and allows us to use traditional Python tooling (e.g. PyCharm) with Bazel-managed dependences. [1] https://github.com/aspect-build/rules_py https://github.com/aspect-build/rules_py [2] https://github.com/cedarai/rules_pyvenv https://github.com/cedarai/rules_pyvenv