Hi, I know you weren't asking me, but I do lurk on the mailing list. I think pulling invocation scoped fixtures for the 3.0 release is an awesome solution for now. If this were a commercial software system this feature would be regarded as a nice to have feature for the release. Meaning it doesn't get to hold up shipment to get fixed.
My two cents. BTW. Thanks for all the hard work to get 3.0 out, and all the previous work you've done on the project. - Brian Okken > On Aug 14, 2016, at 6:15 PM, Bruno Oliveira <[email protected]> wrote: > > Hi everyone, > > I've worked on the weekend on the issue discovered by Florian on the > qutebrowser test suite, and unfortunately I think the current implementation > will have to be re-thought because it contains a serious problem regarding > finalizers when fixtures are being overwritten. > > Because redesigning it might take a awhile, I suggest we remove invocation > fixtures for now so we can make the 3.0 release. We can then work this week > on the remaining issues[1] and make a release candidate by the middle of the > week, aiming for the official release by the end of the week. > > How does that sound? > > Cheers, > Bruno. > > [1] https://github.com/pytest-dev/pytest/milestone/2 > > > _______________________________________________ > 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
