Hi everyone,

after trying for a while to sanely introduce a FunctionDefinition node type,
and failing due to pretty nasty coupling in the code,

i decided i will introduce inheritance compatible marker apis in a
different way

this will mean a slight mess due to the lack of some important correct
places for marks,
but it will allow to finally use marks correctly at least

the main problem point will be the transfer of marks from call
specs/parameterized calls
to normal functions

as usually when the legacy mark api are involved, type and structure of
the involved data is not just wrong but inherently hostile to reliable

so even when going for a less sensible structure to get it trough in a
smaller package i expect some horrendous fallout.

-- Ronny

pytest-dev mailing list

Reply via email to