Hi Bruno, i created https://github.com/pytest-dev/pytest/projects/2 as a starting point a while back, but its still far from the botton of things,
My current impression is, that a detailed analysis will take a major block of time. My intentionally inflated estimate is about 1 work week, since everything about config initialization gives me the impression its intertwined. which is why i'd prefer a a iterative approach that's allowed to break things. (i simply cant afford even a 2 day block to get into things, and i certainly don't want to spread it over time as it adds quite some extra overhead for getting back into things) however i still suspect low outside effect overall. -- Ronny Am 21.08.2018 um 14:01 schrieb Bruno Oliveira: > Hi Ronny, > > On Tue, Aug 21, 2018 at 4:00 AM RonnyPfannschmidt > <[email protected] > <mailto:[email protected]>> wrote: > > Hi everyone, > > currently pytest configguration initialization is pretty much broken in > many details, > and as far as i can tell its going to be even more tricky to try and fix > than marks, > > i will not again go trough the pain that i had with marks and want to > sort out a gate > to lift and change detail apis that will be broken. > > > I know what you mean, for example `-p no:logging` does not work on xdist > works for some reason, and that is due to how config and parsing are > initialized. I tried to follow the implementation once while working on > something else, but couldn't figure it out and ended up giving up. > > I think the first step is to actually write down the issues/actions > points, so I propose we start a tracking issue so we can at least start > to list the problems that we want to fix, and then create action points > from there. Or perhaps another media, like a page on the Wiki or a GH > Project? > > Cheers, > Bruno. _______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
