-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
pluginmanager does not run consider_module on setuptools plugins #2391
Comments
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', [])) |
@nicoddemus while looking at it, i really wonder about having a concept of dependent plugin again (in pluggy) |
Hmm how would one declare dependencies in that way? I suppose this dependency mechanism would have to work for both |
@nicoddemus off hand i took a look at the way setup-tools plugins work, it cant be directly integrated without changing pluggy |
I might have misunderstood your first comment, but I thought you meant to introduce a way for plugins (loaded either by |
@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 |
Agreed! 👍 |
@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 |
IMO definitely. |
@nicoddemus ok, upcoming pr then ^^ |
That would be in |
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
The text was updated successfully, but these errors were encountered: