Releases: DavidVujic/poetry-multiproject-plugin
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.
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
fix(check-project): from top folder
Fix: mypy analyser running properly when check-project from top folder with the --directory
option.
Pull Request #23
fix: add support for global options
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 #21
fix: check-project command with reusable venv
Use the Poetry global cache-dir for the temporary virtual environment that is created during check-project. This will speed up the process, and avoid unnecessary network calls.
Pull Request #19
fix: check-project command
Fixes the check-project command that didn't work as intended.
More info in Pull request #18
new command: check-project
This command is mainly useful to check for any missing dependencies or packages in code for a project. It uses MyPy under the hood.
Pull Request: #17
Add support for Python 3.8
Minimum Python version (3.10), Community standards, CI
v1.0.4 add CircleCI badge