I went back and fourth on this, but ultimately decided that it's more trouble
than it's worth. Between false positives, deeply nested packages raising
vulnerabilities, and the brittleness of the poetry-plugin-export that the
tooling relies on, it causes more headaches than it avoids. A future PR will
enable dependabot tooling that will open PRs to automatically fix this problem
so I don't have to deal with it anymore (hopefully)
Add the _poetry submodule to support importing Poetry internals at runtime rather
than import time. This allows the plugin to be run, and either skipped or errored,
without crashing tox
When running 'poetry remove tox-poetry-installer' in the same env as
poetry is installed to, poetry will uninstall itself. This is, obviously,
not ideal.
This change makes poetry an optional dependency so that the plugin can be
installed (and uninstalled) alongside poetry in the same env without
breaking the poetry installation. The intention is that the plugin can be
installed with the 'poetry' extra when being installed to an isolated environment
where poetry is not otherwise available.
This is a mitigation of Issue #2 as an alternative to vendorization of the enitre
poetry project 😬
Add precommit hook for checking for merge conflicts
Add dev dep for blacken-docs
Add dev dep for pre-commit-hooks
Update all precommit hooks to use system language
Update toxfile to use new dev deps
Fix tox vs. precommit conflicts with reorder-python-imports
Poetry 1.1 is due any day and when it does much of the functionality this
module uses will be moved to poetry-core. Until this module is updated
to use poetry-core 1.1 will be a breaking change