Sylvain Marié

Hi @fabaff coming back to you about this issue: how does it sound to run the tests of each package in a venv/virtualenv ? Would it solve your circular deps...

Thanks @Gutifarra for pushing pytest-cases to the limits ! `pytest` has foundamental limitations in its design that prevent most of the use cases in `pytest-cases` to be achievable without hacking...

Thanks for the feedback and kind words @Gutifarra ! I'll leave the ticket open so that we can process it later then.

Thanks @sgbaird for your question. A simple way to tackle the issue would be to revert the problem: you first create a parametrize fixture that returns a pair of objects...

A case function is "just" a `pytest_cases.lazy_value` fed to a `@pytest_cases.parametrize`, or a fixture. It is turned into one or the other depending on whether it requires parametrization. Below you...

> Below you can find info on lazy values, but the more I think about it, the more I think that the simple way is to detect generator cases and...

Note that #170 may solve this by supporting parametrized `lazy_value`s

One aspect that needs not to be forgotten is how easy the parameter of a case function can be accessed afterwards. With the current situation (parametrized cases = fixtures) it...

Thanks a lot @andioz for the feedback ! From the `pytest` [documentation link](https://docs.pytest.org/en/6.2.x/pythonpath.html) that you point out: > `--import-mode=importlib` [...] makes test modules non-importable by each other. [...] Users which...

Indeed, fair point. I confirm that `import-mode=prepend` works since this is the default. The pytest team says that this will not disappear, it will just not be the default anymore....