I don't get the "broke the API" part of this issue. What used to work and doesn't now? Is this really significant enough to warrant bumping to 4.0. Are you ready to follow through with the deprecating promise of https://docs.pytest.org/en/latest/backwards-compatibility.html so soon after the introduction of 3.0?
How many people are affected by this change compared to the confusion of having to explain to everyone what the major feature(s) of 4.0 is(are)? - Brian Sent from my iPhone > On May 16, 2017, at 12:13 PM, Bruno Oliveira <[email protected]> wrote: > > Hi everyone, > >> On Fri, May 12, 2017 at 7:03 PM Ronny Pfannschmidt >> <[email protected]> wrote: >> with the recent discovery of >> https://github.com/pytest-dev/pytest/issues/2398 which was a result of >> accidentally introducing object as base class in pytest-2.9.1 via >> https://github.com/pytest-dev/pytest/pull/1486 >> >> since https://github.com/pytest-dev/pytest/pull/2179 , which will go >> into pytest-3.1 does the "same" >> i propose considering this as breaking change (since there are subtle >> differences on the python 2 side after all) >> >> while doing that we can also gracefully resolve the regression by >> documenting the earlier accidental change and the new expectations. > > Any thoughts on this proposal? I would like to release the new version this > week if possible, so it would be nice to get this discussion going. :) > > Cheers, > Bruno. > _______________________________________________ > 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
