Mailman 3 May 2017 - pytest-dev

Suggestion: EuroPython pytest/tox/devpi helpdesk
by Oliver Bestwalter July 4, 2017

July 4, 2017

Hi all, EuroPython is on the horizon and they have a new thing (or at least new for me) called "helpdesk" > Helpdesk / 10 slots > Helpdesks are a great way to share your experience on a technology, by offering to help people answering their questions and solving their practical problems. You can run a helpdesk by yourself or with colleagues and friends. Each helpdesk will be open for 3 hours in total, 1.5 hours in the morning and 1.5 hours in the afternoon. People looking for help will sign up for a 30 minute slot and talk to you. There is no specific preparation needed; you just need to be proficient in the technology you run the helpdesk for. see: https://ep2017.europython.eu/en/call-for-proposals/ I would be interested to try this and volunteer to help with questions about tox mainly. Would anybody else interested in that kind of thing? If we find a handful of people that would want to do that, we could have a tox/pytest/devpi helpdesk :) Cheers, Oliver

4 13

Re: [pytest-dev] [proposal] introducing attrs to the codebase
by Floris Bruynooghe June 24, 2017

June 24, 2017

Hi, Personally I also don't mind the dependency. Though I know in the past we've had a policy of keeping dependencies to a minimum as well as licenses. Attrs uses MIT as well so that should not be a problem. One thing which does stand out is that attrs is at v16, suggesting they break their API a lot. Since you work with it already I guess you have an idea on whether they've stabilised by now or the changes are not so bad? As an aside, if we're happy to introduce more libraries then maybe we should also consider the standard six package instead of doing our own stuff, mostly because I'd make it easier for new contributors. Regards, Floris On 6 Dec 2016 11:16, "Bruno Oliveira" <nicoddemus(a)gmail.com> wrote: Oh good point Raphael. Here's the link for the discussion about pip dropping Python 2.6: https://github.com/pypa/pip/issues/3955 Cheers, Bruno On Tue, Dec 6, 2016 at 8:57 AM Raphael Pierzina <raphael(a)hackebrot.de> wrote: > Hey there, > > I don’t mind adding a dependency as long as there is a need for it. +1 > > The problem I see with ‘attrs’ as it stands today, is that it does not > support Python 2.6 whereas pytest does. So we probably want to get > https://github.com/pytest-dev/pytest/issues/1273 in before adding ‘attrs’ > as a dependency. I’m not up-to-date with how things are in pip as to > dropping Python 2.6 compatibility. I can’t seem to find a ticket on the pip > issue tracker. > > Best, > Raphael > > On 06 Dec 2016, at 09:52, Bruno Oliveira <nicoddemus(a)gmail.com> wrote: > > Hi Ronny, > > Could you list the classes which you think would be changed to use > 'attrs'? I'm not against adding another dependency if it can help us > maintain the codebase. Also, introducing a new dependency should be done in > `3.1.0`, not in a patch release. > > Cheers, > Bruno. > > On Tue, Dec 6, 2016 at 5:44 AM Ronny Pfannschmidt < > opensource(a)ronnypfannschmidt.de> wrote: > > Hi all, > > i'd like to introduce https://pypi.python.org/pypi/attrs as a > dependency, > > its a fairly usefull library that takes away quite some boilerplate and > common error cause while automatically adding repr, comparators and > similar small details to python classes. > > I have used it in a number of personal projects, and dont want to miss > it by now. > > -- Ronny > _______________________________________________ > pytest-dev mailing list > pytest-dev(a)python.org > https://mail.python.org/mailman/listinfo/pytest-dev > > _______________________________________________ > pytest-dev mailing list > pytest-dev(a)python.org > https://mail.python.org/mailman/listinfo/pytest-dev > > > _______________________________________________ pytest-dev mailing list pytest-dev(a)python.org https://mail.python.org/mailman/listinfo/pytest-dev

4 4

