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

pluginmanager does not run consider_module on setuptools plugins #2391

Open
RonnyPfannschmidt opened this Issue May 4, 2017 · 11 comments

Comments

Projects
None yet
2 participants
@RonnyPfannschmidt
Member

RonnyPfannschmidt commented May 4, 2017

while turning a local set of modules into a entry-point based pytest plugin i discovered that for based setuptools plugins we dont run consider_module

i'd like to clarify if we want/dont want to do that and how to warn users about that

@hpk42 @nicoddemus ping

@nicoddemus

This comment has been minimized.

Member

nicoddemus commented May 4, 2017

I think for consistency it should, unless there's a hidden reason which I'm not aware about.

For quick reference:

    def consider_module(self, mod):
        self._import_plugin_specs(getattr(mod, 'pytest_plugins', []))
@RonnyPfannschmidt

This comment has been minimized.

Member

RonnyPfannschmidt commented May 4, 2017

@nicoddemus while looking at it, i really wonder about having a concept of dependent plugin again (in pluggy)

@nicoddemus

This comment has been minimized.

Member

nicoddemus commented May 4, 2017

Hmm how would one declare dependencies in that way? I suppose this dependency mechanism would have to work for both pytest_plugins and setuptools plugins.

@RonnyPfannschmidt

This comment has been minimized.

Member

RonnyPfannschmidt commented May 4, 2017

@nicoddemus off hand i took a look at the way setup-tools plugins work, it cant be directly integrated without changing pluggy

@nicoddemus

This comment has been minimized.

Member

nicoddemus commented May 4, 2017

I might have misunderstood your first comment, but I thought you meant to introduce a way for plugins (loaded either by setuptools or the pytest_plugins mechanism) to declare dependencies on other plugins. If that's correct, I'm not sure how plugins declared using pytest_plugins would declare that they depend on other plugins.

@RonnyPfannschmidt

This comment has been minimized.

Member

RonnyPfannschmidt commented May 4, 2017

@nicoddemus lets keep the generalized future concept out of the current issue

triggering registration, and being aware of dependencies orders are quite different beasts

as of now py.test has neither, both play into each other, but the triggering of registration should be a lot more simple

@nicoddemus

This comment has been minimized.

Member

nicoddemus commented May 4, 2017

as of now py.test has neither, both play into each other, but the triggering of registration should be a lot more simple

Agreed! 👍

@RonnyPfannschmidt

This comment has been minimized.

Member

RonnyPfannschmidt commented May 4, 2017

@nicoddemus as current measure, should we ensure that for all plugin modules we do consider_module ?

that would allow to consolidate various importation details into a plugin registration hook

@nicoddemus

This comment has been minimized.

Member

nicoddemus commented May 4, 2017

as current measure, should we ensure that for all plugin modules we do consider_module ?

IMO definitely.

@RonnyPfannschmidt

This comment has been minimized.

Member

RonnyPfannschmidt commented May 4, 2017

@nicoddemus ok, upcoming pr then ^^

@nicoddemus

This comment has been minimized.

Member

nicoddemus commented May 4, 2017

That would be in features right? Right on time for 3.1 then. 😉

This was referenced Mar 6, 2018

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