[pytest-dev] pytest 2.8.1 issue status and blockers
holger at merlinux.eu
Mon Sep 28 17:35:37 CEST 2015
On Mon, Sep 28, 2015 at 08:06 +0200, Ronny Pfannschmidt wrote:
> Hi everyone,
> over the weekend i had some time to do grooming and attempted a few
> fixes and did issue grooming
> the 1.8.1 milestone is down to 4 open issues
> * a fix in pluggy is on the way thanks to Brono!
that is fixed now (although differently than with Bruno's PR).
> * that pull request is currently not merge-able since it brings back
> regressions we fixed pre-2.8, but the items it fixes are critical
> we def want that in
> Buck did a great job of discovering the cause and doing the fixes,
> unfortunately his refracting went too far and reintroduced an internal
This shouldn't block IMO -- also i am not sure what the original
> * is a regression we def want to fix
I couldn't yet reproduce -- the issue is missing an example or details.
Let's generally ask people to provide an example that fails when
they post "pytest does not work with my project".
> * is not critical but nice to have documentation, ideally fixed in union
> with #1073
right, not a blocker.
As it stands, i don't see any blocker where I could effectively work on.
Given that current master fixes a number of issues there is not much
point in blocking 2.8.1 if you ask me.
> i consider #1060 is a release blocker, but it has a very high backward
> break potential as is,
> however i cant work on it myself this week,
> we can either try to include it or should make a big note as a known
> issue and try to do another patch release as soon as its ready
> current time-frames look like we should mark it as known issue
> -- Ronny
> pytest-dev mailing list
> pytest-dev at python.org
about me: http://holgerkrekel.net/about-me/
More information about the pytest-dev