[pytest-dev] pytest-commit emails

Hi everyone, I receive an email from [email protected] whenever new merges happen on a branch of the pytest repository, but it seems it happens only for my own merges. It was my understanding I should receive for any merge, not just my own. Does this happen for anybody else or is it just m

[pytest-dev] "Reference" page is up!

Hey everyone, I've merged the PR which includes a long-time-requested Reference page, check it out at: *https://docs.pytest.org/en/latest/reference.html * It might have some missing bits still, in which case feedback is welcome! Cheers, Bruno. __

Re: [pytest-dev] "Reference" page is up!

Wonderful resource, great to have it all in one place. Thanks! Christian On Thu, Mar 15, 2018 at 10:20 AM, Bruno Oliveira wrote: > Hey everyone, > > I've merged the PR which includes a long-time-requested Reference page, > check it out at: https://docs.pytest.org/en/latest/reference.html > > It

[pytest-dev] pytest 3.5 soon?

Hi everyone, pytest 3.4 was released on 2018-01-30, and we had agreed that we should make a new minor release every 2 months or so to allow users to enjoy the new features and fixes in the “features” branch. For 3.5 one of the major features was to replace the internal warning subsystem by the bu

Re: [pytest-dev] pytest 3.5 soon?

+1 the next big things i will try to work on are * a new marker api and * a actually correct config initialization   (the one we currently do is broken and creates bugs in xdist) i hope to get a part in for 3.5 but i believe most of the important things will need 3.6 -- Ronny Am 15.03.2018 um

Re: [pytest-dev] pytest 3.5 soon?

On Thu, Mar 15, 2018 at 4:26 PM RonnyPfannschmidt < [email protected]> wrote: > +1 > > the next big things i will try to work on are > > * a new marker api and > * a actually correct config initialization > (the one we currently do is broken and creates bugs in xdist) > Sounds goo

[pytest-dev] Fixture ordering and scopes

Hi everyone and Holger, Looking at the code below: data = {} @pytest.fixture(scope='session')def clean_data(): data.clear() @pytest.fixture(autouse=True)def add_data(): data['value'] = 1 @pytest.mark.usefixtures('clean_data')def test_foo(): assert data.get('value') Should test_foo f

Re: [pytest-dev] No traceback filtering with __tracebackhide__ attribute using custom pytest plugin

Hi Ringo, On Tue, Mar 13, 2018 at 6:47 AM Ringo De Smet [email protected] wrote: > Am I right in saying that the pytest_runtest_makereport hook from > runner.py is the one calling into the filtering of the traceback and using > the __tracebac

Re: [pytest-dev] Fixture ordering and scopes

Bruno, Please, merge that PR! caveat: I have not reviewed the code. However, ... I get numerous questions about it, and I always tell people to create artificial dependencies between fixtures that need to run in a certain order. The general mental model that people have for fixtures is that they

Re: [pytest-dev] Fixture ordering and scopes

I too have observed this weird ordering. I would like like the order of fixtures to always respect the order of scopes. On Thu, Mar 15, 2018 at 6:47 PM, Brian Okken wrote: > Bruno, > > Please, merge that PR! > caveat: I have not reviewed the code. > > However, ... > I get numerous questions abou

Re: [pytest-dev] preparing a breaking internal change - splitting Session into the node and the plugin

Hi everyone, On Fri, Mar 9, 2018 at 10:46 AM RonnyPfannschmidt < [email protected]> wrote: > > > I wouldn't take a major release to cram in as much changes as possible. > > IMHO it's fine to have a major release for just one breaking change. > > That way it's easier to manage possib

Re: [pytest-dev] pytest 3.5 soon?

Am Donnerstag, den 15.03.2018, 19:30 + schrieb Bruno Oliveira: > On Thu, Mar 15, 2018 at 4:26 PM RonnyPfannschmidt annschmidt.de> wrote: > > > > > > > > > > +1 > > > > the next big things i will try to work on are > > > > > > > > * a new marker api and > >