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

[proposal] using towncrier for merge-friendly changelog management
by Ronny Pfannschmidt May 4, 2017

May 4, 2017

Hi all, today i noticed how pip manages its change-logs in a pretty interesting way, they manage the fragments to be composed before a release in the folder "news" in files named like "$ticketnumber.$changetype" before a release those files get take out and composed into the change-log. The fabulous tool behind that is https://github.com/hawkowl/towncrier/ - after taking a first look at it, i believe it should be a massive enhancement compared to what we put ourselves trough right now. i also would be delighted, if we used it in more projects ^^ cheers, Ronny

3 7

[3.1 feature] "assert not raise exception" helper: opinions about the name
by Bruno Oliveira April 26, 2017

April 26, 2017

Hi all, We are about to land on the features branch an implementation of the proposal outlined by Florian Bruhin ( https://github.com/pytest-dev/pytest/issues/1830) where we introduce a small helper to facilitate writing parametrized tests that sometimes raise an error for an input parameter and sometimes don’t: @pytest.mark.parametrize('inp, expectation', [ (-1, pytest.raises(ValueError)), (3.5, pytest.raises(TypeError)), (5, pytest.does_not_raise), (10, pytest.does_not_raise), ])def test_bar(inp, expectation): with expectation: validate_positive_integer(inp) The pytest.does_not_raise helper actually does nothing, is meant solely to help writing this type of parametrized test. The PR is at https://github.com/pytest-dev/pytest/pull/2339 and is ready for merging, but this email is about *how to name it* since we had some debate about it. We have this proposals so far: - pytest.does_not_raise; - pytest.not_raises; - pytest.wont_raise; So we would like to ask for opinions here because nailing down the name is important. *Another question* is if someone sees a problem in making it a singleton like in the example above, or if we should force users instantiate it each time: pytest.does_not_raise(). Cheers,

12 34

doc/docs.pytest.org now proper with https
by holger krekel March 29, 2017

March 29, 2017

Thanks to Florian Schulze who instantiated an nginx/letsencrypt proxy on the planet.pytest.org pytest now serves ssl directly (https://docs.pytest.org ) directly by proxying and reverse-proxying to readthedocs.org. But we need an email admin address -- i can create a "pytest-admin(a)pytest.org" alias which forwards to a couple of committers and we could also mention it in the contacts page. Makes sense? holger

3 3

Travis auto-cancellation enabled
by Bruno Oliveira March 27, 2017

March 27, 2017

Hi everyone, Travis introduced "auto-cancellation", meaning that if a new commit is pushed to a branch or PR, any queued builds for the previous commit in that branch or PR is cancelled automatically. I think this is a great idea as it avoids building older commits which are probably no longer relevant. More information here: https://blog.travis-ci.com/2017-03-22-introducing-auto-cancellation I decided to go ahead and enable this as I believe it is a win-win situation, but if somebody disagrees please let me know. Cheers, Bruno.

2 1

Mozilla Open Source Support
by Thomas Lotze March 24, 2017

March 24, 2017

Hi, I just noticed that the next deadline for applications for Mozilla Open Source Support awards will be due soon, at the end of the month. Also, pytest (as well as tox) is listed among the projects Mozilla considers Foundational technology which it supports through a dedicated awards track. https://wiki.mozilla.org/MOSS https://wiki.mozilla.org/MOSS/Foundational_Technology/Projects_We_Use I wonder whether the pytest project should apply for an award. This question has been brought up on this mailing list before, at least last summer by Florian Bruhin. The discussion back then didn't lead to a conclusion, more-or-less open questions being what well-defined project objective to propose, who could work on it, and, not the least important, what Holger thought of it as the money would likely be handled by his company. Florian Schulze was the only one who said he was available full-time at the time. Now, I'm aware that I've not been known as a pytest contributor so far, but I've been using pytest, I want to help improve it in turn, and I'm interested in and available for working on open-source Python projects on the basis of funding such as the MOSS awards. This is why I'd like to re-raise the question of applying for such an award, and ask you who else might be interested in joining the work and what would be the best objectives to have funded. "Reducing the number of bugs" would be useful but possibly too much of general maintenance to be eligible for an award. There are a number of enhancement proposals in the tracker, some of which will be more urgent or helpful to the project than others, or might lend themselves better to being implemented by one or two persons rather than, e.g., during a sprint. If there is any interest in applying for a MOSS award, I'd be happy to work on an application during the next few days. But if there is a feeling that pytest shouldn't apply for an award, or not this time, I'd be equally interested in discussing that and possibly preparing for next time. I'd particularly like to ask the opinions of Holger, and of Dave Hunt, who is listed as the project's contact within Mozilla on the above-mentioned list. Thank you! Cheers, Thomas

4 4

[proposal] big flake8 cleanup before the 3.1 release
by Ronny Pfannschmidt March 17, 2017

March 17, 2017

Hi all, before releasing 3.1 i would like to bring pytest up to coding standards while not all agree on the exact rules of flake8, i find it an insult to my eyes to that basically all tools that don't/can't support all kinds of config files pretty much show about half of pytest in violation all the time what i certainly don't want to do, is start to disable code standard enforcement on random projects, so i want to enforce it - and that means fixing up pytest once and for all. a good point in time would e to do it on the features branch right before doing a release and merging back to master as it would create the smallest merge effort. additionally it would allow us to switch from travis for linting to a dedicated service with better gh integration in future without maintaining yet another massive exclude list -- Ronny

4 3

Sprint this summer?
by Oliver Bestwalter March 17, 2017

March 17, 2017

Hi all, just want to get the ball rolling and ask if planning has started already and how I can help. This is mainly triggered by a question here: https://github.com/tox-dev/tox/issues/485 Would it maybe be feasible to coordinate this together with the EuroPython this year? Cheers, Oliver

5 5

pytest 3.0.7 released
by Bruno Oliveira March 14, 2017

March 14, 2017

pytest-3.0.7 ============ pytest 3.0.7 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: * Anthony Sottile * Barney Gale * Bruno Oliveira * Florian Bruhin * Floris Bruynooghe * Ionel Cristian Mărieș * Katerina Koukiou * NODA, Kai * Omer Hadari * Patrick Hayes * Ran Benita * Ronny Pfannschmidt * Victor Uriarte * Vidar Tonaas Fauske * Ville Skyttä * fbjorn * mbyt Happy testing, The pytest Development Team

1 0