Poetry-multiproject-plugin

Fixing the issue reported in 28 - thank you for reporting this! ⭐

More details in Pull Request 29

Supporting the use case for publishing PyPI package(s) from a Python Monorepo arranged according to what's suggested in this repo, and with Polylith.

When projects includes shared packages, they will have the same top namespace. This can be a problem when libraries, that originates from projects built from the same monorepo, will be installed into the same virtual environment.

Since Python libraries are installed in a "flat" folder structure, two libraries with the same top namespace will collide.

This release will offer a solution to this, by choosing a custom namespace to be used in the build process. Then organize the namespaced packages, and more importantly, re-write the imports made in the source code.

[Pull Request](https://github.com/DavidVujic/poetry-multiproject-plugin/pull/27)

Making the `check-project` command faster. Details in [Pull Request](https://github.com/DavidVujic/poetry-multiproject-plugin/pull/26).

More details in [Pull Request](https://github.com/DavidVujic/poetry-multiproject-plugin/pull/25)

Fix: mypy analyser running properly when check-project from top folder with the `--directory` option.

Pull Request https://github.com/DavidVujic/poetry-multiproject-plugin/pull/23

Adding support for the --directory option in build-project and check-project
Adding support for the --verbose option in check-project, because this command mutes output by default

Pull Request https://github.com/DavidVujic/poetry-multiproject-plugin/pull/21