Ape hijacks pytest, not allowing pytest to be used independently or pytest-xdit to be used

Environment information

Ape version was beta 0.1.3 and this issue surfaced before plug-in installation.

• Python Version: 3.8
• OS: macOS

I’m using poetry with ape as a dev dependency.

What went wrong?

When I run poetry run pytest ape reports “no provider name test” After that I switched to running poetry run ape test, which worked fine as a replacement. However, recently started using pytest-xdist for test parallelization and when running poetry run ape test -n auto, the same error occurs. Had to uninstall ape to be able to test directly with pytest.

How can it be fixed?

Fill this in if you have ideas on how the bug could be fixed.

[Pet3ris]

Thanks @unparalleled-js - I did this on a non-ape repo:

poetry add --dev git+https://github.com/unparalleled-js/ape.git#fix/test-race-cond
poetry run pytest

Can confirm it works now, which didn’t work on main.

[unparalleled-js]

Maybe to add more color on the consequences of using global package state from a python module: I used a conda environment to create a poetry env for ape development. After uninstalling ape to be able to use pytest parallelization (the issue above), I created another poetry env based on this conda environment. However, this env still has ape_test and ape and I cannot uninstall them. Moreover it seems to have modified some internal pytest registry so I’m not able to test. I had to delete the conda env altogether 😦.

I don’t understand why ape is still installed in a new environment; that must be related to conda?. For now, to turn off the ape-test pytest plugin, you either have to use ape in separate environment or use the -p no:ape_test option when invoking pytest.

https://stackoverflow.com/questions/37924489/how-to-disable-pytest-plugins-for-single-tests