From bubenkoff at gmail.com Sun Feb 1 13:10:57 2015 From: bubenkoff at gmail.com (Anatoly Bubenkov) Date: Sun, 1 Feb 2015 13:10:57 +0100 Subject: [pytest-dev] FOSDEM / Saturday pytest meetup in Bruxelles In-Reply-To: <20150119202430.GI12060@merlinux.eu> References: <20150119202430.GI12060@merlinux.eu> Message-ID: Hi all, i've put discussed stuff into a small overview: *https://docs.google.com/document/d/14mbVs_f5UFypPx5vvaW-Vh_8Xq9XBKeoNrA0dR0fiJI/edit * *feel free to update/comment* On 19 January 2015 at 21:24, holger krekel wrote: > Hi folks, > > as some of you know some pytest devs are going to meet at FOSDEM > in Bruxelles end of the month. ASFAIK, Anatoly Bubenkoff, Brianna Laugher, > Floris Bruynooghe and me are bound to come, anyone else? > > During our meetup i'd like to discuss and work on finalizing > https://bitbucket.org/pytest-dev as the new place for pytest core, py, > pytest-xdist, pytest-cache, ..., tox, repositories and using a unified > contribution process for all of them. > > I'd also like to discuss going for a little crowd-funding project that > automates testing and releasing pytest-dev packages including pushing docs > to the respective sites. Bruno Oliveira has already done some work > for visualizing the pytest-plugin status against the latest pytest release > which can probably be re-used > http://pytest.org/latest/plugins_index/index.html > > As to the location at FOSDEM, I suggest to meetup 4pm around the > Python FOSDEM room: http://python-fosdem.org/#location > I'll probably be there during the day but also have some other > appointments so can't guarantee that. I'll arrive friday evening > but will probably directly go to Pieter Hintjens's flat and only arrive > saturday morning at the conf site. > > best, > holger > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iQEcBAEBAgAGBQJUvWf+AAoJEI47A6J5t3LW45AIAJ36pk7VHXJ/y7t4p//lpLqP > QoJCYNzrdd+F9rN9mccoRR8oPH/i/IRkJgYWmz79oH/WV557HBrX2D4oUE/BsDJ8 > Dpk2hx0sGqAHCylwHxGvMA1mHvNA9HgVdnsynjxHs98D544r/ZqiKQxM0aaoFEtx > ljyEuEV7rkB/LxHHZqRvwnrcnQlPMk9uPgRwKyWRWCvirLXLt7XPOMKMuqb4GaVj > Sm0ibd/PVCnoczlzLeiXRzZvpRe0ohVQqn1VfP6yFTtiNv7UMD6Y/P+ncVgeqrCa > K4G3rVow2mgioWtEAD1hYdqXmLpotYUhZRSmU82WzSbv2+6FAp9TarWDtfJvKPM= > =dsJ1 > -----END PGP SIGNATURE----- > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > > -- Anatoly Bubenkov -------------- next part -------------- An HTML attachment was scrubbed... URL: From brianna.laugher at gmail.com Thu Feb 5 21:50:51 2015 From: brianna.laugher at gmail.com (Brianna Laugher) Date: Thu, 5 Feb 2015 21:50:51 +0100 Subject: [pytest-dev] Let's have an "Adopt pytest month" Message-ID: Hello, So as Anatoly mentioned in the notes from the FOSDEM mini-meetup [1], we talked about if we were interested in actively trying to increase pytest adoption, ie get more open source/free software projects using it. As we know how great pytest is, it seems a shame that more people don't know as well! I had an idea that we could have a "adopt pytest month": pair knowledgeable pytest users together with interested projects, and help them convert their existing test suite, or start one from scratch if they don't really have any tests yet. Holger liked the idea, so that's a start :) It would also be a good way for us to discover "pain points" for new pytest users, for example which areas need better documentation or examples. I was thinking it could be in April: ? February: gather pytest volunteers ? March: advertise and ask for projects interested in taking part ? April: the actual work ? May: survey/write up how it went I imagine that volunteers would commit to spending maybe 2-4 hours a week, for the month. They would probably need to download and install the project, join their mailing list and give advice, maybe write some code such as example tests, conftest options. (Basically: I would not expect you to write all their tests for them!) I don't think you would need to be a pytest super developer or guru. You could even do it as a way of learning something new about pytest yourself. I am happy to try and organise this. I imagine I would do something like this: ? Make a short form to gather details about pytest volunteers (e.g. areas of experience/interest) ? Make a page to put on the pytest website, with info to advertise to potential projects ? Make a short form for projects to apply/register to take part ? Pair volunteers and projects together ? Survey volunteers and projects after the month is over, write a summary of responses So, IF YOU ARE INTERESTED IN TAKING PART: please reply to the list to say so! Also if you have any questions or suggestions, let me know. Thanks, Brianna [1] https://docs.google.com/document/d/14mbVs_f5UFypPx5vvaW-Vh_8Xq9XBKeoNrA0dR0fiJI/edit -- They've just been waiting in a mountain for the right moment: http://modernthings.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From bubenkoff at gmail.com Thu Feb 5 22:31:25 2015 From: bubenkoff at gmail.com (Anatoly Bubenkov) Date: Thu, 5 Feb 2015 22:31:25 +0100 Subject: [pytest-dev] Let's have an "Adopt pytest month" In-Reply-To: References: Message-ID: I'm in! On Feb 5, 2015 9:51 PM, "Brianna Laugher" wrote: > Hello, > > So as Anatoly mentioned in the notes from the FOSDEM mini-meetup [1], we > talked about if we were interested in actively trying to increase pytest > adoption, ie get more open source/free software projects using it. As we > know how great pytest is, it seems a shame that more people don't know as > well! > > I had an idea that we could have a "adopt pytest month": pair > knowledgeable pytest users together with interested projects, and help them > convert their existing test suite, or start one from scratch if they don't > really have any tests yet. Holger liked the idea, so that's a start :) > > It would also be a good way for us to discover "pain points" for new > pytest users, for example which areas need better documentation or examples. > > I was thinking it could be in April: > ? February: gather pytest volunteers > ? March: advertise and ask for projects interested in taking part > ? April: the actual work > ? May: survey/write up how it went > > I imagine that volunteers would commit to spending maybe 2-4 hours a week, > for the month. They would probably need to download and install the > project, join their mailing list and give advice, maybe write some code > such as example tests, conftest options. (Basically: I would not expect you > to write all their tests for them!) > > I don't think you would need to be a pytest super developer or guru. You > could even do it as a way of learning something new about pytest yourself. > > I am happy to try and organise this. I imagine I would do something like > this: > > ? Make a short form to gather details about pytest volunteers (e.g. areas > of experience/interest) > ? Make a page to put on the pytest website, with info to advertise to > potential projects > ? Make a short form for projects to apply/register to take part > ? Pair volunteers and projects together > ? Survey volunteers and projects after the month is over, write a summary > of responses > > So, IF YOU ARE INTERESTED IN TAKING PART: please reply to the list to say > so! > Also if you have any questions or suggestions, let me know. > > Thanks, > Brianna > > > [1] > https://docs.google.com/document/d/14mbVs_f5UFypPx5vvaW-Vh_8Xq9XBKeoNrA0dR0fiJI/edit > > -- > They've just been waiting in a mountain for the right moment: > http://modernthings.org/ > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andreas at pelme.se Thu Feb 5 22:33:40 2015 From: andreas at pelme.se (Andreas Pelme) Date: Thu, 5 Feb 2015 22:33:40 +0100 Subject: [pytest-dev] Let's have an "Adopt pytest month" In-Reply-To: References: Message-ID: Me too! /Andreas > On 5 feb 2015, at 22:31, Anatoly Bubenkov wrote: > > I'm in! > > On Feb 5, 2015 9:51 PM, "Brianna Laugher" wrote: > Hello, > > So as Anatoly mentioned in the notes from the FOSDEM mini-meetup [1], we talked about if we were interested in actively trying to increase pytest adoption, ie get more open source/free software projects using it. As we know how great pytest is, it seems a shame that more people don't know as well! > > I had an idea that we could have a "adopt pytest month": pair knowledgeable pytest users together with interested projects, and help them convert their existing test suite, or start one from scratch if they don't really have any tests yet. Holger liked the idea, so that's a start :) > > It would also be a good way for us to discover "pain points" for new pytest users, for example which areas need better documentation or examples. > > I was thinking it could be in April: > ? February: gather pytest volunteers > ? March: advertise and ask for projects interested in taking part > ? April: the actual work > ? May: survey/write up how it went > > I imagine that volunteers would commit to spending maybe 2-4 hours a week, for the month. They would probably need to download and install the project, join their mailing list and give advice, maybe write some code such as example tests, conftest options. (Basically: I would not expect you to write all their tests for them!) > > I don't think you would need to be a pytest super developer or guru. You could even do it as a way of learning something new about pytest yourself. > > I am happy to try and organise this. I imagine I would do something like this: > > ? Make a short form to gather details about pytest volunteers (e.g. areas of experience/interest) > ? Make a page to put on the pytest website, with info to advertise to potential projects > ? Make a short form for projects to apply/register to take part > ? Pair volunteers and projects together > ? Survey volunteers and projects after the month is over, write a summary of responses > > So, IF YOU ARE INTERESTED IN TAKING PART: please reply to the list to say so! > Also if you have any questions or suggestions, let me know. > > Thanks, > Brianna > > > [1] https://docs.google.com/document/d/14mbVs_f5UFypPx5vvaW-Vh_8Xq9XBKeoNrA0dR0fiJI/edit > > -- > They've just been waiting in a mountain for the right moment: http://modernthings.org/ > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev From holger at merlinux.eu Thu Feb 5 22:57:37 2015 From: holger at merlinux.eu (holger krekel) Date: Thu, 5 Feb 2015 21:57:37 +0000 Subject: [pytest-dev] Let's have an "Adopt pytest month" In-Reply-To: References: Message-ID: <20150205215737.GJ22123@merlinux.eu> On Thu, Feb 05, 2015 at 22:33 +0100, Andreas Pelme wrote: > Me too! I am in if at least one person which hasn't yet committed to pytest yet is in as well :) Holger > /Andreas > > > > On 5 feb 2015, at 22:31, Anatoly Bubenkov wrote: > > > > I'm in! > > > > On Feb 5, 2015 9:51 PM, "Brianna Laugher" wrote: > > Hello, > > > > So as Anatoly mentioned in the notes from the FOSDEM mini-meetup [1], we talked about if we were interested in actively trying to increase pytest adoption, ie get more open source/free software projects using it. As we know how great pytest is, it seems a shame that more people don't know as well! > > > > I had an idea that we could have a "adopt pytest month": pair knowledgeable pytest users together with interested projects, and help them convert their existing test suite, or start one from scratch if they don't really have any tests yet. Holger liked the idea, so that's a start :) > > > > It would also be a good way for us to discover "pain points" for new pytest users, for example which areas need better documentation or examples. > > > > I was thinking it could be in April: > > ? February: gather pytest volunteers > > ? March: advertise and ask for projects interested in taking part > > ? April: the actual work > > ? May: survey/write up how it went > > > > I imagine that volunteers would commit to spending maybe 2-4 hours a week, for the month. They would probably need to download and install the project, join their mailing list and give advice, maybe write some code such as example tests, conftest options. (Basically: I would not expect you to write all their tests for them!) > > > > I don't think you would need to be a pytest super developer or guru. You could even do it as a way of learning something new about pytest yourself. > > > > I am happy to try and organise this. I imagine I would do something like this: > > > > ? Make a short form to gather details about pytest volunteers (e.g. areas of experience/interest) > > ? Make a page to put on the pytest website, with info to advertise to potential projects > > ? Make a short form for projects to apply/register to take part > > ? Pair volunteers and projects together > > ? Survey volunteers and projects after the month is over, write a summary of responses > > > > So, IF YOU ARE INTERESTED IN TAKING PART: please reply to the list to say so! > > Also if you have any questions or suggestions, let me know. > > > > Thanks, > > Brianna > > > > > > [1] https://docs.google.com/document/d/14mbVs_f5UFypPx5vvaW-Vh_8Xq9XBKeoNrA0dR0fiJI/edit > > > > -- > > They've just been waiting in a mountain for the right moment: http://modernthings.org/ > > > > _______________________________________________ > > pytest-dev mailing list > > pytest-dev at python.org > > https://mail.python.org/mailman/listinfo/pytest-dev > > > > _______________________________________________ > > pytest-dev mailing list > > pytest-dev at python.org > > https://mail.python.org/mailman/listinfo/pytest-dev > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev From flub at devork.be Fri Feb 6 00:19:11 2015 From: flub at devork.be (Floris Bruynooghe) Date: Thu, 5 Feb 2015 23:19:11 +0000 Subject: [pytest-dev] Let's have an "Adopt pytest month" In-Reply-To: <20150205215737.GJ22123@merlinux.eu> References: <20150205215737.GJ22123@merlinux.eu> Message-ID: I'm happy to help too, though I won't be able to do much/anything before April as I'm very busy preparing to be away or away for most of the time. On 5 February 2015 at 21:57, holger krekel wrote: > On Thu, Feb 05, 2015 at 22:33 +0100, Andreas Pelme wrote: > > Me too! > > I am in if at least one person which hasn't yet committed to pytest yet > is in as well :) > > Holger > > > /Andreas > > > > > > > On 5 feb 2015, at 22:31, Anatoly Bubenkov wrote: > > > > > > I'm in! > > > > > > On Feb 5, 2015 9:51 PM, "Brianna Laugher" > wrote: > > > Hello, > > > > > > So as Anatoly mentioned in the notes from the FOSDEM mini-meetup [1], > we talked about if we were interested in actively trying to increase pytest > adoption, ie get more open source/free software projects using it. As we > know how great pytest is, it seems a shame that more people don't know as > well! > > > > > > I had an idea that we could have a "adopt pytest month": pair > knowledgeable pytest users together with interested projects, and help them > convert their existing test suite, or start one from scratch if they don't > really have any tests yet. Holger liked the idea, so that's a start :) > > > > > > It would also be a good way for us to discover "pain points" for new > pytest users, for example which areas need better documentation or examples. > > > > > > I was thinking it could be in April: > > > ? February: gather pytest volunteers > > > ? March: advertise and ask for projects interested in taking part > > > ? April: the actual work > > > ? May: survey/write up how it went > > > > > > I imagine that volunteers would commit to spending maybe 2-4 hours a > week, for the month. They would probably need to download and install the > project, join their mailing list and give advice, maybe write some code > such as example tests, conftest options. (Basically: I would not expect you > to write all their tests for them!) > > > > > > I don't think you would need to be a pytest super developer or guru. > You could even do it as a way of learning something new about pytest > yourself. > > > > > > I am happy to try and organise this. I imagine I would do something > like this: > > > > > > ? Make a short form to gather details about pytest volunteers (e.g. > areas of experience/interest) > > > ? Make a page to put on the pytest website, with info to advertise to > potential projects > > > ? Make a short form for projects to apply/register to take part > > > ? Pair volunteers and projects together > > > ? Survey volunteers and projects after the month is over, write a > summary of responses > > > > > > So, IF YOU ARE INTERESTED IN TAKING PART: please reply to the list to > say so! > > > Also if you have any questions or suggestions, let me know. > > > > > > Thanks, > > > Brianna > > > > > > > > > [1] > https://docs.google.com/document/d/14mbVs_f5UFypPx5vvaW-Vh_8Xq9XBKeoNrA0dR0fiJI/edit > > > > > > -- > > > They've just been waiting in a mountain for the right moment: > http://modernthings.org/ > > > > > > _______________________________________________ > > > pytest-dev mailing list > > > pytest-dev at python.org > > > https://mail.python.org/mailman/listinfo/pytest-dev > > > > > > _______________________________________________ > > > pytest-dev mailing list > > > pytest-dev at python.org > > > https://mail.python.org/mailman/listinfo/pytest-dev > > > > _______________________________________________ > > pytest-dev mailing list > > pytest-dev at python.org > > https://mail.python.org/mailman/listinfo/pytest-dev > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Fri Feb 6 01:20:42 2015 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Thu, 5 Feb 2015 22:20:42 -0200 Subject: [pytest-dev] Let's have an "Adopt pytest month" In-Reply-To: References: <20150205215737.GJ22123@merlinux.eu> Message-ID: Me too. :) On Thu, Feb 5, 2015 at 9:19 PM, Floris Bruynooghe wrote: > I'm happy to help too, though I won't be able to do much/anything before > April as I'm very busy preparing to be away or away for most of the time. > > On 5 February 2015 at 21:57, holger krekel wrote: > >> On Thu, Feb 05, 2015 at 22:33 +0100, Andreas Pelme wrote: >> > Me too! >> >> I am in if at least one person which hasn't yet committed to pytest yet >> is in as well :) >> >> Holger >> >> > /Andreas >> > >> > >> > > On 5 feb 2015, at 22:31, Anatoly Bubenkov >> wrote: >> > > >> > > I'm in! >> > > >> > > On Feb 5, 2015 9:51 PM, "Brianna Laugher" >> wrote: >> > > Hello, >> > > >> > > So as Anatoly mentioned in the notes from the FOSDEM mini-meetup [1], >> we talked about if we were interested in actively trying to increase pytest >> adoption, ie get more open source/free software projects using it. As we >> know how great pytest is, it seems a shame that more people don't know as >> well! >> > > >> > > I had an idea that we could have a "adopt pytest month": pair >> knowledgeable pytest users together with interested projects, and help them >> convert their existing test suite, or start one from scratch if they don't >> really have any tests yet. Holger liked the idea, so that's a start :) >> > > >> > > It would also be a good way for us to discover "pain points" for new >> pytest users, for example which areas need better documentation or examples. >> > > >> > > I was thinking it could be in April: >> > > ? February: gather pytest volunteers >> > > ? March: advertise and ask for projects interested in taking part >> > > ? April: the actual work >> > > ? May: survey/write up how it went >> > > >> > > I imagine that volunteers would commit to spending maybe 2-4 hours a >> week, for the month. They would probably need to download and install the >> project, join their mailing list and give advice, maybe write some code >> such as example tests, conftest options. (Basically: I would not expect you >> to write all their tests for them!) >> > > >> > > I don't think you would need to be a pytest super developer or guru. >> You could even do it as a way of learning something new about pytest >> yourself. >> > > >> > > I am happy to try and organise this. I imagine I would do something >> like this: >> > > >> > > ? Make a short form to gather details about pytest volunteers (e.g. >> areas of experience/interest) >> > > ? Make a page to put on the pytest website, with info to advertise to >> potential projects >> > > ? Make a short form for projects to apply/register to take part >> > > ? Pair volunteers and projects together >> > > ? Survey volunteers and projects after the month is over, write a >> summary of responses >> > > >> > > So, IF YOU ARE INTERESTED IN TAKING PART: please reply to the list to >> say so! >> > > Also if you have any questions or suggestions, let me know. >> > > >> > > Thanks, >> > > Brianna >> > > >> > > >> > > [1] >> https://docs.google.com/document/d/14mbVs_f5UFypPx5vvaW-Vh_8Xq9XBKeoNrA0dR0fiJI/edit >> > > >> > > -- >> > > They've just been waiting in a mountain for the right moment: >> http://modernthings.org/ >> > > >> > > _______________________________________________ >> > > pytest-dev mailing list >> > > pytest-dev at python.org >> > > https://mail.python.org/mailman/listinfo/pytest-dev >> > > >> > > _______________________________________________ >> > > pytest-dev mailing list >> > > pytest-dev at python.org >> > > https://mail.python.org/mailman/listinfo/pytest-dev >> > >> > _______________________________________________ >> > pytest-dev mailing list >> > pytest-dev at python.org >> > https://mail.python.org/mailman/listinfo/pytest-dev >> _______________________________________________ >> pytest-dev mailing list >> pytest-dev at python.org >> https://mail.python.org/mailman/listinfo/pytest-dev >> > > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wosc at wosc.de Thu Feb 5 16:51:05 2015 From: wosc at wosc.de (Wolfgang Schnerring) Date: Thu, 5 Feb 2015 15:51:05 +0000 (UTC) Subject: [pytest-dev] Best practises for sharing fixtures Message-ID: Hi, so I have some fixtures in package A, and I'm using said package from package B, which means I might want to write tests in B that re-use the fixtures from A. If I understand the documentation correctly, mechanically I'd simply declare an entrypoint in A like this, correct? Or do I need implement some pytest_ hook to share the fixtures? entry_points = { 'pytest11': ['the_a_fixtures = package_a.conftest'] } Are there any best practises for namespacing / scoping the fixtures? Do I have to take care in package A to prefix all my fixture names with a_fixture1, a_fixture2 so that they do not clash in fixtures in package B? Thanks for any thoughts, Wolfgang From holger at merlinux.eu Fri Feb 6 09:40:24 2015 From: holger at merlinux.eu (holger krekel) Date: Fri, 6 Feb 2015 08:40:24 +0000 Subject: [pytest-dev] Best practises for sharing fixtures In-Reply-To: References: Message-ID: <20150206084024.GL22123@merlinux.eu> Hi Wolfgang, On Thu, Feb 05, 2015 at 15:51 +0000, Wolfgang Schnerring wrote: > Hi, > > so I have some fixtures in package A, and I'm using said package from > package B, which means I might want to write tests in B that re-use the > fixtures from A. > > If I understand the documentation correctly, mechanically I'd simply declare > an entrypoint in A like this, correct? Or do I need implement some pytest_ > hook to share the fixtures? > entry_points = { > 'pytest11': ['the_a_fixtures = package_a.conftest'] > } > > Are there any best practises for namespacing / scoping the fixtures? Do I > have to take care in package A to prefix all my fixture names with > a_fixture1, a_fixture2 so that they do not clash in fixtures in package B? There is no pytest mechanism for name scoping. You could play with importing needed fixtures in package_b.conftest from package_a.conftest under a different name. If package_a fixtures have dependencies on one another it won't easily work, though. Therefore i guess using a prefix for the fixtures you want to share can make sense. holger > Thanks for any thoughts, > Wolfgang > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > From wosc at wosc.de Fri Feb 6 09:45:21 2015 From: wosc at wosc.de (Wolfgang Schnerring) Date: Fri, 6 Feb 2015 09:45:21 +0100 Subject: [pytest-dev] Best practises for sharing fixtures In-Reply-To: <20150206084024.GL22123@merlinux.eu> References: <20150206084024.GL22123@merlinux.eu> Message-ID: <20150206084521.GA19396@zeit.de> Hi, * holger krekel [2015-02-06 08:40]: > > Are there any best practises for namespacing / scoping the fixtures? Do I > > have to take care in package A to prefix all my fixture names with > > a_fixture1, a_fixture2 so that they do not clash in fixtures in package B? > > There is no pytest mechanism for name scoping. You could play with > importing needed fixtures in package_b.conftest from package_a.conftest > under a different name. If package_a fixtures have dependencies on one > another it won't easily work, though. Therefore i guess using a prefix > for the fixtures you want to share can make sense. Yeah, I tried the importing route, that gets hairy really fast. :) I'll go with prefixed names for now. Thanks for your input! Wolfgang -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 173 bytes Desc: Digital signature URL: From opensource at ronnypfannschmidt.de Fri Feb 6 13:39:53 2015 From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt) Date: Fri, 06 Feb 2015 13:39:53 +0100 Subject: [pytest-dev] =?iso-8859-1?q?=5Bdiscuss=5D_on_the_upcoming_changes?= =?iso-8859-1?q?_of_--looponfail/--boxed_and_the_related_releases?= Message-ID: <3e8c8d29-3132-484d-a6d0-9b7cfa05fad1@ronnypfannschmidt.de> Hi, in order to prepare switching --looponfail over to pytest-cache i created some branches in the main repos while doing that i also removed --boxed from xdist related pull requests are * https://bitbucket.org/hpk42/pytest-cache/pull-request/12/move-in-looponfail-from-xdist * https://bitbucket.org/hpk42/pytest-xdist/pull-request/14/kill-looponfail-and-boxed/diff in particular looponchangeroots might need some more discussion about semantics i already prepared a potential replacement for --boxed in pytest-boxed (which is not yet released, maybe sometime later today) the current set changes requires to update xdist and cache at the same time to keep backward compatibility better, i could move the actual --looponfail option to xdist and set up the requirements of xdist to contain boxed/cache in order keep the same feature set availiable main question is do we want to enforce update at once or have a more gradual process (i'm in favor of a more disruptive change but, i know many of you have compatibiliy concernsto take into consideration) -- Ronny From holger at merlinux.eu Fri Feb 6 14:56:55 2015 From: holger at merlinux.eu (holger krekel) Date: Fri, 6 Feb 2015 13:56:55 +0000 Subject: [pytest-dev] [discuss] on the upcoming changes of --looponfail/--boxed and the related releases In-Reply-To: <3e8c8d29-3132-484d-a6d0-9b7cfa05fad1@ronnypfannschmidt.de> References: <3e8c8d29-3132-484d-a6d0-9b7cfa05fad1@ronnypfannschmidt.de> Message-ID: <20150206135655.GO22123@merlinux.eu> Hi Ronny, Indeed backward compat is a major concern. It's a) nicer UI b) avoids spending time on unneccessary support issues. I suggest we make sure that all combinations of pytest-xdist (current and next) work with pytest-2.6.4 and pytest-2.7 and to discountinue pytest-cache. Given that pytest-2.7 might not be far away i suggest to directly move looponfail and pytest-cache functionality into the core and make sure that pytest-2.7 auto-disables pytest-cache when it is installed (with a warning). The pytest-xdist looponfail cmdline option will then conflict with pytest-2.7 core looponfail. We can enhance the command line option registration to ignore adding same-named options and issue a precise warning. (Warnings can be issued globally, need not be tied to an item). holger On Fri, Feb 06, 2015 at 13:39 +0100, Ronny Pfannschmidt wrote: > > Hi, > > in order to prepare switching --looponfail over to pytest-cache > i created some branches in the main repos > > while doing that i also removed --boxed from xdist > > related pull requests are * https://bitbucket.org/hpk42/pytest-cache/pull-request/12/move-in-looponfail-from-xdist > * https://bitbucket.org/hpk42/pytest-xdist/pull-request/14/kill-looponfail-and-boxed/diff > > in particular looponchangeroots might need some more discussion > about semantics > > > i already prepared a potential replacement for --boxed in > pytest-boxed (which is not yet released, maybe sometime later today) > > the current set changes requires to update xdist and cache at the same time > > to keep backward compatibility better, > i could move the actual --looponfail option to xdist > and set up the requirements of xdist to contain boxed/cache > in order keep the same feature set availiable > > main question is do we want to enforce update at once > or have a more gradual process > (i'm in favor of a more disruptive change but, > i know many of you have compatibiliy concernsto take into consideration) > > -- Ronny > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > From tibor.arpas at infinit.sk Tue Feb 10 22:44:57 2015 From: tibor.arpas at infinit.sk (Tibor Arpas) Date: Tue, 10 Feb 2015 22:44:57 +0100 Subject: [pytest-dev] Let's have an "Adopt pytest month" In-Reply-To: References: Message-ID: Hi, Good idea! I might help depending on how busy I'm in March and April. Cheers, Tibor On Thu, Feb 5, 2015 at 9:50 PM, Brianna Laugher wrote: > Hello, > > So as Anatoly mentioned in the notes from the FOSDEM mini-meetup [1], we > talked about if we were interested in actively trying to increase pytest > adoption, ie get more open source/free software projects using it. As we > know how great pytest is, it seems a shame that more people don't know as > well! > > I had an idea that we could have a "adopt pytest month": pair > knowledgeable pytest users together with interested projects, and help them > convert their existing test suite, or start one from scratch if they don't > really have any tests yet. Holger liked the idea, so that's a start :) > > It would also be a good way for us to discover "pain points" for new > pytest users, for example which areas need better documentation or examples. > > I was thinking it could be in April: > ? February: gather pytest volunteers > ? March: advertise and ask for projects interested in taking part > ? April: the actual work > ? May: survey/write up how it went > > I imagine that volunteers would commit to spending maybe 2-4 hours a week, > for the month. They would probably need to download and install the > project, join their mailing list and give advice, maybe write some code > such as example tests, conftest options. (Basically: I would not expect you > to write all their tests for them!) > > I don't think you would need to be a pytest super developer or guru. You > could even do it as a way of learning something new about pytest yourself. > > I am happy to try and organise this. I imagine I would do something like > this: > > ? Make a short form to gather details about pytest volunteers (e.g. areas > of experience/interest) > ? Make a page to put on the pytest website, with info to advertise to > potential projects > ? Make a short form for projects to apply/register to take part > ? Pair volunteers and projects together > ? Survey volunteers and projects after the month is over, write a summary > of responses > > So, IF YOU ARE INTERESTED IN TAKING PART: please reply to the list to say > so! > Also if you have any questions or suggestions, let me know. > > Thanks, > Brianna > > > [1] > https://docs.google.com/document/d/14mbVs_f5UFypPx5vvaW-Vh_8Xq9XBKeoNrA0dR0fiJI/edit > > -- > They've just been waiting in a mountain for the right moment: > http://modernthings.org/ > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From opensource at ronnypfannschmidt.de Wed Feb 11 00:48:23 2015 From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt) Date: Wed, 11 Feb 2015 00:48:23 +0100 Subject: [pytest-dev] =?iso-8859-1?q?=5Bdiscuss=5D_solving_the_yield_test_?= =?iso-8859-1?q?setupstate_problem_and_expanding_on_it?= Message-ID: <1fb2e53c-52de-4be0-bc02-58ff2fa499cb@ronnypfannschmidt.de> Hi, since i did hit the generator test i started to create a proof of concept on solving it by creating the pytest_pyfunc_interpret_result hook. now instead of running at collect time, generators checks run inline this currently degrades reporting * breaks on first fail * no separate reports per check and it degrades nose support * no generator check setup/teardown while i suppose its possible to extend generator support with teardown in a hackish fashin i think going for a clean solution makes more sense is anyone propperly using these features? onwards i'd like to check how to extend pytest_pyfunc_interpret_result with convenience for asyncio and twisted -- Ronny From holger at merlinux.eu Wed Feb 11 08:55:36 2015 From: holger at merlinux.eu (holger krekel) Date: Wed, 11 Feb 2015 07:55:36 +0000 Subject: [pytest-dev] [discuss] solving the yield test setupstate problem and expanding on it In-Reply-To: <1fb2e53c-52de-4be0-bc02-58ff2fa499cb@ronnypfannschmidt.de> References: <1fb2e53c-52de-4be0-bc02-58ff2fa499cb@ronnypfannschmidt.de> Message-ID: <20150211075536.GA17518@merlinux.eu> Hi Ronny, could you first outline the problem you are trying to solve? holger On Wed, Feb 11, 2015 at 00:48 +0100, Ronny Pfannschmidt wrote: > > Hi, > > since i did hit the generator test i started to create a proof of > concept on solving it by creating the pytest_pyfunc_interpret_result > hook. > > now instead of running at collect time, generators checks run inline > > this currently degrades reporting > * breaks on first fail > * no separate reports per check > > and it degrades nose support * no generator check setup/teardown > > while i suppose its possible to extend generator support with > teardown in a hackish fashin i think going for a clean solution > makes more sense > > is anyone propperly using these features? > > > onwards i'd like to check how to extend > pytest_pyfunc_interpret_result with convenience for asyncio and > twisted > > > -- Ronny > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > From raphael at hackebrot.de Thu Feb 12 22:06:21 2015 From: raphael at hackebrot.de (Raphael Pierzina) Date: Thu, 12 Feb 2015 22:06:21 +0100 Subject: [pytest-dev] Let's have an "Adopt pytest month" In-Reply-To: <20150205215737.GJ22123@merlinux.eu> References: <20150205215737.GJ22123@merlinux.eu> Message-ID: <54DD15CD.4050604@hackebrot.de> I'm in :) This is a great idea. Back in November I converted a bunch of tests for Cookiecutter. Most PR's are still pending though. https://github.com/audreyr/cookiecutter/pulls/hackebrot I did not contribute to PyTest thus far. Raphael From opensource at ronnypfannschmidt.de Wed Feb 18 18:23:25 2015 From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt) Date: Wed, 18 Feb 2015 18:23:25 +0100 Subject: [pytest-dev] [STATUS, RFC, PLANS] development of the copy-in-cache branch Message-ID: Hi , this is a status and a rfc for the copy-in-cache branch. its mostly relevant for the pytest core developers current status: the pytest-cache branch with the --looponfail/--looponchange modes is copyed in and adapted to the codebase futher plan: also include logcapture backward compat plan: * ignore the cache/logcapture plugins as disabled and warn if they are installed * override the --looponfail option to be a callback, setting the lastfailed and looponchange options and allow pytest-xdist to override it (but warn if a xdist of the current series is found, explaining that the new better behaviour is still availiable using the --looponchange option combined with --lf) note: the current idea is, to implement this in a _pytest.deprecation plugin intentionally left out: * the --boxed option - it should eventually be reimplemeted on top of xdist, current xdist does still include it, (i'd prefer a major xdist release droping all features) -- Ronny From holger at merlinux.eu Fri Feb 20 09:55:28 2015 From: holger at merlinux.eu (holger krekel) Date: Fri, 20 Feb 2015 08:55:28 +0000 Subject: [pytest-dev] PRs / pytest2.7 Message-ID: <20150220085528.GY9574@merlinux.eu> Hi pytest committers, could you help with looking at/merging PRs for pytest? See https://bitbucket.org/hpk42/pytest/pull-requests Getting out pytest-2.7 in the next 1-2 weeks would be good i guess to clear out the backlog. best and thanks! holger From holger at merlinux.eu Fri Feb 20 10:32:30 2015 From: holger at merlinux.eu (holger krekel) Date: Fri, 20 Feb 2015 09:32:30 +0000 Subject: [pytest-dev] [STATUS, RFC, PLANS] development of the copy-in-cache branch In-Reply-To: References: Message-ID: <20150220093230.GZ9574@merlinux.eu> Hi Ronny, thanks for the write up. On Wed, Feb 18, 2015 at 18:23 +0100, Ronny Pfannschmidt wrote: > Hi , > > this is a status and a rfc for the copy-in-cache branch. > its mostly relevant for the pytest core developers > > current status: > the pytest-cache branch with the --looponfail/--looponchange > modes is copyed in and adapted to the codebase You mentioned elsewhere that you want to use some filewatch package for detecting file changes. If you do that --looponfail cannot move to pytest-core because core should have the least possible dependencies, ideally zero. The reason is that pytest runs "in-process" and thus pytest's dependencies might interfere with the program under test. Anything that requires third party deps should thus be in a plugin so users have a choice about which dependencies contaminate their test environment. Alternatively, we could vendor select dependencies into the pytest namespace to avoid clashes but that'd probably give trouble with fedora/debian maintainers who generally don't like vendoring. > futher plan: > also include logcapture makes sense because "logging" is part of the stdlib anyway. We need a new option to disable logcapture because previously you could disable it by not installing pytest-logcapture. Maybe "-p-logcapture" is enough, needs to be tested. > backward compat plan: > * ignore the cache/logcapture plugins as disabled > and warn if they are installed OK. > * override the --looponfail option to be a callback, > setting the lastfailed and looponchange options and > allow pytest-xdist to override it > (but warn if a xdist of the current series is found, > explaining that the new better behaviour > is still availiable > using the --looponchange option combined with --lf) note sure i understand. I think pytest-xdist-NEXTVERSION should use pytest-2.7 and its cache/lastfail mechanisms to implement --looponfail (and maybe depend on a "watch" package if you will, see above). > note: the current idea is, > to implement this in a _pytest.deprecation plugin Not sure a "deprecation" plugin is needed -- we have deprecated bits all over the place and cannot easily move it to a plugin. > intentionally left out: > * the --boxed option - it should eventually > be reimplemeted on top of xdist, > current xdist does still include it, > (i'd prefer a major xdist release droping all features) pytest-xdist is generally free to implement boxed otherwise. It's not clear, however, if using execnet/xdist code to implement boxed is fully backward compatible but we can try and see about user feedback, i guess. To summarize: - pytest-2.7 to contain pytest-cache and pytest-logcapture code and ignore their installation with a warning - pytest-xdist-2.0 to depend on pytest-2.7 and to (possibly) re-implement boxed as "-n1". When moving pytest-cache and pytest-logcapture to core please please make sure you also move/have some docs. I can review your work beginning next week if tests pass on linux/windows with py2/py3. best, holger From opensource at ronnypfannschmidt.de Sat Feb 21 19:46:56 2015 From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt) Date: Sat, 21 Feb 2015 19:46:56 +0100 Subject: [pytest-dev] [RFC] some initial ideas for pylib-2.0 Message-ID: Hi all, i'd like to start some very rough planing for pylib 2.0 hoping for some comments main going a bit far things i currently have in mind * kill py.std * kill most of terminalwriter * move code/capture/saferepr to pytest ? * kill svn path (its broken and nobody fixes it) * de-vendorize apipkg/iniparse * kill xml gen * unify errors and the new python3 error hierachy * modernize py.builtin using six, potential api changes where six raises attribute errors * evaluate log, potentially kill? * refactor local path, consider pathlib this is a long term plan -- Ronny From holger at merlinux.eu Sat Feb 21 20:01:34 2015 From: holger at merlinux.eu (holger krekel) Date: Sat, 21 Feb 2015 19:01:34 +0000 Subject: [pytest-dev] [RFC] some initial ideas for pylib-2.0 In-Reply-To: References: Message-ID: <20150221190134.GC7964@merlinux.eu> Hi Ronny, On Sat, Feb 21, 2015 at 19:46 +0100, Ronny Pfannschmidt wrote: > Hi all, > > i'd like to start some very rough planing for pylib 2.0 > hoping for some comments > > main going a bit far things i currently have in mind > > * kill py.std > * kill most of terminalwriter > * move code/capture/saferepr to pytest ? > * kill svn path (its broken and nobody fixes it) > * de-vendorize apipkg/iniparse > * kill xml gen > * unify errors and the new python3 error hierachy > * modernize py.builtin using six, potential api changes where six > raises attribute errors > > * evaluate log, potentially kill? > * refactor local path, consider pathlib > > this is a long term plan I consider pylib to be more or less EOLed (at end-of-life) apart from occasional minor fixes. Changing and removing things from py will break dependend tools and i don't think that's worth the trouble. As far as pytest and tox are concerned i suggest (if anything) to reduce usage and dependency on pylib to the point where it can be removed as a dependency. This way there is no breaking combination of py/pytest ever. One area that indeed would make sense to move first is py.code.* because it's really quite pytest-specific code and we typically need to release a new py to fix exception/formatting related bugs for pytest. Even then i'd not remove it from pylib, just not use it anymore from pytest (and it's rarely used by others, special attention for PyPy needed, though) cheers, holger From nicoddemus at gmail.com Sat Feb 21 20:32:14 2015 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Sat, 21 Feb 2015 17:32:14 -0200 Subject: [pytest-dev] [RFC] some initial ideas for pylib-2.0 In-Reply-To: <20150221190134.GC7964@merlinux.eu> References: <20150221190134.GC7964@merlinux.eu> Message-ID: Hi Holger, On Sat, Feb 21, 2015 at 5:01 PM, holger krekel wrote: > > > As far as pytest and tox are concerned i suggest (if anything) to reduce > usage and dependency on pylib to the point where it can be removed as a > dependency. This way there is no breaking combination of py/pytest > ever. In that direction, py.path would have to be moved to pytest as well? pytest's API exposes it. Cheers, -------------- next part -------------- An HTML attachment was scrubbed... URL: From opensource at ronnypfannschmidt.de Sat Feb 21 20:34:41 2015 From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt) Date: Sat, 21 Feb 2015 20:34:41 +0100 Subject: [pytest-dev] [RFC] some initial ideas for pylib-2.0 In-Reply-To: References: <20150221190134.GC7964@merlinux.eu> Message-ID: <4dedf9df-dab0-4dce-8aac-4937d4c651d4@ronnypfannschmidt.de> Hi Bruno, nope, it'll remain a separate lib, plans will made after py.test-2.7 -- Ronny On Saturday, February 21, 2015 8:32:14 PM CEST, Bruno Oliveira wrote: > Hi Holger, > > On Sat, Feb 21, 2015 at 5:01 PM, holger krekel wrote: > > As far as pytest and tox are concerned i suggest (if anything) to reduce > usage and dependency on pylib to the point where it can be removed as a > dependency. This way there is no breaking combination of py/pytest > ever. > > In that direction, py.path would have to be moved to pytest as > well? pytest's API exposes it. > > Cheers, From holger at merlinux.eu Sat Feb 21 21:07:10 2015 From: holger at merlinux.eu (holger krekel) Date: Sat, 21 Feb 2015 20:07:10 +0000 Subject: [pytest-dev] [RFC] some initial ideas for pylib-2.0 In-Reply-To: References: <20150221190134.GC7964@merlinux.eu> Message-ID: <20150221200710.GA9441@merlinux.eu> Hi Bruno, On Sat, Feb 21, 2015 at 17:32 -0200, Bruno Oliveira wrote: > Hi Holger, > > On Sat, Feb 21, 2015 at 5:01 PM, holger krekel wrote: > > > > > > As far as pytest and tox are concerned i suggest (if anything) to reduce > > usage and dependency on pylib to the point where it can be removed as a > > dependency. This way there is no breaking combination of py/pytest > > ever. > > In that direction, py.path would have to be moved to pytest as well? > pytest's API exposes it. Question is what APIs plugins (typically) use. Depending on that it's probably not hard to experiment with exposing a compatibility adaptor using pathlib within pytest core for use from plugins. best, holger From tom at viner.tv Mon Feb 23 17:48:04 2015 From: tom at viner.tv (Tom Viner) Date: Mon, 23 Feb 2015 16:48:04 +0000 Subject: [pytest-dev] [py-dev] using tmpdir/monkeypatch/... from non-function scopes Message-ID: Re this thread from 2012: https://mail.python.org/pipermail/pytest-dev/2012-November/002157.html Was there ever any resolution or workaround to using monkeypatch / tmpdir with scopes other than function? Example: @pytest.fixture(scope="module") def something(monkeypatch): ... you get a ScopeMismatchError Thanks, Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From holger at merlinux.eu Mon Feb 23 18:40:07 2015 From: holger at merlinux.eu (holger krekel) Date: Mon, 23 Feb 2015 17:40:07 +0000 Subject: [pytest-dev] [py-dev] using tmpdir/monkeypatch/... from non-function scopes In-Reply-To: References: Message-ID: <20150223174007.GF9441@merlinux.eu> On Mon, Feb 23, 2015 at 16:48 +0000, Tom Viner wrote: > Re this thread from 2012: > https://mail.python.org/pipermail/pytest-dev/2012-November/002157.html > > Was there ever any resolution or workaround to using monkeypatch / tmpdir > with scopes other than function? > > Example: > > @pytest.fixture(scope="module") def something(monkeypatch): > ... > you get a ScopeMismatchError The plan is to introduce a new scope for fixture functions but it's not done yet. For now, you can create a tempdir fixture using the canonical tempdir std library module. best, holger From tom at viner.tv Mon Feb 23 18:58:16 2015 From: tom at viner.tv (Tom Viner) Date: Mon, 23 Feb 2015 17:58:16 +0000 Subject: [pytest-dev] [py-dev] using tmpdir/monkeypatch/... from non-function scopes In-Reply-To: <20150223174007.GF9441@merlinux.eu> References: <20150223174007.GF9441@merlinux.eu> Message-ID: Ok thanks Holger, sounds like a good plan. I found I could work around the problem by implementing my own session versions like this: @pytest.fixture(scope='session') def tmpdir_session(request): # code copied from _pytest/tmpdir.py """return a temporary directory path object which is unique to each test function invocation, created as a sub directory of the base temporary directory. The returned object is a `py.path.local`_ path object. """ name = request.node.name name = re.sub("[\W]", "_", name) MAXVAL = 30 if len(name) > MAXVAL: name = name[:MAXVAL] x = request.config._tmpdirhandler.mktemp(name, numbered=True) return x @pytest.yield_fixture(scope='session') def monkeypatch_session(request): from _pytest.monkeypatch import monkeypatch mp = _monkeypatch() yield mp request.addfinalizer(mp.undo) Do you see any inherent problem with these? On 23 February 2015 at 17:40, holger krekel wrote: > On Mon, Feb 23, 2015 at 16:48 +0000, Tom Viner wrote: > > Re this thread from 2012: > > https://mail.python.org/pipermail/pytest-dev/2012-November/002157.html > > > > Was there ever any resolution or workaround to using monkeypatch / tmpdir > > with scopes other than function? > > > > Example: > > > > @pytest.fixture(scope="module") def something(monkeypatch): > > ... > > you get a ScopeMismatchError > > The plan is to introduce a new scope for fixture functions > but it's not done yet. For now, you can create a tempdir > fixture using the canonical tempdir std library module. > > best, > holger > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wosc at wosc.de Tue Feb 24 07:14:07 2015 From: wosc at wosc.de (Wolfgang Schnerring) Date: Tue, 24 Feb 2015 07:14:07 +0100 Subject: [pytest-dev] [py-dev] using tmpdir/monkeypatch/... from non-function scopes References: Message-ID: <20150224071407.532fb616@anthrakas> * Tom Viner [2015-02-23 16:48]: > Was there ever any resolution or workaround to using monkeypatch / > tmpdir with scopes other than function? As a workaround, I find myself doing this from time to time (copy&paste from actual code, which you can tell from the loving comment :-) # XXX Dear pytest, you've got to be kidding. @pytest.fixture(scope='session') def tmpdir_session(request): return _pytest.tmpdir.tmpdir(request) Wolfgang From anto.cuni at gmail.com Wed Feb 25 10:12:06 2015 From: anto.cuni at gmail.com (Antonio Cuni) Date: Wed, 25 Feb 2015 10:12:06 +0100 Subject: [pytest-dev] [RFC] some initial ideas for pylib-2.0 In-Reply-To: <20150221190134.GC7964@merlinux.eu> References: <20150221190134.GC7964@merlinux.eu> Message-ID: Hi, On Sat, Feb 21, 2015 at 8:01 PM, holger krekel wrote: > As far as pytest and tox are concerned i suggest (if anything) to reduce > usage and dependency on pylib to the point where it can be removed as a > dependency. This way there is no breaking combination of py/pytest > ever. One area that indeed would make sense to move first is py.code.* > because it's really quite pytest-specific code and we typically need to > release a new py to fix exception/formatting related bugs for pytest. > Even then i'd not remove it from pylib, just not use it anymore from pytest > (and it's rarely used by others, special attention for PyPy needed, though) > ?fwiw, I use py.code.Source almost everytime I need to exec some code generated on the fly. Please don't remove it from pylib, or lots of my projects will break :)? -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Fri Feb 27 14:28:22 2015 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Fri, 27 Feb 2015 10:28:22 -0300 Subject: [pytest-dev] Move plugins to pytest-deb@github: pytest-cpp, pytest-qt, pytest-mock Message-ID: Hi, I would to like to know if there are any objections to move the following plugins to pytest-dev at github organization: https://github.com/nicoddemus/pytest-qt https://github.com/nicoddemus/pytest-cpp https://github.com/nicoddemus/pytest-mock All of those repositories are in PyPI, have an appropriate README, license, continuous integration, etc. It seems people are starting to move plugins that have a good number of users to the pytest-dev organization, so I thought I would move those too. Cheers, ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From bubenkoff at gmail.com Fri Feb 27 14:59:56 2015 From: bubenkoff at gmail.com (Anatoly Bubenkov) Date: Fri, 27 Feb 2015 14:59:56 +0100 Subject: [pytest-dev] Move plugins to pytest-deb@github: pytest-cpp, pytest-qt, pytest-mock In-Reply-To: References: Message-ID: +1 for the move, please do - you have all the rights On 27 February 2015 at 14:28, Bruno Oliveira wrote: > Hi, > > I would to like to know if there are any objections to move the following > plugins to pytest-dev at github organization: > > https://github.com/nicoddemus/pytest-qt > https://github.com/nicoddemus/pytest-cpp > https://github.com/nicoddemus/pytest-mock > > All of those repositories are in PyPI, have an appropriate README, > license, continuous integration, etc. > > It seems people are starting to move plugins that have a good number of > users to the pytest-dev organization, so I thought I would move those too. > > Cheers, > ? > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > > -- Anatoly Bubenkov -------------- next part -------------- An HTML attachment was scrubbed... URL: From holger at merlinux.eu Fri Feb 27 15:02:23 2015 From: holger at merlinux.eu (holger krekel) Date: Fri, 27 Feb 2015 14:02:23 +0000 Subject: [pytest-dev] Move plugins to pytest-deb@github: pytest-cpp, pytest-qt, pytest-mock In-Reply-To: References: Message-ID: <20150227140223.GZ17945@merlinux.eu> On Fri, Feb 27, 2015 at 14:59 +0100, Anatoly Bubenkov wrote: > +1 for the move, please do - you have all the rights I am also fine with moving them! best, holger > On 27 February 2015 at 14:28, Bruno Oliveira wrote: > > > Hi, > > > > I would to like to know if there are any objections to move the following > > plugins to pytest-dev at github organization: > > > > https://github.com/nicoddemus/pytest-qt > > https://github.com/nicoddemus/pytest-cpp > > https://github.com/nicoddemus/pytest-mock > > > > All of those repositories are in PyPI, have an appropriate README, > > license, continuous integration, etc. > > > > It seems people are starting to move plugins that have a good number of > > users to the pytest-dev organization, so I thought I would move those too. > > > > Cheers, > > ? > > > > _______________________________________________ > > pytest-dev mailing list > > pytest-dev at python.org > > https://mail.python.org/mailman/listinfo/pytest-dev > > > > > > > -- > Anatoly Bubenkov > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev From holger at merlinux.eu Fri Feb 27 15:04:05 2015 From: holger at merlinux.eu (holger krekel) Date: Fri, 27 Feb 2015 14:04:05 +0000 Subject: [pytest-dev] Move plugins to pytest-deb@github: pytest-cpp, pytest-qt, pytest-mock In-Reply-To: <20150227140223.GZ17945@merlinux.eu> References: <20150227140223.GZ17945@merlinux.eu> Message-ID: <20150227140405.GA17945@merlinux.eu> On Fri, Feb 27, 2015 at 14:02 +0000, holger krekel wrote: > On Fri, Feb 27, 2015 at 14:59 +0100, Anatoly Bubenkov wrote: > > +1 for the move, please do - you have all the rights > > I am also fine with moving them! Btw. It's a good idea to update the respective pypi pages of the latest release if they contain links and put a empty "moved to note" in the old location (unless github does this automatically?). best, holger > best, > holger > > > > On 27 February 2015 at 14:28, Bruno Oliveira wrote: > > > > > Hi, > > > > > > I would to like to know if there are any objections to move the following > > > plugins to pytest-dev at github organization: > > > > > > https://github.com/nicoddemus/pytest-qt > > > https://github.com/nicoddemus/pytest-cpp > > > https://github.com/nicoddemus/pytest-mock > > > > > > All of those repositories are in PyPI, have an appropriate README, > > > license, continuous integration, etc. > > > > > > It seems people are starting to move plugins that have a good number of > > > users to the pytest-dev organization, so I thought I would move those too. > > > > > > Cheers, > > > ? > > > > > > _______________________________________________ > > > pytest-dev mailing list > > > pytest-dev at python.org > > > https://mail.python.org/mailman/listinfo/pytest-dev > > > > > > > > > > > > -- > > Anatoly Bubenkov > > > _______________________________________________ > > pytest-dev mailing list > > pytest-dev at python.org > > https://mail.python.org/mailman/listinfo/pytest-dev > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev From nicoddemus at gmail.com Fri Feb 27 15:06:44 2015 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Fri, 27 Feb 2015 11:06:44 -0300 Subject: [pytest-dev] Move plugins to pytest-deb@github: pytest-cpp, pytest-qt, pytest-mock In-Reply-To: <20150227140405.GA17945@merlinux.eu> References: <20150227140223.GZ17945@merlinux.eu> <20150227140405.GA17945@merlinux.eu> Message-ID: Yes, thanks for the reminder. I think gihub does the redirecting automatically, but I will make sure to update the pypi pages anyway. Cheers, On Fri, Feb 27, 2015 at 11:04 AM, holger krekel wrote: > On Fri, Feb 27, 2015 at 14:02 +0000, holger krekel wrote: > > On Fri, Feb 27, 2015 at 14:59 +0100, Anatoly Bubenkov wrote: > > > +1 for the move, please do - you have all the rights > > > > I am also fine with moving them! > > Btw. It's a good idea to update the respective pypi pages of the > latest release if they contain links and put a empty "moved to note" in > the old location (unless github does this automatically?). > > best, > holger > > > best, > > holger > > > > > > > On 27 February 2015 at 14:28, Bruno Oliveira > wrote: > > > > > > > Hi, > > > > > > > > I would to like to know if there are any objections to move the > following > > > > plugins to pytest-dev at github organization: > > > > > > > > https://github.com/nicoddemus/pytest-qt > > > > https://github.com/nicoddemus/pytest-cpp > > > > https://github.com/nicoddemus/pytest-mock > > > > > > > > All of those repositories are in PyPI, have an appropriate README, > > > > license, continuous integration, etc. > > > > > > > > It seems people are starting to move plugins that have a good number > of > > > > users to the pytest-dev organization, so I thought I would move > those too. > > > > > > > > Cheers, > > > > ? > > > > > > > > _______________________________________________ > > > > pytest-dev mailing list > > > > pytest-dev at python.org > > > > https://mail.python.org/mailman/listinfo/pytest-dev > > > > > > > > > > > > > > > > > -- > > > Anatoly Bubenkov > > > > > _______________________________________________ > > > pytest-dev mailing list > > > pytest-dev at python.org > > > https://mail.python.org/mailman/listinfo/pytest-dev > > > > _______________________________________________ > > pytest-dev mailing list > > pytest-dev at python.org > > https://mail.python.org/mailman/listinfo/pytest-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From brianna.laugher at gmail.com Fri Feb 27 17:45:04 2015 From: brianna.laugher at gmail.com (Brianna Laugher) Date: Fri, 27 Feb 2015 17:45:04 +0100 Subject: [pytest-dev] Let's have an "Adopt pytest month" In-Reply-To: <54DD15CD.4050604@hackebrot.de> References: <20150205215737.GJ22123@merlinux.eu> <54DD15CD.4050604@hackebrot.de> Message-ID: Hello all! We finally have a web page for adopt pytest month: http://pytest.org/latest/adopt.html If you would like to be a helper, please fill out this short form, preferably in the next week or so: http://goo.gl/forms/nxqAhqWt1P I will use the information to try and pair helpers with appropriate projects according to their needs. And if you have some projects in mind that you'd like to gently nudge towards pytest, I think now is the time to spread the word :) cheers Brianna On 12 February 2015 at 22:06, Raphael Pierzina wrote: > I'm in :) This is a great idea. > > Back in November I converted a bunch of tests for Cookiecutter. Most PR's > are still pending though. > https://github.com/audreyr/cookiecutter/pulls/hackebrot > > I did not contribute to PyTest thus far. > > Raphael > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > -- They've just been waiting in a mountain for the right moment: http://modernthings.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From holger at merlinux.eu Sat Feb 28 21:54:02 2015 From: holger at merlinux.eu (holger krekel) Date: Sat, 28 Feb 2015 20:54:02 +0000 Subject: [pytest-dev] commit messages from drone In-Reply-To: <20150228205020.19154.16752@drone.io> References: <20150228205020.19154.16752@drone.io> Message-ID: <20150228205402.GT17945@merlinux.eu> Is there a configuration where only failures are sent to the list? It's a bit verbose as it stands IMHO. And maybe just the author in the commit should get success mails for a commit. holger On Sat, Feb 28, 2015 at 20:50 +0000, Drone.io Build wrote: > Build was Successful > > Build : https://drone.io/bitbucket.org/pytest-dev/pytest/13 > Project : https://drone.io/bitbucket.org/pytest-dev/pytest > > Repository : https://bitbucket.org/pytest-dev/pytest > Version : 3892:ebe73a63994f > Author : Anatoly Bubenkov > Branch : plugincompat-move > > Message: > Close branch plugincompat-move > > _______________________________________________ > pytest-commit mailing list > pytest-commit at python.org > https://mail.python.org/mailman/listinfo/pytest-commit -- about me: http://holgerkrekel.net/about-me/ contracting: http://merlinux.eu