I have a custom pytest plugin that runs a test remotely. I run pytest with -p my_plugin -p no:python so that it doesn't also run it locally. Since pytest 4.5.0, pytest raises UsageError: plugin python cannot be disabled.
This behaviour was introduced in #5005. I have read through that PR, and its issue #4976, and PR #4965 where the change was originally suggested, but I still don't understand the reason for preventing p -no:python.
The reason I use pytest for this, is because the PyCharm IDE provides pytest integration. With my configuration I can click on a "play" icon next to the test name, and PyCharm runs pytest. PyCharm doesn't allow configuring a custom shell command, hence I've been using pytest.
I have a custom pytest plugin that runs a test remotely. I run pytest with
-p my_plugin -p no:pythonso that it doesn't also run it locally. Since pytest 4.5.0, pytest raisesUsageError: plugin python cannot be disabled.This behaviour was introduced in #5005. I have read through that PR, and its issue #4976, and PR #4965 where the change was originally suggested, but I still don't understand the reason for preventing
p -no:python.The reason I use pytest for this, is because the PyCharm IDE provides pytest integration. With my configuration I can click on a "play" icon next to the test name, and PyCharm runs pytest. PyCharm doesn't allow configuring a custom shell command, hence I've been using pytest.