Hi everyone,

in https://github.com/pytest-dev/pytest/pull/3317 i introduced a new way to
store marks and aslo consistently use it (this fixed a few bugs pytest
dragged along since years)

some of the things i had to do is introduce a internal FunctionDefinition
node that's currently just being used by the collectors to give metafunc
correct access to marks.

i'm hoping to eventually elevate that in future,
but the amount of spaghetti makes that a major undertaking,
pytest is just so tightly coupled all over the place that it is suffocating
and really error inducing

I also did deprecate markinfo attributes,
so everyone using them will get deprecation warnings.

as far as i'm concerned, markinfo attributes where never ever a correct way
to handle distinct marks and quite a few bugs in pytest came from using
combined marks in markinfo instead of distinct marks.

i also changed get_marker, and starting to realize that i need to make it
return a MarkInfo again (at least one with correct data this time around)
(that's upcoming in a few)

other than that please take a look and find details to scrutinize

-- Ronny

-- 

Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael
O'Neill, Eric Shander
_______________________________________________
pytest-dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pytest-dev

Reply via email to