[WIP] load_entrypoint_plugins option/marker

[blueyed]

Alternative to #4518.

[RonnyPfannschmidt]

that looks like a good start well done, the necessary hacking you had to do inside of the config initialization points to yet another area for the config object detanglement

[blueyed]

The config hack would not be required if self.pluginmanager.load_setuptools_entrypoints("pytest11") would be more modular (

pytest/src/_pytest/config/__init__.py

Line 824 in d1221f1

self.pluginmanager.load_setuptools_entrypoints("pytest11")

).

Given that this adds is_blocked for this, we could also override load_setuptools_entrypoints in PytestPluginmanager and skip them there.

But like asked in #4518 already: how to enable this for all of pytest's inner tests then?
Should pytester forward this? If so, should it use an env or default args?

[nicoddemus]

Thanks @blueyed!

Please take a look at my comments. Other than that, we should add the option to the reference page.

[nicoddemus]

It will be a bummer to write one, but I guess we should add a functional test for this?

[blueyed]

Yeah, tests are fine.. :D

[nicoddemus]

Please use type="args" here to force this to always be a list.

[blueyed]

Rebased, and used type=args.

I came across this again, since pytest-pdb also gets used in inline runs and then throws an error if an attribute exists already.

[nicoddemus]

Hey @blueyed,

Closing this for the same reasons as the other PRs, feel free to re-open it if you're still interested. 👍