click-plugins
click-plugins copied to clipboard
click-contrib
Register CLI commands via setuptools entry-points.
Using the `@with_plugins()` decorator generates a type error in PyCharm (but *not* with mypy) when using `CliRunner.invoke()`: In the above code, removing the `@with_plugins()` decorator also removes the type error....
If any package dependency is not met the entry point fails to load. Even if this does not impact the functioning of the CLI at all Could this be replaced...
This adds support for passing an endpoint name to `with_plugins()`, as proposed in https://github.com/click-contrib/click-plugins/issues/13: - If the `plugins` parameter is a string, it's interpreted as an endpoint name and `pkg_resources.iter_entry_points()`...
As indicated by https://github.com/pypa/setuptools/issues/510, `pkg_resources` is known to be slow. `click-plugins` leverages `setuptools` entry points to load CLI plugin commands but this comes with a performance hit for the entire...
I can adapt the tests etc. If you agree that this is a workable way and if this issue is indeed a problem you don't want to see. Fix #31
There really isn't a need for the user to be doing: ``` python from pkg_resources import iter_entry_points from click_plugins import with_plugins @with_plugins(iter_entry_points(entry.point)) ``` When they could just do: ``` python...
`pkg_resources` is [deprecated](https://setuptools.pypa.io/en/latest/pkg_resources.html), it would be nice have the docs clarify how to use `click-plugins` with `importlib_metadata` / `importlib.metadata` instead. > ATTENTION > > Use of pkg_resources is deprecated in...
Metadata
Owner
Metadata
Register CLI commands via setuptools entry-points.