Mailman 3 July 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

can we remove the deprecated pytest.config variable assignment before 3.0
by Ronny Pfannschmidt July 21, 2016

July 21, 2016

Hi, while working on config.py i just noted we have that pytest.config assignment around in there for compatibility i'd like to remove it - and wonder if its something thats ok to slip into 3.0 or if we should go for deprecation in the 3 series and removal in the 4 series? -- Ronny -- 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

4 6

EuroPython Talk on pytest 3.0
by Raphael Pierzina July 19, 2016

July 19, 2016

Hi pytest-friends, as we are getting closer to EuroPython and my talk on Pytest 3.0, I would be delighted if you could send me your ideas on what you feel is most important to cover. I will be spending the weekend to work on my talk and send around what I have early next week. https://ep2016.europython.eu/conference/talks/pytest-30 <https://ep2016.europython.eu/conference/talks/pytest-30> Holger sent around a list of features/improvement that we hope to ship with pytest (and tox); search for “[pytest-dev] pytest-3.0 / tox-2.4 release plans” from 25 June. What’s the current status and what do you think will be merged in the next couple of days to be included in the release? Any feedback or questions, please let me know. Cheers Raphael

7 9

Postpone 3.0?
by Bruno Oliveira July 17, 2016

July 17, 2016

Hi pytesters, Our original target date for pytest 3.0 was around this week (just before EuroPython), but it seems we are not going to make it as there are some issues still in the 3.0 check list which have not been merged: https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist My question is if we should delay the release a little bit and give more time to people to work on them for 3.0, or bite the bullet and make the release anyway this weekend/early next week? And if we decide to delay, what people think would be a good time for a new target date? Personally I would rather wait a little more because I consider the remaining issues important to go in 3.0. Btw, I was taking a look at the Pulse page on GitHub ( https://github.com/pytest-dev/pytest/pulse <https://github.com/pytest-dev/pytest/pulse/monthly>) and in the last 7 days we have merged 16 PRs. That's awesome. :) Cheers, Bruno.

6 10

Dependency CI
by Brianna Laugher July 16, 2016

July 16, 2016

Hi, This is a new service thing that is free for open source projects. https://dependencyci.com/ Is it worth investigating for pytest and plugins? cheers, Brianna -- They've just been waiting in a mountain for the right moment: http://modernthings.org/

2 1

Announcing pytest-pdb
by Florian Schulze July 12, 2016

July 12, 2016

Hi! I just released https://pypi.python.org/pypi/pytest-pdb It adds a ``whichtest`` command to pdb. It prints identifying information about the current test you are in. Much easier than looking through the stack trace of ``which`` and it prints info on parameters. Regards, Florian Schulze

2 2

RFC deprecation policy
by Oliver Bestwalter July 11, 2016

July 11, 2016

Hi all, while it's still in the air where I shall place the precious text I thusly have constructed, I would like to give you the chance to comment on it, especially is something is still missing. I tried to keep it as sweet as simple as I could - maybe we should add the command line parameter to shut the warnings up right in there as well (add hint about ``--disable-pytest-warnings``)? Here's the gist: https://gist.github.com/obestwalter/60080d472dc5c0a97ddc265e985f1aae Cheers Oliver

3 3

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

pytest.readthedocs.io pointing to "latest"
by Bruno Oliveira July 8, 2016

July 8, 2016

Hi all, I have configured http://pytest.readthedocs.io/ to point to “latest” by default (which represents master branch) rather than “stable” (which represents “latest release/tag”). I think it makes more sense because usually our changes to the documentation in master don’t change behavior, but are fixes to the “live” documentation like typos, removing the sprint banner, fixing dead links, etc, so makes sense for it to be up-to-date at all times. The only “downside” is that 2.9.3.dev shows up in the CHANGELOG, but I don’t see that as a bad thing, because it is clear that it is the not-released, development version, and one can argue that it is even nice because shows up what’s coming in the next release. Let me know if any of you disagrees or have any other comments. Holger, Any chance of pointing docs.pytest.org to http://pytest.readthedocs.io/ in your server before 3.0? I really would like to have that ready, if possible. :) Cheers, Bruno.

3 3

call for crowd-help with enabling the accurate import of tox issues to github
by Ronny Pfannschmidt July 7, 2016

July 7, 2016

Hi everyone, we want to move tox to github before the next release. however unlike the move of pytest (where we had issues with the mapping of bitbucket usernames to git usernames ) we'd like to get started on that with a more accurate usermap for that purpose i prototyped a small tool to deal with usermaps and apply them to issues however now that it mostly works, the crowd-sourceable problem is apparent, there are dozens and dozens of usernames to verify and mark as correct, renamed or missing i hope for some volunteers to help me over the weekend/some free time to run trough those in some coordination to get a reasonable amount of those marked my current process for the usermap is in https://github.com/RonnyPfannschmidt/bitbucket_issue_migration/tree/master/… and currently many of those are null instead of True or matching, False for missing or a string for telling the new name. my hope is that sunday evening i can present a import that is reasonably complete and acceptable as something we can move to the tox-dev org i created on github afterwards we will just pull the history into the repo and rejoice Regards, Ronny

1 0