Mailman 3 February 2017 - pytest-dev

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

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

Reviving pytest-commit
by Floris Bruynooghe Feb. 20, 2017

Feb. 20, 2017

Hi all, Those of you subscribed to pytest-commit may have noticed I tried to revive it as it had been dead since the github migration. On an unrelated issue I noticed I actually used this a fair bit when it was working. Sadly github will only send us commit messages instead of full diffs by default. To get it to email full diffs we'd have to run a service somewhere which github can poke as webhook or something, which seems a bit a pain to setup and maintain. If anyone is aware of an easier way do speak up, otherwise I might not bother for now, unless lots of people would want it. Regards, Floris

2 1

Google Summer of Code
by Ana Ribeiro Feb. 10, 2017

Feb. 10, 2017

Hello Fellows, Applications to Google Summer of Code to organizations are open! We should apply as Pytest! https://summerofcode.withgoogle.com/ I think I can help with the application (Writing it), but I can not be an organization admin because I am eligible to apply as a student and I think I'll do that (either applying to Mozilla or Pytest). Best Regards, Ana

7 23

request for feedback, pytest-suites - a plugin to execute a subset of tests
by Bryan Berry Feb. 7, 2017

Feb. 7, 2017

Hey folks! I have made a little plugin that makes it easier to executes subsets of your tests. I would very much appreciate your feedback on it. https://github.com/bryanwb/pytest-suites This plugin determines which tests belong in a suite by applying UNIX-style glob to the test function name. A suite consists of a name, pattern (glob) or patterns, and additional metadata. First, add pytest-suites to your conftest.py # conftest.py pytest_plugins = ['suites'] Next you will likely want to define a suite or two. Also do this in ``conftest.py`` # conftest.py from pytest_suites import add_suite add_suite(name="smoke", pattern="*basic*") add_suite(name="advanced", pattern="*") add_suite(name="extended", pattern="*", tags={'mode': 'extended'}) Meanwhile, add some tests: # my_test.py def test_basic_feature1(): assert True def test_basic_feature2(): assert True def test_advanced_feature1(): assert True def test_advanced_feature1(): assert True Use the command-line option ``--suite SUITE`` to specify the suite Executing ``pytest my_test.py --suite smoke`` will only execute the tests `test_basic_feature1` and `test_basic_feature2`. pytest-suites provides a mechanism for running tests to learn what suite is currently being executed and access the suite's tags dictionary. This can be useful when you want to occasionally test less or greater functionality within a given test. For example, you may frequently want `test_my_feature` to check the common case but right before a release you may the same test to be more exhaustive. def test_advanced_feature1(suite): mode = suite.tags.get('mode', 'basic') if mode == 'extended': # test exhaustively assert do_expensive_operation() else: # test the common case assert True That's pretty much it! there is a little more info on the github page. I plan to publish this to pypi shortly.

1 0