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

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

Looking for help in Hook function ordering
by Son Son Jan. 26, 2017

Jan. 26, 2017

Hi, I am not sure whether I am sending my query to right mailing list or not, however, pls. redirect me if my query contradicts with the purpose of this mailing list. *Query:* I have total 5 independent pytest plugins, however I would like to invoke them in a right order. I tried ‘pytest.hookimpl(tryfirst=true) and pytest.hookimpl(trylast=true), however I don’t know how to align it in order if I have more than 2 plugins. I tried the same, however it is not being invoked in order. =========================== Can someone please provide inputs in this regard? myplugin1.py =========== @pytest.hookimpl(tryfirst=True) def pytest_runtest_setup(self, item): <> @pytest.hookimpl(tryfirst=True) def pytest_runtest_teardown(self, item, nextitem): <> myplugin2.py =========== @pytest.hookimpl(trylast=True) def pytest_runtest_setup(self, item): <> @pytest.hookimpl(trylast=True) def pytest_runtest_teardown(self, item, nextitem): <> myplugin3.py =========== @pytest.hookimpl(trylast=True) def pytest_runtest_setup(self, item): <> @pytest.hookimpl(trylast=True) def pytest_runtest_teardown(self, item, nextitem): <> myplugin4.py =========== @pytest.hookimpl(trylast=True) def pytest_runtest_setup(self, item): <> @pytest.hookimpl(trylast=True) def pytest_runtest_teardown(self, item, nextitem): <> myplugin5.py =========== @pytest.hookimpl(trylast=True) def pytest_runtest_setup(self, item): <> @pytest.hookimpl(trylast=True) def pytest_runtest_teardown(self, item, nextitem): <> Here is <snip> of my pytest.main()… addplugins = [myplugin1,myplugin2,myplugin3,myplugin4,myplugin5] # Here we go: if not sys.argv[1:]: pytest_argv = ["-h"] else: pytest_argv = sys.argv[1:] pyres = pytest.main(pytest_argv, plugins=addplugins)

2 1

pypy rejecting scrambled mails now, action decission needed - proposing pytest-dev@python.org
by opensource＠ronnypfannschmidt.de Jan. 22, 2017

Jan. 22, 2017

Hi all, while trying to upload the 3.0.6 release i encountered a new problem, pypi rejecting scramled author mail addresses. i dont just want to de-scramble the email address and/or just insert something else there without a short consensus. i propose putting pytest-dev(a)python.org there. I will consider this actionable if 2 core devs agree and nobody objects. Regards, Ronny

4 4