Hello,
I appreciate the introduction of hatch and what it offers. But of course we are all looking for a build-tool which can do everything.
So I ask, since it is very common with microservice based architectures, is the usage of Monrepos somehow a concern in the design of hatch?
I mean instead of a structure like this:
package
├── module
├── tests
└── pyproject.toml
having something like this:
package_a
├── module
├── tests
└── pyproject.toml
package_b
├── module
├── tests
└── pyproject.toml
with the requirement of
- having also shared project dependecies, i.e.
pytest and similar which are shared among all sub projects and are automatically installed in to each projects dev dependencies
- quickly switching projects (i.e. virtual environments)?
- executing tests automatically in each separate virtual environment?
Hello,
I appreciate the introduction of hatch and what it offers. But of course we are all looking for a build-tool which can do everything.
So I ask, since it is very common with microservice based architectures, is the usage of Monrepos somehow a concern in the design of hatch?
I mean instead of a structure like this:
having something like this:
with the requirement of
pytestand similar which are shared among all sub projects and are automatically installed in to each projects dev dependencies