Hi Bruno, i intend to keep the external facade for usage the same, alsi i want to keep the api on items
however i intend to break the api on the concrete objects -- Ronny ----- Original Message ----- From: "Bruno Oliveira" <[email protected]> To: "Ronny Pfannschmidt" <[email protected]>, [email protected] Sent: Tuesday, March 22, 2016 12:25:46 PM Subject: Re: [pytest-dev] Refactoring/fixing markers Hi Ronny, That would be nice, I think it is OK to use a branch in the main repository. I wonder though if we can keep the same general interface though, but we can discuss this over the code once you have something in place. :) Cheers, On Tue, Mar 22, 2016 at 6:14 AM Ronny Pfannschmidt <[email protected]> wrote: > Hi Everyone, > > the current marker implementation has a massive bugs/issues wrt > application of markers "smearning" across class boundaries > due to marker transfer (which is basically completely broken). > > In order to elevate the issue, i'd like to change how markers are viewed > by test items, > > the idea is to completely remove them from the actual objects, except for > pytestmark collections on modules/classes/functions > > items would then get a merged view of markers that apply to them without > ever copying/changing the marker collections of the applying objects > > this would change the external interface for markers, thus requiring a > major version (pytest-3.0) > so i#d like to request a branch on the main repo expressing that intent. > > > > i'm planning to implement this in the next 1-2 weeks. > > -- Ronny > _______________________________________________ > pytest-dev mailing list > [email protected] > https://mail.python.org/mailman/listinfo/pytest-dev > _______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
