Mailman 3 June 2016 - pytest-dev

Moving pytest-rerunfailures to pytest-dev
by Florian Pilz Oct. 27, 2016

Oct. 27, 2016

Hi, I’m asking whether `pytest-rerunfailures` should be moved to the `pytest-dev` organisation (https://github.com/gocept/pytest-rerunfailures <https://github.com/gocept/pytest-rerunfailures>). Since we (gocept) only rarely take time to work on issues / pull requests of `pytest-rerunfailures` we would prefer to move the extremely useful plugin to `pytest-dev`. There we still can work on it, but are not the only ones taking care of the project. So if you think `pytest-rerunfailures` is a great addition to `pytest` and should be moved to the pytest-dev organization, let us know. :) Best wishes Florian ––––––––– Florian Pilz · fp(a)gocept.com · Software Developer gocept gmbh & co. kg · Forsterstraße 29 · 06112 Halle (Saale) · Germany http://gocept.com <http://gocept.com/> · Tel +49 345 122 9889 7 Python, Pyramid, Plone, Zope · consulting, development, hosting, operations

3 8

pytest 3.0 release check list
by Oliver Bestwalter July 11, 2016

July 11, 2016

Hi all, I created a wiki page containing the checklist for the 3.0 release that resulted from our discussion during the sprint. https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist I think that is better than opening an issue, because everybody involved can update the page directly and if there is still some discussion necessary regarding concrete topics an issue can be opened for that concrete topic. cheers Oliver

3 2

Re: [pytest-dev] Request for additional plugin maintainers on PyPI
by Floris Bruynooghe June 28, 2016

June 28, 2016

Oops, lost the pytest-dev cc. Apologies On 28 Jun 2016 18:13, "Ronny Pfannschmidt" <rpfannsc(a)redhat.com> wrote: > I'd be happy to have that, but Travis is very limited just as our > resources are > Am 28.06.2016 18:04 schrieb "Floris Bruynooghe" <flub(a)devork.be>: > >> Sounds nice, I'm all for more automation! But should devpi not be >> involved somehow? >> On 28 Jun 2016 15:48, "Ronny Pfannschmidt" <rpfannsc(a)redhat.com> wrote: >> >>> if we have a "dedicated" pytest-dev user, and put the password into a >>> travis encrypted field, thing might be reasonably fine >>> >>> >>> >>> 2016-06-28 15:14 GMT+02:00 Floris Bruynooghe <flub(a)devork.be>: >>> >>>> Sadly pypi does not have groups so not as easy. My username is flub >>>> there, probably want to add a few pytest-dev ppl other then me as well tough >>>> On 28 Jun 2016 15:05, "Dave Hunt" <dhunt(a)mozilla.com> wrote: >>>> >>>>> Good idea - done! I’ll still need at least one maintainer for each >>>>> plugin in PyPI. >>>>> >>>>> On 28 Jun 2016, at 14:01, Ronny Pfannschmidt <rpfannsc(a)redhat.com> >>>>> wrote: >>>>> >>>>> Hi dave, >>>>> >>>>> i would like to suggest to just give the pytest core group pr merge >>>>> access, >>>>> >>>>> -- Ronny >>>>> >>>>> 2016-06-28 14:30 GMT+02:00 Dave Hunt <dhunt(a)mozilla.com>: >>>>> >>>>>> Last week the following plugins of mine were moved into pytest-dev: >>>>>> >>>>>> - https://github.com/pytest-dev/pytest-selenium >>>>>> - https://github.com/pytest-dev/pytest-html >>>>>> - https://github.com/pytest-dev/pytest-variables >>>>>> - https://github.com/pytest-dev/pytest-base-url >>>>>> >>>>>> I fully intend to continue to support these plugins myself. The main >>>>>> reason for moving these is to ensure that patches for important fixes can >>>>>> be made without me. I’d also like to add at least one maintainer for each >>>>>> of these projects in PyPI so that releases can be pushed without me. >>>>>> >>>>>> Please respond with your GitHub username if you would like to be >>>>>> added as a developer for any of the above plugins, and your PyPI username >>>>>> if you would like to be considered as a maintainer (so you can push new >>>>>> releases). At this time I would like to restrict new developers and >>>>>> maintainers to pytest core committers. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> -- >>>>>> *Dave Hunt* >>>>>> Automation Engineer >>>>>> Mozilla Corporation >>>>>> dhunt(a)mozilla.com >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> pytest-dev mailing list >>>>>> pytest-dev(a)python.org >>>>>> https://mail.python.org/mailman/listinfo/pytest-dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, >>>>> Commercial register: Amtsgericht Muenchen, HRB 153243, >>>>> Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> pytest-dev mailing list >>>>> pytest-dev(a)python.org >>>>> https://mail.python.org/mailman/listinfo/pytest-dev >>>>> >>>>> >>> >>> >>> -- >>> >>> Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, >>> Commercial register: Amtsgericht Muenchen, HRB 153243, >>> Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander >>> >>>

1 0

readthedocs building?
by Brianna Laugher June 28, 2016

June 28, 2016

Hi, Since this got merged https://github.com/pytest-dev/pytest/pull/1656 but http://pytest.readthedocs.io/en/latest/ still shows the fundraising banner... does anyone know why? I thought it built a new version on each commit. Brianna -- They've just been waiting in a mountain for the right moment: http://modernthings.org/

2 1

Request for additional plugin maintainers on PyPI
by Dave Hunt June 28, 2016

June 28, 2016

Last week the following plugins of mine were moved into pytest-dev: https://github.com/pytest-dev/pytest-selenium <https://github.com/pytest-dev/pytest-selenium> https://github.com/pytest-dev/pytest-html <https://github.com/pytest-dev/pytest-html> https://github.com/pytest-dev/pytest-variables <https://github.com/pytest-dev/pytest-variables> https://github.com/pytest-dev/pytest-base-url <https://github.com/pytest-dev/pytest-base-url> I fully intend to continue to support these plugins myself. The main reason for moving these is to ensure that patches for important fixes can be made without me. I’d also like to add at least one maintainer for each of these projects in PyPI so that releases can be pushed without me. Please respond with your GitHub username if you would like to be added as a developer for any of the above plugins, and your PyPI username if you would like to be considered as a maintainer (so you can push new releases). At this time I would like to restrict new developers and maintainers to pytest core committers. Thanks, -- Dave Hunt Automation Engineer Mozilla Corporation dhunt(a)mozilla.com

3 5

Request to bundle Pytest-finer-verdicts as a default plugin with pytest
by Venkatesh Prasad Ranganath June 27, 2016

June 27, 2016

Hey All, What is the process to make this happen? Is the first step to transfer pytest-finer-verdicts <https://github.com/rvprasad/pytest-finer-verdicts> to pytest-dev organization? If so, please consider this email as the request for transfer. Cheers, Venkatesh-Prasad Ranganath http://about.me/rvprasad

4 5

pytest-3.0 / tox-2.4 release plans
by holger krekel June 25, 2016

June 25, 2016

hi from the pytest/tox sprint ... here is the current plan (keyword points) for getting pytest-3.0 and tox-2.4 finalized. It's WIP and we aim to complete as much as possible today. best. h. tox-conda/roadmap/development discussion: - (TBD) two pending PRs - (TBD) 2.4.0 relase (to be released end June) - (TBD) write doc draft for conda integration (hooks + ini) - (TBD) move to github pytest-3.0 discussion: - TO BE RELEASED BEFORE EUROPYTHON2016 -- between 11th and 14th definitely part of 3.0 - new --setup-only, --setup-plan options - (Steffen, Danielle, TBD) reporitng hooks for fixture setup/teardown - (DONE) new main entry point pytest (and py.test) - (TBD) remove py.test-X* entrypoints (with changelog entry) - (TBD) doc restructuring - (TBD) display pytest warnings by default (one line per warning) - (TBD) remove all deprecated command line options for 3.0 - (TBD) fixture conftest sharing / fixture namespace control, draft suggestion document - (TBD) merged fixtures becomes a doc draft (raphael, me) - (TBD) introduce deprecation docs based on oliver's sprint lightning talk - (TBD, Omar, Ted, Daniel) new option "--override-ini|-o ININAME=INIVALUE" to overrides ini values from the command line so that one can do e.g. "-o xfail_strict=True". We don't change the default. - (TBD) see about issuing a deprecation warning for yielding test functions - (TBD, Floris) remove reinterp assert maybe in 3.0: - (TBD) invocation-scope: e.g. monkeypatch and mocker would be useable from any scope. Will be marked experimental for 3.0. rather later than 3.0: - (rather later than 3.0) merge pytest-warnings module and route internal pytest warnings through python's warning system and integrate the pytest-warnings plugin into core (bruno, ronny will discuss) - holger/floris' original pycon work with "markdef" to introduce a markdef decorator to process all mark creations should go to 4.0 - yielding test functions: we could deprecate using setup state in yielding test functions so they can only be used for parametrization other issues: __multicall__: don't remove for 3.0 marks refactoring / PR merge (ronny, omar...) - ronny's refactoring should be closed and redone: - either first just move code - or do changes in mark.py - as to whitespace/flakes/pep warnings: do that while changing code anyway but no big pure whitespace/style changes xfail strict behaviour by default? not doing it for 3.0 - introduce xflaky in docs and as a synonmym for xfail(strict=False) (needs more discussion)

1 0

sprint alias for latest sprint logistics
by holger krekel June 16, 2016

June 16, 2016

Hi all, as the sprint is gearing up, i've setup an alias sprint2016 at pytest dot org which has all the people attending. everyone can mail there. If you are attending but haven't received a mail in the last hour let me know personally. Accomodation should be sorted now, so let's hope for good weather soon -- up until sunday it's forecasted as a bit rainy, then better. best, holger

1 0

Re: [pytest-dev] On-the-ground sprint communication
by Tom Viner June 15, 2016

June 15, 2016

On 15 June 2016 at 10:45, <pytest-dev-request(a)python.org> wrote: > Date: Wed, 15 Jun 2016 11:45:25 +0200 > From: Florian Bruhin <me(a)the-compiler.org> > > > Signal or WhatsApp group chat? Something else? > > For easier written communication at the sprint (i.e. with everyone > there) I suggest IRC, because many already have that set up and it's > the lowest common denominator. > > As for before that, I know Holger uses Signal, and I use Telegram and > Threema as well. Or XMPP/IRC. Then again I probably won't find my > German SIM card anyways so I won't have any internet connection ;) > > Florian > Ok, let's go with Signal then. I've put my number here: https://github.com/tomviner/pytest/wiki/On-the-ground-comms-for-sprint-2016 I'll tune into the irc too.

1 0

On-the-ground sprint communication
by Tom Viner June 15, 2016

June 15, 2016

Hi all, I'm arriving in Freiburg Saturday afternoon, and wondering how best to communicate for arranging meeting up and getting dinner / Sunday activities etc. Some app that makes my phone beep upon receiving a message would be handy :-) Signal or WhatsApp group chat? Something else? Looking forward to seeing everyone and some German cuisine! Cheers, Tom

2 1