Just my 2c, I think I might would be valuable to create two new plugins:
- one which handles local concurrency via multiprocessing (pipes, shmem,
etc.)
- one which handles remote concurrency (sockets, client/server, etc.)
from a usage standpoint I expect the 99% to be the former suggested plug-in
Another one that might be worth taking a peek at is:
https://github.com/ansible/pytest-mp
I've never dug in personally but it always looked promising.
On Thu, Oct 24, 2019 at 4:22 PM RonnyPfannschmidt
wrote:
>
> Hi Freddy,
>
>
> unfortunately pytest-concurrent is fundamentally broken for
Hi Freddy,
unfortunately pytest-concurrent is fundamentally broken for managing
fixtures and other details,
as things are my suggestion is to avoid it.
-- Ronny
Am 24.10.19 um 15:22 schrieb Rietdijk:
Hi,
I think having a simple `pytest-multiprocessing` or
`pytest-concurrent` would be
Hey,
On Thu, Oct 24, 2019 at 09:45:48AM -0300, Bruno Oliveira wrote:
> Because of this, we have been discussing creating a new package,
> pytest-xdist2 (other suggestions are welcome), without any backward
> compatibility guarantees with pytest-xdist.
pytest-[yz]dist? ;)
> pytest-xdist2 would,
Hi,
I think having a simple `pytest-multiprocessing` or `pytest-concurrent`
would be extremely useful and cover a lot of people's use cases and would
strongly recommend to have that as a separate plugin from something bigger
that does feature hooks and/or remote execution.. It seems though as
Hi everyone,
For some time now execnet has been in maintenance only mode, and even so
very few people are willing to maintain it; lately just myself and I’m not
a good choice given that I don’t know the codebase at all, plus I have tons
on my plate already. This poses a problem because often we