pytest.org redirect request (#2453)
by Bruno Oliveira June 1, 2017

June 1, 2017

Hi everyone, An issue has been raised in the bug tracker asking to redirect docs.pytest.org/latest/* to docs.pytest.org/en/latest/*: https://github.com/pytest-dev/pytest/issues/2453 Whoever has powers to that change the redirect rules could take a look please? Thanks! Cheers, Bruno.

2 1

pytest 3.1.1 released!
by Bruno Oliveira May 31, 2017

May 31, 2017

pytest 3.1.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 * Florian Bruhin * Floris Bruynooghe * Jason R. Coombs * Ronny Pfannschmidt * wanghui Happy testing, The pytest Development Team

1 0

pytest 3.1 warning capture woes
by Bruno Oliveira May 30, 2017

May 30, 2017

Hi everyone, Unfortunately pytest's 3.1 warning capture being active by default has caused grief on some test suites and there's been a lengthy discussion about it on this thread: https://github.com/pytest-dev/pytest/issues/2430 I'm pointing this out here so others can join the discussion and share their thoughts. Also, I'm wondering what should be our next course of action on this. Should we make a new release (3.1.1, 3.2, 4.0?) where this feature is opt-in or if by now it is too late to revert it given that those affected might have already fixed their suites. As a lesson learned here I'm starting to think that we should from now on always introduce new features as opt-in, and if we want to change the defaults do so only on a major release. Would love to hear everyone's opinion on this. Cheers, Bruno.

5 10

pytest-testdirectory fixture
by Morten V. Pedersen May 29, 2017

May 29, 2017

Hi all, Just wanted to share a fixture that we have created for py.test. The purpose of the fixture, is to make it easy to create folders and run commands. E.g. for integration testing small utilities etc. https://github.com/steinwurf/pytest-testdirectory The fixture supports a number of different operations. Hope some of you will find it useful. All the best, Morten

3 4

progressing with fixing mark, a potentially backward compatible path to progression
by RonnyPfannschmidt May 29, 2017

May 29, 2017

Hi everyone, first let me link https://github.com/pytest-dev/pytest/labels/mark-issue those issues give a basic idea on how badly mark is broken and how it breaks things for users (we had some people rewrite their complete testsuites to deal with the fallout of how bad it is) a few basic underpinnings already happened in pytest 3.1 with `pytest.param` and the internal restructuring of marker values whats missing now is to bring marks onto the collection tree not as a bastardized broken and inconsistent version of keywords, but as actual marker objects, without any of the breakages and inconsistencies we see today in order to do that i see a need for a new property on all nodes where the markers of a node are discover-able (get_marker is broken beyond repair i'm not going to fix that before we can get a correct view of marks) this property can then be used to pass over marks of the ndoes, the parent nodes and so on, in order to get a consistent view on markers for an item in order to make this work consistently with parameterization, i will introduce a FunctionDefinition node (and a function-definition scope), that will upon collection apply the parameters (and invoke the generate_tests hook (also now we will be able to give metafunc a correct view of marks) and then a function node will just be the final parameterized call to a function definition, in order to ensure this works nicely, i will introduce a pytestmark property on all marked functions, that acts like the attribute property on classes, but will not be affected by the legacy marker transfer once we have a basic clean data-set for markers on all nodes we can begin to fix up apis like get_marker and/or deprecate as we see need in the next step we can introduce opt-outs of the old and staining marking mechanim and prepare for a truly breaking release -- Ronny

2 2

[proposal] abolishing the features branch
by Ronny Pfannschmidt May 23, 2017

May 23, 2017

Hi everyone, since quite a while now we keep a lot of code away from users by leaving it in the features branch, more recent detail https://github.com/pytest-dev/pytest/issues/2365 where even i didn't realize we had a fix since half a year. >From my point of view it has been demonstrated that we don't deliver well from the features branch, and it has been a massive pain to keep merged with master over and over. As such i would like to stop using a features branch at all and return to having only master. -- Ronny

5 9

pytest 3.1.0 has been released!
by Bruno Oliveira May 22, 2017

May 22, 2017

The pytest team is proud to announce the 3.1.0 release! pytest is a mature Python testing tool with more than a 1600 tests against itself, passing on many different interpreters and platforms. This release contains a number of bugs fixes and improvements, so users are encouraged to take a look at the CHANGELOG: http://doc.pytest.org/en/latest/changelog.html For complete documentation, please visit: http://docs.pytest.org As usual, you can upgrade from pypi via: pip install -U pytest Thanks to all who contributed to this release, among them: * Anthony Sottile * Ben Lloyd * Bruno Oliveira * David Giese * David Szotten * Dmitri Pribysh * Florian Bruhin * Florian Schulze * Floris Bruynooghe * John Towler * Jonas Obrist * Katerina Koukiou * Kodi Arfer * Krzysztof Szularz * Lev Maximov * Loïc Estève * Luke Murphy * Manuel Krebber * Matthew Duck * Matthias Bussonnier * Michael Howitz * Michal Wajszczuk * Paweł Adamczak * Rafael Bertoldi * Ravi Chandra * Ronny Pfannschmidt * Skylar Downes * Thomas Kriechbaumer * Vitaly Lashmanov * Vlad Dragos * Wheerd * Xander Johnson * mandeep * reut Happy testing, The Pytest Development Team

1 0

Is anyone at PyCon2017 in Portland?
by Dan Nealschneider May 21, 2017

May 21, 2017

Is anyone else at PyCon2017? Are there open issues we could work on during the Sprints?

1 0