-
-
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
regression: testdir fixture not found with pytester plugin loaded #9280
Comments
Right, I'll send a PR to revert this commit, see this discussion on why I added it. Maybe @RonnyPfannschmidt has an idea how to salvage it though. Anyway it's not too bad without it. |
…sponding plugins are registered" This reverts commit e6eac28. This approach doesn't work when pytester is loaded thru a conftest `pytest_plugins`. Fixes pytest-dev#9280.
Let's register pytester legacy in the pytest plugin registred hook so we auto enable when pytester gets activated We need a condition on the plugin |
The idea is to eventually move the plugin to be standalone, so I prefer the approach to be compatible with that. Can you think of a trick that would keep it localized to the legacypath plugin? Hmm maybe use |
Exactly that 😅 |
I should learn to read :) (I read it as loading the sub-plugin from the pytester plugin) |
Fixes pytest-dev#9280. Previous approach didn't support pytester being loaded using `pytest_plugins = "pytester"` in a conftest.
After #9208, this:
fails with:
I bisected this to e6eac28.
Considering this as a showstopper for 7.0 given that this is a very common way of accessing the
testdir
fixture.cc @bluetech
The text was updated successfully, but these errors were encountered: