Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Refactor marks to get rid of the current "marks transfer" mechanism #2363
Marks currently are transferred between nested Python objects after collection, by mutating the objects themselves. For example, marks applied to classes are copied over all the test methods of the class, being added as attributes of the methods themselves.
@RonnyPfannschmidt has proposed to get rid of the current mark transfer mechanism in favor of a new one where marks are transfered from parent items to children, instead of mutating the Python objects.
@nicoddemus there is various bugs about this one already, the basic elements of mistake are that markers are transvered in a mutating way over boundaries they should NEVER cross and finally end up as "kewords" on items
to correctly fix that one we need to make parameterization part of the collection tree, disengage marks from keywords and work out new internal types to represent marks, and potentially expose them to users in the old fashion (or just remove their old exposure alltogether