fix(mypy): use latest minor of v1

Using the latest MyPy v1 version to avoid downgrades in CIs that don't allow the recommended poetry self add plugin way.

Details in Pull Request #48

fix: update lock files

Details in Pull Request #46

fix: bump sub-dependencies (poetry lock file)

Details in #43

fix: extend ignore patterns

Extend the ignore copy pattern for the build-project and check-project commands.

More details in #39

Allow paths for top namespace

feat: add paths support when running poetry build-project with the --with-top-namespace flag.

⭐ This feature was added by @ryaminal ⭐
Thank you!

Details in Pull Request #34

fix: TOML parsing on Windows and Poetry 1.5

Fixing issue in #30

Thank you for reporting this error ⭐ 👏

More details about the change in PR #31

fix(build-project: accidentally overwritten default build options

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

More details in Pull Request #29

feat: rewrite top namespaces for relative includes when building packages

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

fix(check-project): avoid unnecessary files

Making the check-project command faster. Details in Pull Request.

fix(check-project): install mypy in temp virtual environment

More details in Pull Request