Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deprecate load_setuptools_entrypoints #154

Open
RonnyPfannschmidt opened this issue May 23, 2018 · 4 comments
Open

deprecate load_setuptools_entrypoints #154

RonnyPfannschmidt opened this issue May 23, 2018 · 4 comments

Comments

@RonnyPfannschmidt
Copy link
Member

entry-point loading should be moved into a interface where one passes the entry-point system (either pkg_resources or entry_points), the plugin-manager and the entrypoint name into a helper that facilitates registration

@nicoddemus
Copy link
Member

Good idea, this will make pluggy more useful in contexts outside the setuptools ecosystem.

@goodboy
Copy link
Contributor

goodboy commented May 25, 2018

@RonnyPfannschmidt what would be some other examples for alternative registry namespaces?
I find building out a general API at least requires a couple examples.

Maybe the filesystem-conftest.py listed pytest_plugins variables as discovered with pytest?

@RonnyPfannschmidt
Copy link
Member Author

RonnyPfannschmidt commented May 25, 2018

@goodboy im not aware of any - the distribution<>entryoint mapping things is just something that is generalizable as a next step

@goodboy goodboy added this to the 1.0 milestone Nov 9, 2018
@anxuae
Copy link

anxuae commented Mar 9, 2020

Hello,

I'm wondering if it is possible that the helper can load a plugin from a path to a python module?
This will help to load plugin form user who don't fully mastering in packaging using setuptools.

for instance a function load_entrypoints(pm, entrypoint), the entrypoint could be a key as defined in setuptools or a path to a python module to be loaded.

The module imp could be used to load the module.

BR
anxuae

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants