Mailman 3 December 2017 - pytest-dev

[proposal] experiment with adapting gitmate.io for automating issue maintenance/triaging tasks
by Ronny Pfannschmidt Jan. 18, 2018

Jan. 18, 2018

Hi Everyone, a while back the people behind gitmate.io did interview me to expand their perspective with focus on how pytest does things as well as how i do certain things at work, they also provided me with a basic example on what i would have done for pytest: https://gitmate.io/report/https:%2F%2Fgithub.com%2Fpytest-dev%2Fpytest i beleive it would help to free up a lof of volunteer time from issue triaging to start and use such a tool. -- Ronny

5 7

Proposal: Move adamchainz/pytest-randomly to pytest-dev/pytest-randomly
by Adam Johnson Dec. 17, 2017

Dec. 17, 2017

As Bruno suggested to me*, I'd like to propose moving pytest-randomly into the pytest-dev organization. I'd still be the main maintainer :) https://github.com/adamchainz/pytest-randomly I believe the plugin checks off all the items in the checklist: https://github.com/pytest-dev/pytest/blob/master/CONTRIBUTING.rst#submittin… Thanks! * https://github.com/adamchainz/pytest-randomly/issues/94 -- Adam

3 4

Re: [pytest-dev] [proposal] experiment with adapting gitmate.io for automating issue maintenance/triaging tasks
by Florian Bruhin Dec. 11, 2017

Dec. 11, 2017

On Mon, Dec 11, 2017 at 01:31:05PM +0100, Ronny Pfannschmidt wrote: > Hi, > > when i noticed that bit i was a bit shocked as well, > for pytest i mitigated the issue by switching the commenting user to > pytestbot > > its really a shocking misfeature to me that by default a *real person* > is used as the bot user. > > Luckily i could just switch it to the pytestbot for pytest and its much > less of an issue there. > Had it commented as **me** that would have been an absolute deal breaker > for me. Yeah, I probably need to find out how to make it use some @qutebot or so as well... Also see https://gitlab.com/gitmate/open-source/gitmate-2/issues/244 Florian -- https://www.qutebrowser.org | me(a)the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/

2 1

pytest 3.3.1 released!
by Bruno Oliveira Dec. 6, 2017

Dec. 6, 2017

Hi everyone, pytest 3.3.1 has just been released to PyPI. This is a bug-fix release, being a drop-in replacement. To upgrade:: pip install --upgrade pytest The full changelog is available at http://doc.pytest.org/en/latest/changelog.html. Thanks to all who contributed to this release, among them: * Bruno Oliveira * Daniel Hahler * Eugene Prikazchikov * Florian Bruhin * Roland Puntaier * Ronny Pfannschmidt * Sebastian Rahlf * Tom Viner Happy testing, The pytest Development Team

1 0

pytest _pytest/mark.MarkMapping behavior
by Yury Krasouski Dec. 5, 2017

Dec. 5, 2017

Hello Team, To begin with, I would like to say "Thank You" for great tools. I am writing here to ask question about _pytest/mark.MarkMapping behavior which was used in one plug-in. I noted that API is changed a little what produced issue like this: https://github.com/reportportal/agent-python-pytest/issues/37 The fix is simple at first look: just replace _marks to own_mark_names. But I wonder about inconvenient behavior of > def __getitem__(self, name): > return name in self.own_mark_names I would expect to call list(MarkMapping) which will return list of mark names, but instead this returns infinite iterator which produced False (or True in some cases). What is the reason for such behavior? Thanks, Yury

3 3

Re: [pytest-dev] Question about fixtures and the use of finalizers vs yield
by Ernesto D. Luzon Jr. Dec. 4, 2017

Dec. 4, 2017

PyTest fixtures using addfinalizer() become convenient when you want to make them work in RobotFramework as well. def fixture_being_used_in_robotframework(): closure = "details of how to cleanup the fixture" def clean_up(): print(closure) return clean_up @pytest.fixture() def reuse_robotframework_fixture(request): request.addfinalizer(fixture_being_used_in_robotframework()) Cheers, Ernesto > > Message: 3 > Date: Mon, 4 Dec 2017 11:49:24 +0000 > From: Dr Keith M Franklin <keith.franklin(a)gmail.com> > To: pytest-dev(a)python.org > Subject: [pytest-dev] Question about fixtures and the use of > finalizers vs yield > Message-ID: <D7E4FF9A-6EE8-404B-8654-C1F7EE9E47A3(a)gmail.com> > Content-Type: text/plain; charset=utf-8 > > > Good morning/afternoon, > > I hope this is the right place to post this. I?ve been using PyTest for a > while but recently come across someone else?s fixture which made me wonder > if I?m doing this right. Basically I?ve been creating a fixture like and > adding a finalizer like so: > > @pytest.fixture(scope=?function?) > def my_fixture(request): > # Code that does something e.g. creates a database record > rec = DBObject() > > def clean_up(): > # Code required to clean up the fixture code and return the state > back to the > ... > request.addfinalizer(clean_up) > return rec > > > However, I?ve seen fixtures written using yield instead e.g. > > > @pytest.fixture(scope=?function?) > def my_fixture(request): > # Code that does something e.g. creates a database record > rec = DBObject() > yield rec > > # Code required to clean up the fixture code and return the state back > to the > ... > > Can I ask, is there any real difference between the two approaches? Is > there a preferred method and if so why? > > Thanks in advance for any help. > > Keith > > ------------------------------ > > Message: 4 > Date: Mon, 04 Dec 2017 12:14:42 +0000 > From: Bruno Oliveira <nicoddemus(a)gmail.com> > To: Dr Keith M Franklin <keith.franklin(a)gmail.com> > Cc: pytest-dev(a)python.org > Subject: Re: [pytest-dev] Question about fixtures and the use of > finalizers vs yield > Message-ID: > <CA+RQFff9Cx-P_Vs4jcU=cCQHy=mwuuRauU0vQEv7wdF=cZKv+A@mail. > gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi Keith, > > Both approaches are valid and identical; I personally prefer using yield > because to me it feels more natural. > > Cheers, > >

3 2

Question about fixtures and the use of finalizers vs yield
by Dr Keith M Franklin Dec. 4, 2017

Dec. 4, 2017

Good morning/afternoon, I hope this is the right place to post this. I’ve been using PyTest for a while but recently come across someone else’s fixture which made me wonder if I’m doing this right. Basically I’ve been creating a fixture like and adding a finalizer like so: @pytest.fixture(scope=‘function’) def my_fixture(request): # Code that does something e.g. creates a database record rec = DBObject() def clean_up(): # Code required to clean up the fixture code and return the state back to the ... request.addfinalizer(clean_up) return rec However, I’ve seen fixtures written using yield instead e.g. @pytest.fixture(scope=‘function’) def my_fixture(request): # Code that does something e.g. creates a database record rec = DBObject() yield rec # Code required to clean up the fixture code and return the state back to the ... Can I ask, is there any real difference between the two approaches? Is there a preferred method and if so why? Thanks in advance for any help. Keith

2 1

Proposal: Move davehunt/pytest-metadata to pytest-dev/metadata
by Dave Hunt Dec. 4, 2017

Dec. 4, 2017

I’d like to propose moving the pytest-metadata plugin to pytest-dev. It’s a dependency for pytest-html, which is already in the pytest-dev organisation, so I believe this makes sense. I would still be the owner/maintainer, but it means that if I’m unavailable then others could land emergency fixes. The repository is configured to deploy after a successful Travis CI build whenever a tag is pushed, so anyone with push access would be able to release a new version. https://pypi.python.org/pypi/pytest-metadata/ <https://pypi.python.org/pypi/pytest-metadata/> Cheers, Dave

5 8