Consider MRO when obtaining marks for classes When using pytest markers in two baseclasses Foo and Bar …
Consider MRO when obtaining marks for classes When using pytest markers in two baseclasses Foo and Bar …: a task in Lego-RL-SWE-Bench-Verified (Harbor dataset). If it is widely understood that all markers are part of a single attribute, I guess you could say that this is just expected behavior as…
The task
If it is widely understood that all markers are part of a single attribute, I guess you could say that this is just expected behavior as per MRO. However, I'd argue that it would be more intuitive to attempt to merge marker values into one, possibly deduplicating marker names by MRO.
Part of Lego-X/Lego-RL-SWE-Bench-Verified.