Hi,

in order to prepare switching --looponfail over to pytest-cache
i created some branches in the main repos

while doing that i also removed --boxed from xdist

related pull requests are * https://bitbucket.org/hpk42/pytest-cache/pull-request/12/move-in-looponfail-from-xdist * https://bitbucket.org/hpk42/pytest-xdist/pull-request/14/kill-looponfail-and-boxed/diff

in particular looponchangeroots might need some more discussion about semantics


i already prepared a potential replacement for --boxed in pytest-boxed (which is not yet released, maybe sometime later today)

the current set changes requires to update xdist and cache at the same time

to keep backward compatibility better,
i could move the actual --looponfail option to xdist
and set up the requirements of xdist to contain boxed/cache
in order keep the same feature set availiable

main question is do we want to enforce update at once
or have a more gradual process
(i'm in favor of a more disruptive change but,
i know many of you have compatibiliy concernsto take into consideration)

-- Ronny
_______________________________________________
pytest-dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pytest-dev

Reply via email to