From fp at gocept.com  Tue Feb  2 09:19:01 2016
From: fp at gocept.com (Florian Pilz)
Date: Tue, 2 Feb 2016 15:19:01 +0100
Subject: [pytest-dev] Moving pytest-rerunfailures to pytest-dev
Message-ID: <40229627-C690-41D0-9734-A17EC6B40E3E@gocept.com>

Hi, I?m asking whether `pytest-rerunfailures` should be moved to the `pytest-dev` organisation (https://github.com/gocept/pytest-rerunfailures <https://github.com/gocept/pytest-rerunfailures>).

Since we (gocept) only rarely take time to work on issues / pull requests of `pytest-rerunfailures` we would prefer to move the extremely useful plugin to `pytest-dev`. There we still can work on it, but are not the only ones taking care of the project.

So if you think `pytest-rerunfailures` is a great addition to `pytest` and should be moved to the pytest-dev organization, let us know. :)

Best wishes
Florian
?????????
Florian Pilz ? fp at gocept.com ? Software Developer
gocept gmbh & co. kg ? Forsterstra?e 29 ? 06112 Halle (Saale) ? Germany
http://gocept.com <http://gocept.com/> ? Tel +49 345 122 9889 7
Python, Pyramid, Plone, Zope ? consulting, development, hosting, operations

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160202/37ede26a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160202/37ede26a/attachment.sig>

From me at the-compiler.org  Tue Feb  2 09:32:15 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Tue, 2 Feb 2016 15:32:15 +0100
Subject: [pytest-dev] Moving pytest-rerunfailures to pytest-dev
In-Reply-To: <40229627-C690-41D0-9734-A17EC6B40E3E@gocept.com>
References: <40229627-C690-41D0-9734-A17EC6B40E3E@gocept.com>
Message-ID: <20160202143215.GE542@tonks>

* Florian Pilz <fp at gocept.com> [2016-02-02 15:19:01 +0100]:
> Hi, I?m asking whether `pytest-rerunfailures` should be moved to the `pytest-dev` organisation (https://github.com/gocept/pytest-rerunfailures <https://github.com/gocept/pytest-rerunfailures>).
> 
> Since we (gocept) only rarely take time to work on issues / pull requests of `pytest-rerunfailures` we would prefer to move the extremely useful plugin to `pytest-dev`. There we still can work on it, but are not the only ones taking care of the project.
> 
> So if you think `pytest-rerunfailures` is a great addition to `pytest` and should be moved to the pytest-dev organization, let us know. :)

I haven't used it yet, but I'll probably have to do so soon, as there
are some flaky things in my testsuite out of my control.

Other than that it seems to work well from what I've seen, so +1 from
my side.

Florian (hah!)

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160202/1a9e3a28/attachment.sig>

From nicoddemus at gmail.com  Tue Feb  2 09:39:32 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Tue, 02 Feb 2016 14:39:32 +0000
Subject: [pytest-dev] Moving pytest-rerunfailures to pytest-dev
In-Reply-To: <40229627-C690-41D0-9734-A17EC6B40E3E@gocept.com>
References: <40229627-C690-41D0-9734-A17EC6B40E3E@gocept.com>
Message-ID: <CA+RQFfcHyZuKULNUtPy0v_n0_EykWoeHZucWDTm2FywSK3pWWg@mail.gmail.com>

Florian (not you compiler!),

Thanks for writing. I'm +1 as well, as the plugin seems to be used by a lot
of people and meets all requirements we have set for plugins to be moved
under pytest-dev.

Could you please transfer ownership to me (@nicoddemus) or Florian
(@The-Compiler)? You have to transfer to us so we can move it to the
organization (at least we couldn't figure out another way to do it).

Cheers,
Bruno.

On Tue, Feb 2, 2016 at 12:29 PM Florian Pilz <fp at gocept.com> wrote:

> Hi, I?m asking whether `pytest-rerunfailures` should be moved to the
> `pytest-dev` organisation (https://github.com/gocept/pytest-rerunfailures
> ).
>
> Since we (gocept) only rarely take time to work on issues / pull requests
> of `pytest-rerunfailures` we would prefer to move the extremely useful
> plugin to `pytest-dev`. There we still can work on it, but are not the only
> ones taking care of the project.
>
> So if you think `pytest-rerunfailures` is a great addition to `pytest` and
> should be moved to the pytest-dev organization, let us know. :)
>
> Best wishes
> Florian
> ?????????
> Florian Pilz ? fp at gocept.com ? Software Developer
> gocept gmbh & co. kg ? Forsterstra?e 29 ? 06112 Halle (Saale) ? Germany
> http://gocept.com ? Tel +49 345 122 9889 7
> Python, Pyramid, Plone, Zope ? consulting, development, hosting, operations
>
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160202/de684572/attachment.html>

From me at the-compiler.org  Tue Feb  2 09:45:55 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Tue, 2 Feb 2016 15:45:55 +0100
Subject: [pytest-dev] Moving pytest-rerunfailures to pytest-dev
In-Reply-To: <CA+RQFfcHyZuKULNUtPy0v_n0_EykWoeHZucWDTm2FywSK3pWWg@mail.gmail.com>
References: <40229627-C690-41D0-9734-A17EC6B40E3E@gocept.com>
 <CA+RQFfcHyZuKULNUtPy0v_n0_EykWoeHZucWDTm2FywSK3pWWg@mail.gmail.com>
Message-ID: <20160202144555.GF542@tonks>

* Bruno Oliveira <nicoddemus at gmail.com> [2016-02-02 14:39:32 +0000]:
> Could you please transfer ownership to me (@nicoddemus) or Florian
> (@The-Compiler)? You have to transfer to us so we can move it to the
> organization (at least we couldn't figure out another way to do it).

From the GitHub docs[1]:

    Users must have admin or owner rights within the receiving
    organization before they can transfer a repository that they
    individually own. If the user does not already have this level of
    access, a temporary admin team can be created with only the user.
    The user sending the repository is the only one who can perform
    the transfer.

I added a pytest-rerunfailures-admin team and invited @florianpilz in
it. Florian, I think that means you should be able to transfer the
repository now.

Florian

[1] https://help.github.com/articles/transferring-a-repository/#transferring-from-a-user-to-an-organization

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160202/a7e739d5/attachment.sig>

From me at the-compiler.org  Tue Feb  2 09:47:27 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Tue, 2 Feb 2016 15:47:27 +0100
Subject: [pytest-dev] Moving pytest-rerunfailures to pytest-dev
In-Reply-To: <CAAWk_DxrXAzrnjzadWn3trn2mBa=57=snNDwJsdeh5kgCBiS7Q@mail.gmail.com>
References: <40229627-C690-41D0-9734-A17EC6B40E3E@gocept.com>
 <20160202143215.GE542@tonks>
 <CAAWk_DxrXAzrnjzadWn3trn2mBa=57=snNDwJsdeh5kgCBiS7Q@mail.gmail.com>
Message-ID: <20160202144727.GG542@tonks>

* Floris Bruynooghe <floris.bruynooghe at gmail.com> [2016-02-02 14:43:00 +0000]:
> BTW, a more general question. Do we have any policy wrt pypi rights? That
> bit seems rather ad-hoc currently.

CONTRIBUTING says[1]:

    We recommend that each plugin has at least three people who have
    the right to release to pypi.

However in practice this rarely seems to be the case.

Florian

[1] https://github.com/pytest-dev/pytest/blob/master/CONTRIBUTING.rst#id8

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160202/34a5db16/attachment-0001.sig>

From nicoddemus at gmail.com  Tue Feb  2 09:52:48 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Tue, 02 Feb 2016 14:52:48 +0000
Subject: [pytest-dev] Moving pytest-rerunfailures to pytest-dev
In-Reply-To: <20160202144727.GG542@tonks>
References: <40229627-C690-41D0-9734-A17EC6B40E3E@gocept.com>
 <20160202143215.GE542@tonks>
 <CAAWk_DxrXAzrnjzadWn3trn2mBa=57=snNDwJsdeh5kgCBiS7Q@mail.gmail.com>
 <20160202144727.GG542@tonks>
Message-ID: <CA+RQFfcV2jO1vy+OB7EQ=cs2cTc1keUZh3HccK6pLOWpt=1k-g@mail.gmail.com>

Ahh cool, thanks for the research Florian.

I think we should follow that procedure from now on. :)

[]s,

On Tue, Feb 2, 2016 at 12:47 PM Florian Bruhin <me at the-compiler.org> wrote:

> * Floris Bruynooghe <floris.bruynooghe at gmail.com> [2016-02-02 14:43:00
> +0000]:
> > BTW, a more general question. Do we have any policy wrt pypi rights? That
> > bit seems rather ad-hoc currently.
>
> CONTRIBUTING says[1]:
>
>     We recommend that each plugin has at least three people who have
>     the right to release to pypi.
>
> However in practice this rarely seems to be the case.
>
> Florian
>
> [1] https://github.com/pytest-dev/pytest/blob/master/CONTRIBUTING.rst#id8
>
> --
> http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
>    GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
>          I love long mails! | http://email.is-not-s.ms/
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160202/6d88f100/attachment.html>

From opensource at ronnypfannschmidt.de  Tue Feb  2 16:58:16 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Tue, 2 Feb 2016 22:58:16 +0100
Subject: [pytest-dev] Merging Features To Master - tomorrow evening European
 time
Message-ID: <56B12678.1030008@ronnypfannschmidt.de>

Hi everyone,

i think its time to merge features into master,
so the next release would be 2.9.0

any opinions/blockers? else i propose tomorrow evening as merge time.

-- Ronny

From nicoddemus at gmail.com  Tue Feb  2 19:09:22 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Wed, 03 Feb 2016 00:09:22 +0000
Subject: [pytest-dev] Merging Features To Master - tomorrow evening
 European time
In-Reply-To: <56B12678.1030008@ronnypfannschmidt.de>
References: <56B12678.1030008@ronnypfannschmidt.de>
Message-ID: <CA+RQFff6bODrtK9eyiNH6iLVSjqTqwFmhD0kUC-AFQ3rTDqdAA@mail.gmail.com>

I think that's OK.

Do we have a preliminary release date for 2.9? I was thinking we could make
a release candidate and ask people here and in TIP to give it a try and see
if there are any serious regressions before releasing a final 2.9 version.

On Tue, Feb 2, 2016 at 7:58 PM Ronny Pfannschmidt <
opensource at ronnypfannschmidt.de> wrote:

> Hi everyone,
>
> i think its time to merge features into master,
> so the next release would be 2.9.0
>
> any opinions/blockers? else i propose tomorrow evening as merge time.
>
> -- Ronny
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160203/62891c35/attachment.html>

From fp at gocept.com  Wed Feb  3 01:50:00 2016
From: fp at gocept.com (Florian Pilz)
Date: Wed, 3 Feb 2016 07:50:00 +0100
Subject: [pytest-dev] Moving pytest-rerunfailures to pytest-dev
In-Reply-To: <20160202144555.GF542@tonks>
References: <40229627-C690-41D0-9734-A17EC6B40E3E@gocept.com>
 <CA+RQFfcHyZuKULNUtPy0v_n0_EykWoeHZucWDTm2FywSK3pWWg@mail.gmail.com>
 <20160202144555.GF542@tonks>
Message-ID: <E2AC738E-A94C-4645-80B2-18CE8954C11E@gocept.com>

Am 02.02.2016 um 15:45 schrieb Florian Bruhin <me at the-compiler.org>:
> 
> I added a pytest-rerunfailures-admin team and invited @florianpilz in
> it. Florian, I think that means you should be able to transfer the
> repository now.

Thanks, I transferred the repository to pytest-dev. Currently it?s only part of the team ?pytest-rerunfailures-admin?, since I didn?t know how you use teams. Please assign the project to the teams (probably Owners and Contributors).

Since I want to keep the possibility to maintain the project, I guess I should request to join the Contributors team, right?

Florian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160203/b9d0a2de/attachment.sig>

From me at the-compiler.org  Wed Feb  3 02:15:57 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Wed, 3 Feb 2016 08:15:57 +0100
Subject: [pytest-dev] Moving pytest-rerunfailures to pytest-dev
In-Reply-To: <E2AC738E-A94C-4645-80B2-18CE8954C11E@gocept.com>
References: <40229627-C690-41D0-9734-A17EC6B40E3E@gocept.com>
 <CA+RQFfcHyZuKULNUtPy0v_n0_EykWoeHZucWDTm2FywSK3pWWg@mail.gmail.com>
 <20160202144555.GF542@tonks>
 <E2AC738E-A94C-4645-80B2-18CE8954C11E@gocept.com>
Message-ID: <20160203071557.GK542@tonks>

* Florian Pilz <fp at gocept.com> [2016-02-03 07:50:00 +0100]:
> Am 02.02.2016 um 15:45 schrieb Florian Bruhin <me at the-compiler.org>:
> > 
> > I added a pytest-rerunfailures-admin team and invited @florianpilz in
> > it. Florian, I think that means you should be able to transfer the
> > repository now.
> 
> Thanks, I transferred the repository to pytest-dev. Currently it?s
> only part of the team ?pytest-rerunfailures-admin?, since I didn?t
> know how you use teams. Please assign the project to the teams
> (probably Owners and Contributors).
> 
> Since I want to keep the possibility to maintain the project, I
> guess I should request to join the Contributors team, right?

I think this is how it's handled currently:

- Every project has a pytest-xyz-admin team, with its projects admins
  in it, having admin permissions on the repo.

  This was already present, I now also added it as a repo admin team,
  so you should have full permissions to the repo again.

- Every project has a pytest-xyz-developers team, having write (but
  not admin) permission to the repo. I added the team and permissions,
  and it's currently empty. If you want to add any people there, I
  think we'll need to add them to the organization, and then you can
  add them to the team.

- The 'Contributors' group has write access to every project, and
  every project admin is in it. I added it to pytest-rerunfailures,
  and added you to the group.

Bruno, does this sound correct to you? I think it was you who came up
with that scheme, right? Would be nice to have it documented
somewhere, but I don't really know where. Maybe in CONTRIBUTING.

Florian

(We have at least 3 Florians and 1 Floris in the team now... Phew :D)

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160203/bf9265e9/attachment.sig>

From holger at merlinux.eu  Wed Feb  3 02:46:12 2016
From: holger at merlinux.eu (holger krekel)
Date: Wed, 3 Feb 2016 07:46:12 +0000
Subject: [pytest-dev] Merging Features To Master - tomorrow evening
 European time
In-Reply-To: <56B12678.1030008@ronnypfannschmidt.de>
References: <56B12678.1030008@ronnypfannschmidt.de>
Message-ID: <20160203074612.GQ3793@merlinux.eu>

On Tue, Feb 02, 2016 at 22:58 +0100, Ronny Pfannschmidt wrote:
> Hi everyone,
> 
> i think its time to merge features into master,
> so the next release would be 2.9.0
> any opinions/blockers? else i propose tomorrow evening as merge time.

I'd assume we rather merge master into features, do the release and then
merge back features into master.  Is there a reason to do it the other way
round?

best,
holger

> -- Ronny
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
> 

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From opensource at ronnypfannschmidt.de  Wed Feb  3 04:29:18 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Wed, 03 Feb 2016 10:29:18 +0100
Subject: [pytest-dev] Merging Features To Master - tomorrow evening
 European time
In-Reply-To: <20160203074612.GQ3793@merlinux.eu>
References: <56B12678.1030008@ronnypfannschmidt.de>
 <20160203074612.GQ3793@merlinux.eu>
Message-ID: <ACDBE61C-5283-4B90-BFF8-D41D1512A6AA@ronnypfannschmidt.de>

Just that i'd like all releases to come from master.

Best,
Ronny


Am 3. Februar 2016 08:46:12 MEZ, schrieb holger krekel <holger at merlinux.eu>:
>On Tue, Feb 02, 2016 at 22:58 +0100, Ronny Pfannschmidt wrote:
>> Hi everyone,
>> 
>> i think its time to merge features into master,
>> so the next release would be 2.9.0
>> any opinions/blockers? else i propose tomorrow evening as merge time.
>
>I'd assume we rather merge master into features, do the release and
>then
>merge back features into master.  Is there a reason to do it the other
>way
>round?
>
>best,
>holger
>
>> -- Ronny
>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>> 
>
>-- 
>about me:    http://holgerkrekel.net/about-me/
>contracting: http://merlinux.eu

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160203/c740b189/attachment-0001.html>

From holger at merlinux.eu  Wed Feb  3 05:00:27 2016
From: holger at merlinux.eu (holger krekel)
Date: Wed, 3 Feb 2016 10:00:27 +0000
Subject: [pytest-dev] RFC: pytest sprint indiegogo page (draft)
Message-ID: <20160203100027.GT3793@merlinux.eu>

Hey all,

i've done a indiegogo sprint page which is still in draft mode, see here:

    https://www.indiegogo.com/project/preview/ee72990c#/

I also invited Bruno, Brianna, Floris and Florian as editors.
If other wants to help edit, or comment on the setup, please send
a mail here.  I am particular unsure about the "perks" ...

I'd like to get it online tomorrow or latest friday if possible.

cheers,
holger

--
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From mail at florian-schulze.net  Wed Feb  3 05:05:02 2016
From: mail at florian-schulze.net (Florian Schulze)
Date: Wed, 03 Feb 2016 11:05:02 +0100
Subject: [pytest-dev] pytest sprint indiegogo page (draft)
In-Reply-To: <20160203100027.GT3793@merlinux.eu>
References: <20160203100027.GT3793@merlinux.eu>
Message-ID: <B05E7626-2B2B-4E3E-A8DA-F257B02A421F@florian-schulze.net>

Looks good overall. I think the perks are just fine.

I think there is a typo: Brianna Laughner should be Brianna Laugher if 
I'm not mistaken.

Regards,
Florian Schulze


On 3 Feb 2016, at 11:00, holger krekel wrote:

> Hey all,
>
> i've done a indiegogo sprint page which is still in draft mode, see 
> here:
>
>   https://www.indiegogo.com/project/preview/ee72990c#/
>
> I also invited Bruno, Brianna, Floris and Florian as editors.
> If other wants to help edit, or comment on the setup, please send
> a mail here.  I am particular unsure about the "perks" ...
>
> I'd like to get it online tomorrow or latest friday if possible.
>
> cheers,
> holger
>
> --
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev

From me at the-compiler.org  Wed Feb  3 05:20:47 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Wed, 3 Feb 2016 11:20:47 +0100
Subject: [pytest-dev] RFC: pytest sprint indiegogo page (draft)
In-Reply-To: <20160203100027.GT3793@merlinux.eu>
References: <20160203100027.GT3793@merlinux.eu>
Message-ID: <20160203102047.GL542@tonks>

Hey Holger,

* holger krekel <holger at merlinux.eu> [2016-02-03 10:00:27 +0000]:
> Hey all,
> 
> i've done a indiegogo sprint page which is still in draft mode, see here:
> 
>     https://www.indiegogo.com/project/preview/ee72990c#/

Yay, thank you! \o/

    Floris Bruhin, Switzerland
    Florian Bruynooghe, UK

*cough* *cough* ;)

If you're busy I can fix it myself later, still haven't figured out
that "sync password manager database between multiple machines" thing
reliably.

Is this "flexible funding"? It seems to me like it isn't, i.e. if we
don't get the 8kEUR, we'll get no money at all? Might make more sense
to get the money even if we reach, say, 5kEUR, and then see what we
can do to make it happen with that?

> I am particular unsure about the "perks" ...

Stickers sound good. Maybe T-Shirts as well, for something between
EUR 50 and EUR 500? If I wasn't involved in pytest but liking it a
lot, I'd be willing to spend EUR 100 or so, but I'd like something
more than 10 stickers in return ;)

OTOH it's some work and logistic overhead someone would need to
tackle.

"fix an issue" sounds a bit problematic. I'd rather not give the
blanket promise of fixing a particular thing or introducing a feature,
this has the potential to "force" us to do things nobody considers a
good idea, if things go bad. Maybe more something like "vote on a
specific bug/feature we'll consider a priority"?

What about some document about the sprint where funders will be
listed, with higher perks with (company) logo/URL? That's something
I've seen a lot with other campaigns and seems reasonable to me.

What do you think about perks for pytest trainings? Maybe that'd be a
good incentive for companies - fund the sprint *and* get a training
for pytest (or pytest/tox/devpi - not including travel/stay for the
training of course).

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160203/9e6613ec/attachment.sig>

From holger at merlinux.eu  Wed Feb  3 05:31:31 2016
From: holger at merlinux.eu (holger krekel)
Date: Wed, 3 Feb 2016 10:31:31 +0000
Subject: [pytest-dev] RFC: pytest sprint indiegogo page (draft)
In-Reply-To: <20160203102047.GL542@tonks>
References: <20160203100027.GT3793@merlinux.eu>
 <20160203102047.GL542@tonks>
Message-ID: <20160203103131.GW3793@merlinux.eu>

On Wed, Feb 03, 2016 at 11:20 +0100, Florian Bruhin wrote:
> Hey Holger,
> 
> * holger krekel <holger at merlinux.eu> [2016-02-03 10:00:27 +0000]:
> > Hey all,
> > 
> > i've done a indiegogo sprint page which is still in draft mode, see here:
> > 
> >     https://www.indiegogo.com/project/preview/ee72990c#/
> 
> Yay, thank you! \o/
> 
>     Floris Bruhin, Switzerland
>     Florian Bruynooghe, UK
> 
> *cough* *cough* ;)

fixed :)

> If you're busy I can fix it myself later, still haven't figured out
> that "sync password manager database between multiple machines" thing
> reliably.
> 
> Is this "flexible funding"? It seems to me like it isn't, i.e. if we
> don't get the 8kEUR, we'll get no money at all? Might make more sense
> to get the money even if we reach, say, 5kEUR, and then see what we
> can do to make it happen with that?

I intended flexible funding certainly.  Hopefully fixed now.

> > I am particular unsure about the "perks" ...
> 
> Stickers sound good. Maybe T-Shirts as well, for something between
> EUR 50 and EUR 500? If I wasn't involved in pytest but liking it a
> lot, I'd be willing to spend EUR 100 or so, but I'd like something
> more than 10 stickers in return ;)
> 
> OTOH it's some work and logistic overhead someone would need to
> tackle.
> 
> "fix an issue" sounds a bit problematic. I'd rather not give the
> blanket promise of fixing a particular thing or introducing a feature,
> this has the potential to "force" us to do things nobody considers a
> good idea, if things go bad. Maybe more something like "vote on a
> specific bug/feature we'll consider a priority"?

"tackle an issue?"

> What about some document about the sprint where funders will be
> listed, with higher perks with (company) logo/URL? That's something
> I've seen a lot with other campaigns and seems reasonable to me.

Yes, i am fine.

> What do you think about perks for pytest trainings? Maybe that'd be a
> good incentive for companies - fund the sprint *and* get a training
> for pytest (or pytest/tox/devpi - not including travel/stay for the
> training of course).

That would have to be quite a high perk, not sure that fits for this
campaign.

holger


> 
> Florian
> 
> -- 
> http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
>    GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
>          I love long mails! | http://email.is-not-s.ms/



-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From brianna.laugher at gmail.com  Wed Feb  3 07:01:40 2016
From: brianna.laugher at gmail.com (Brianna Laugher)
Date: Wed, 3 Feb 2016 23:01:40 +1100
Subject: [pytest-dev] RFC: pytest sprint indiegogo page (draft)
In-Reply-To: <20160203100027.GT3793@merlinux.eu>
References: <20160203100027.GT3793@merlinux.eu>
Message-ID: <CAPjwCjtbJxhYrO1SEnzM2DVnWsr1TjHLRzUoA=hQDfbS6+HwkQ@mail.gmail.com>

Hi,

I put some ideas here previously
https://github.com/pytest-dev/pytest/wiki/2016-dev-sprint

In particular, I saw an idea once which I thought was clever, in cases like
this where there is little in the way of material offers. You can have
several perks at the same level, and treat them as "votes".  "If 10 people
support at this level, we will do X." In this case, I thought these could
be "votes" for a broad area of focus, such as
- Speed/performance/xdist
- plugins
- 'unloved corners' (Unicode/Windows/doctests)
- documentation
- resolving pytest/py.test (maybe??!)

Of course that wouldn't mean it's the only thing that gets done, but it is
a small way people can influence what happens.

Including some photos may be nice too
https://github.com/pytest-dev/pytest/wiki/Meetings

Holger, I think it would be useful if you explicitly say you are the
founder of pytest and give some context of your authority for the casual
reader :)

Also I think tying it a 3.0 release would be a pleasing target!

cheers
Brianna


On 3 February 2016 at 21:00, holger krekel <holger at merlinux.eu> wrote:

> Hey all,
>
> i've done a indiegogo sprint page which is still in draft mode, see here:
>
>     https://www.indiegogo.com/project/preview/ee72990c#/
>
> I also invited Bruno, Brianna, Floris and Florian as editors.
> If other wants to help edit, or comment on the setup, please send
> a mail here.  I am particular unsure about the "perks" ...
>
> I'd like to get it online tomorrow or latest friday if possible.
>
> cheers,
> holger
>
> --
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160203/2c06704f/attachment-0001.html>

From flub at devork.be  Wed Feb  3 07:02:28 2016
From: flub at devork.be (Floris Bruynooghe)
Date: Wed, 3 Feb 2016 12:02:28 +0000
Subject: [pytest-dev] RFC: pytest sprint indiegogo page (draft)
In-Reply-To: <20160203103131.GW3793@merlinux.eu>
References: <20160203100027.GT3793@merlinux.eu> <20160203102047.GL542@tonks>
 <20160203103131.GW3793@merlinux.eu>
Message-ID: <CAAWk_DzbkGLHnd67icW9ZQDStX+siCOGMPG45RB0JabSxaYr8w@mail.gmail.com>

Hi,

Overall looks great!

On 3 February 2016 at 10:31, holger krekel <holger at merlinux.eu> wrote:
> On Wed, Feb 03, 2016 at 11:20 +0100, Florian Bruhin wrote:
>> * holger krekel <holger at merlinux.eu> [2016-02-03 10:00:27 +0000]:
>> > I am particular unsure about the "perks" ...
>>
>> Stickers sound good. Maybe T-Shirts as well, for something between
>> EUR 50 and EUR 500? If I wasn't involved in pytest but liking it a
>> lot, I'd be willing to spend EUR 100 or so, but I'd like something
>> more than 10 stickers in return ;)
>>
>> OTOH it's some work and logistic overhead someone would need to
>> tackle.
>>
>> "fix an issue" sounds a bit problematic. I'd rather not give the
>> blanket promise of fixing a particular thing or introducing a feature,
>> this has the potential to "force" us to do things nobody considers a
>> good idea, if things go bad. Maybe more something like "vote on a
>> specific bug/feature we'll consider a priority"?
>
> "tackle an issue?"

I agree with this worry, "Prioritise an issue" seems a safer way to
say this.  And maybe hint about having a chat with us first if you
feel strongly to avoid disappointment.

Secondly do we need limits on the number of issues and topics we can
have?  It's kind of odd to limit but likewise we can't have 20 topics
and 200 issues as we'll just have to disappoint (and to be honest, we
might be more motivated working on other bits ;-)).


>> What about some document about the sprint where funders will be
>> listed, with higher perks with (company) logo/URL? That's something
>> I've seen a lot with other campaigns and seems reasonable to me.
>
> Yes, i am fine.

Can we make being listed as supporter opt-in for all levels?  Then we
can add logo and links for higher level sponsors (?500-?1000).



I also wonder if it's worth going into more detail about what we might
work on, currently seems rather vague.  For example I'd like to work
on the "failing tests from finalizers"/addverifier which I'd be happy
to summarise in a paragraph.  It might give people something more
explicit too look forward too, rather then just the next release.
Just the next release will happen anyway, maybe a bit later or with a
fewer features but it will happen.


Regards,
Floris

From holger at merlinux.eu  Wed Feb  3 07:21:38 2016
From: holger at merlinux.eu (holger krekel)
Date: Wed, 3 Feb 2016 12:21:38 +0000
Subject: [pytest-dev] RFC: pytest sprint indiegogo page (draft)
In-Reply-To: <CAAWk_DzbkGLHnd67icW9ZQDStX+siCOGMPG45RB0JabSxaYr8w@mail.gmail.com>
References: <20160203100027.GT3793@merlinux.eu> <20160203102047.GL542@tonks>
 <20160203103131.GW3793@merlinux.eu>
 <CAAWk_DzbkGLHnd67icW9ZQDStX+siCOGMPG45RB0JabSxaYr8w@mail.gmail.com>
Message-ID: <20160203122138.GA3793@merlinux.eu>

On Wed, Feb 03, 2016 at 12:02 +0000, Floris Bruynooghe wrote:
> Hi,
> 
> Overall looks great!
> 
> On 3 February 2016 at 10:31, holger krekel <holger at merlinux.eu> wrote:
> > On Wed, Feb 03, 2016 at 11:20 +0100, Florian Bruhin wrote:
> >> * holger krekel <holger at merlinux.eu> [2016-02-03 10:00:27 +0000]:
> >> > I am particular unsure about the "perks" ...
> >>
> >> Stickers sound good. Maybe T-Shirts as well, for something between
> >> EUR 50 and EUR 500? If I wasn't involved in pytest but liking it a
> >> lot, I'd be willing to spend EUR 100 or so, but I'd like something
> >> more than 10 stickers in return ;)
> >>
> >> OTOH it's some work and logistic overhead someone would need to
> >> tackle.
> >>
> >> "fix an issue" sounds a bit problematic. I'd rather not give the
> >> blanket promise of fixing a particular thing or introducing a feature,
> >> this has the potential to "force" us to do things nobody considers a
> >> good idea, if things go bad. Maybe more something like "vote on a
> >> specific bug/feature we'll consider a priority"?
> >
> > "tackle an issue?"
> 
> I agree with this worry, "Prioritise an issue" seems a safer way to
> say this.  And maybe hint about having a chat with us first if you
> feel strongly to avoid disappointment.
> 
> Secondly do we need limits on the number of issues and topics we can
> have?  It's kind of odd to limit but likewise we can't have 20 topics
> and 200 issues as we'll just have to disappoint (and to be honest, we
> might be more motivated working on other bits ;-)).

sure, we can limit.  If we got 20 topics and 200 issues that'd be 120K Euros
in funding, though ;)  

> >> What about some document about the sprint where funders will be
> >> listed, with higher perks with (company) logo/URL? That's something
> >> I've seen a lot with other campaigns and seems reasonable to me.
> >
> > Yes, i am fine.
> 
> Can we make being listed as supporter opt-in for all levels?  Then we
> can add logo and links for higher level sponsors (?500-?1000).

no clue if that's possible, could you look at the interface yourself? (i
invited you as editor)

> I also wonder if it's worth going into more detail about what we might
> work on, currently seems rather vague.  For example I'd like to work
> on the "failing tests from finalizers"/addverifier which I'd be happy
> to summarise in a paragraph.  It might give people something more
> explicit too look forward too, rather then just the next release.
> Just the next release will happen anyway, maybe a bit later or with a
> fewer features but it will happen.

Sure, it's intentionally vague as i don't want the campaign to predetermine
everything.  Adding paragraphs about intentions in a separate section
makes sense i guess.

holger

> Regards,
> Floris
> 

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From holger at merlinux.eu  Wed Feb  3 08:57:05 2016
From: holger at merlinux.eu (holger krekel)
Date: Wed, 3 Feb 2016 13:57:05 +0000
Subject: [pytest-dev] RFC: pytest sprint indiegogo page (draft)
In-Reply-To: <CAPjwCjtbJxhYrO1SEnzM2DVnWsr1TjHLRzUoA=hQDfbS6+HwkQ@mail.gmail.com>
References: <20160203100027.GT3793@merlinux.eu>
 <CAPjwCjtbJxhYrO1SEnzM2DVnWsr1TjHLRzUoA=hQDfbS6+HwkQ@mail.gmail.com>
Message-ID: <20160203135705.GB3793@merlinux.eu>

Hi Brianna,

On Wed, Feb 03, 2016 at 23:01 +1100, Brianna Laugher wrote:
> Hi,
> 
> I put some ideas here previously
> https://github.com/pytest-dev/pytest/wiki/2016-dev-sprint

yes, saw them and used some of them in the campaign draft.

> In particular, I saw an idea once which I thought was clever, in cases like
> this where there is little in the way of material offers. You can have
> several perks at the same level, and treat them as "votes".  "If 10 people
> support at this level, we will do X." In this case, I thought these could
> be "votes" for a broad area of focus, such as
> - Speed/performance/xdist
> - plugins
> - 'unloved corners' (Unicode/Windows/doctests)
> - documentation
> - resolving pytest/py.test (maybe??!)
> 
> Of course that wouldn't mean it's the only thing that gets done, but it is
> a small way people can influence what happens.

TBH I want us to get some general support for doing a sprint without much
attached. We have provided already a lot for free what is used by ten-thousands
of companies and individuals. 

But if we go for voting let's keep it for three options, maybe:

- speed/performance/xdist
- improved fixture system 
- documentation, more examples

?

> Including some photos may be nice too
> https://github.com/pytest-dev/pytest/wiki/Meetings

I did include the pytest logo and the group picture we took at fosdem or
EP2015. It just doesn't show in the draft, does it?

> Holger, I think it would be useful if you explicitly say you are the
> founder of pytest and give some context of your authority for the casual
> reader :)

i mentioned it know in "role".

> Also I think tying it a 3.0 release would be a pleasing target!

Makes sense. Maybe even as a tag line "pytest-sprint 2016, accelerate
pytest-3.0"?

best,
holger

> cheers
> Brianna
> 
> 
> On 3 February 2016 at 21:00, holger krekel <holger at merlinux.eu> wrote:
> 
> > Hey all,
> >
> > i've done a indiegogo sprint page which is still in draft mode, see here:
> >
> >     https://www.indiegogo.com/project/preview/ee72990c#/
> >
> > I also invited Bruno, Brianna, Floris and Florian as editors.
> > If other wants to help edit, or comment on the setup, please send
> > a mail here.  I am particular unsure about the "perks" ...
> >
> > I'd like to get it online tomorrow or latest friday if possible.
> >
> > cheers,
> > holger
> >
> > --
> > about me:    http://holgerkrekel.net/about-me/
> > contracting: http://merlinux.eu
> > _______________________________________________
> > 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/

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From nicoddemus at gmail.com  Wed Feb  3 10:03:59 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Wed, 03 Feb 2016 15:03:59 +0000
Subject: [pytest-dev] Moving pytest-rerunfailures to pytest-dev
In-Reply-To: <20160203071557.GK542@tonks>
References: <40229627-C690-41D0-9734-A17EC6B40E3E@gocept.com>
 <CA+RQFfcHyZuKULNUtPy0v_n0_EykWoeHZucWDTm2FywSK3pWWg@mail.gmail.com>
 <20160202144555.GF542@tonks> <E2AC738E-A94C-4645-80B2-18CE8954C11E@gocept.com>
 <20160203071557.GK542@tonks>
Message-ID: <CA+RQFfeYKRevvDSTh7yR24KErtksBgNdTDdhcYLpUEcG-vSiNw@mail.gmail.com>

On Wed, Feb 3, 2016 at 5:15 AM Florian Bruhin <me at the-compiler.org> wrote:

> - Every project has a pytest-xyz-admin team, with its projects admins
>   in it, having admin permissions on the repo.
>
>   This was already present, I now also added it as a repo admin team,
>   so you should have full permissions to the repo again.
>
> - Every project has a pytest-xyz-developers team, having write (but
>   not admin) permission to the repo. I added the team and permissions,
>   and it's currently empty. If you want to add any people there, I
>   think we'll need to add them to the organization, and then you can
>   add them to the team.
>
> - The 'Contributors' group has write access to every project, and
>   every project admin is in it. I added it to pytest-rerunfailures,
>   and added you to the group.
>
> Bruno, does this sound correct to you? I think it was you who came up
> with that scheme, right?


That sounds reasonable, but IIRC who came up with this scheme was Bubenkov.


> Would be nice to have it documented
> somewhere, but I don't really know where. Maybe in CONTRIBUTING.
>

Sure, sounds like a good place for this information. Posted a note to #1282
to add it to that doc.

(We have at least 3 Florians and 1 Floris in the team now... Phew :D)
>

Heh! :D

Bruno.


>
> --
> http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
>    GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
>          I love long mails! | http://email.is-not-s.ms/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160203/6f9ef048/attachment-0001.html>

From holger at merlinux.eu  Wed Feb  3 11:23:30 2016
From: holger at merlinux.eu (holger krekel)
Date: Wed, 3 Feb 2016 16:23:30 +0000
Subject: [pytest-dev] RFC: pytest sprint indiegogo page (draft)
In-Reply-To: <20160203100027.GT3793@merlinux.eu>
References: <20160203100027.GT3793@merlinux.eu>
Message-ID: <20160203162330.GE3793@merlinux.eu>

Hey all,

i adapted the indiegogo draft page below according to suggestions here.
I didn't include yet Brianna's idea on allowing "voting", see my comment
to her mail.

Feel free to edit or comment here further.  I'd like to publish tomorrow
european evening and i think pytestorg/Brianna should tweet then and we
retweet or so.

Also i think we should put a banner on all pytest.org pages, what do you
think?  Anything else? 

best,
holger


On Wed, Feb 03, 2016 at 10:00 +0000, holger krekel wrote:
> Hey all,
> 
> i've done a indiegogo sprint page which is still in draft mode, see here:
> 
>     https://www.indiegogo.com/project/preview/ee72990c#/
> 
> I also invited Bruno, Brianna, Floris and Florian as editors.
> If other wants to help edit, or comment on the setup, please send
> a mail here.  I am particular unsure about the "perks" ...
> 
> I'd like to get it online tomorrow or latest friday if possible.
> 
> cheers,
> holger
> 
> --
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
> 

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From me at the-compiler.org  Wed Feb  3 11:32:00 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Wed, 3 Feb 2016 17:32:00 +0100
Subject: [pytest-dev] RFC: pytest sprint indiegogo page (draft)
In-Reply-To: <20160203162330.GE3793@merlinux.eu>
References: <20160203100027.GT3793@merlinux.eu>
 <20160203162330.GE3793@merlinux.eu>
Message-ID: <20160203163200.GN542@tonks>

* holger krekel <holger at merlinux.eu> [2016-02-03 16:23:30 +0000]:
> Also i think we should put a banner on all pytest.org pages, what do you
> think?  Anything else?

Brainstorming some ideas (I'm not sure all of those are good):

- Sending a mail to python-announce (it says "announcements related to
  the Python programming language", not just releases, after all).
- Same as above, for testing-in-python
- Putting it into the #pylib topic
- Maybe explicitly writing a mail to some companies using pytest
  extensively? Even more so if they have some kind of opensource
  advocate person, or person active in our communities
  (Mozilla/davehunt comes to mind, I'm sure there are more)
- Mentioning it as a "PS:" for our next release annoucement (might be
  a less agressive version of #1/#2)
- Mentioning it prominently in the README (i.e. GitHub and/or PyPI)
- Talking to Nadia Eghbal[1] who was writing those awesome opensource
  funding articles on Medium.
- Talking to the PSF which seems to have some budget for sprints

[1] https://medium.com/@nayafia

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160203/d4b16f51/attachment.sig>

From brianna.laugher at gmail.com  Wed Feb  3 16:56:04 2016
From: brianna.laugher at gmail.com (Brianna Laugher)
Date: Thu, 4 Feb 2016 08:56:04 +1100
Subject: [pytest-dev] RFC: pytest sprint indiegogo page (draft)
In-Reply-To: <20160203162330.GE3793@merlinux.eu>
References: <20160203100027.GT3793@merlinux.eu>
 <20160203162330.GE3793@merlinux.eu>
Message-ID: <CAPjwCju9dM-Vi_miAP3AhfahC3gUgZMaarKdQjjsinTTxbKq_w@mail.gmail.com>

I think a dedicated page on the pytest site is a good idea (as well as a
banner), then when it is over we can put the supporters names there (if
they wish).

55 days is a long time, maybe a 30 day campaign is better?

I would suggest to include even more context about what pytest is, maybe
some numbers like pypi downloads, founded in 200x.

Cheers
Brianna
On 04/02/2016 3:23 AM, "holger krekel" <holger at merlinux.eu> wrote:

> Hey all,
>
> i adapted the indiegogo draft page below according to suggestions here.
> I didn't include yet Brianna's idea on allowing "voting", see my comment
> to her mail.
>
> Feel free to edit or comment here further.  I'd like to publish tomorrow
> european evening and i think pytestorg/Brianna should tweet then and we
> retweet or so.
>
> Also i think we should put a banner on all pytest.org pages, what do you
> think?  Anything else?
>
> best,
> holger
>
>
> On Wed, Feb 03, 2016 at 10:00 +0000, holger krekel wrote:
> > Hey all,
> >
> > i've done a indiegogo sprint page which is still in draft mode, see here:
> >
> >     https://www.indiegogo.com/project/preview/ee72990c#/
> >
> > I also invited Bruno, Brianna, Floris and Florian as editors.
> > If other wants to help edit, or comment on the setup, please send
> > a mail here.  I am particular unsure about the "perks" ...
> >
> > I'd like to get it online tomorrow or latest friday if possible.
> >
> > cheers,
> > holger
> >
> > --
> > about me:    http://holgerkrekel.net/about-me/
> > contracting: http://merlinux.eu
> > _______________________________________________
> > pytest-dev mailing list
> > pytest-dev at python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
> >
>
> --
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160204/7a5311ed/attachment.html>

From flub at devork.be  Wed Feb  3 17:21:10 2016
From: flub at devork.be (Floris Bruynooghe)
Date: Wed, 3 Feb 2016 22:21:10 +0000
Subject: [pytest-dev] RFC: pytest sprint indiegogo page (draft)
In-Reply-To: <20160203162330.GE3793@merlinux.eu>
References: <20160203100027.GT3793@merlinux.eu>
 <20160203162330.GE3793@merlinux.eu>
Message-ID: <CAAWk_DwrGB1ATnTCVG3o3WBwYCmFo_T5kDY-Hazoem+WemN9jw@mail.gmail.com>

On 3 February 2016 at 16:23, holger krekel <holger at merlinux.eu> wrote:
> Feel free to edit or comment here further.  I'd like to publish tomorrow
> european evening and i think pytestorg/Brianna should tweet then and we
> retweet or so.

Sounds good, I added a line towards the end of the story page about
supporters being able to opt-in to be credited.  I couldn't find a way
to get this automatically so we'll have to do this manually by email.


> Also i think we should put a banner on all pytest.org pages, what do you
> think?  Anything else?

The banner seems like a good plan to me.  Maybe a good reason for me
to dust off my blog as well :-).

From flub at devork.be  Wed Feb  3 17:31:45 2016
From: flub at devork.be (Floris Bruynooghe)
Date: Wed, 3 Feb 2016 22:31:45 +0000
Subject: [pytest-dev] RFC: pytest sprint indiegogo page (draft)
In-Reply-To: <CAAWk_DwrGB1ATnTCVG3o3WBwYCmFo_T5kDY-Hazoem+WemN9jw@mail.gmail.com>
References: <20160203100027.GT3793@merlinux.eu>
 <20160203162330.GE3793@merlinux.eu>
 <CAAWk_DwrGB1ATnTCVG3o3WBwYCmFo_T5kDY-Hazoem+WemN9jw@mail.gmail.com>
Message-ID: <CAAWk_Dw_-ByUJCTVd_AEoWxP08cg1yQP99xBHWB=DAEWdpJ2ig@mail.gmail.com>

I've also changed the picture as apparently it needs to be 620x413 so
the previous one was zoomed to that size which left some people out.
I'm no image person so it's done very naively and the spare space is
just transparent (I hope), it looks reasonable I think.  But if
someone can do better please do!


On 3 February 2016 at 22:21, Floris Bruynooghe <flub at devork.be> wrote:
> On 3 February 2016 at 16:23, holger krekel <holger at merlinux.eu> wrote:
>> Feel free to edit or comment here further.  I'd like to publish tomorrow
>> european evening and i think pytestorg/Brianna should tweet then and we
>> retweet or so.
>
> Sounds good, I added a line towards the end of the story page about
> supporters being able to opt-in to be credited.  I couldn't find a way
> to get this automatically so we'll have to do this manually by email.
>
>
>> Also i think we should put a banner on all pytest.org pages, what do you
>> think?  Anything else?
>
> The banner seems like a good plan to me.  Maybe a good reason for me
> to dust off my blog as well :-).

From nicoddemus at gmail.com  Wed Feb  3 19:26:03 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 04 Feb 2016 00:26:03 +0000
Subject: [pytest-dev] RFC: pytest sprint indiegogo page (draft)
In-Reply-To: <20160203102047.GL542@tonks>
References: <20160203100027.GT3793@merlinux.eu> <20160203102047.GL542@tonks>
Message-ID: <CA+RQFffJS6jtpwjJhck8fx6k4z+FWt4AW_L1PPY0FyE5chm6Zg@mail.gmail.com>

Hi all,

Sorry for chipping in so late, I didn't have a chance of looking more
carefully at the draft until now.

I think it looks great so far, and I like most of the suggestions given by
others. I would like to stress on the part about it being flexible funding
though, as I think this sprint should happen even if not all the funding we
ask for is reached, even if that means some people can't attend the sprint
(myself included of course). After all, better to have a sprint with most
developers present than not having a sprint at all. :)

Cheers,
Bruno.


On Wed, Feb 3, 2016 at 8:20 AM Florian Bruhin <me at the-compiler.org> wrote:

> Hey Holger,
>
> * holger krekel <holger at merlinux.eu> [2016-02-03 10:00:27 +0000]:
> > Hey all,
> >
> > i've done a indiegogo sprint page which is still in draft mode, see here:
> >
> >     https://www.indiegogo.com/project/preview/ee72990c#/
>
> Yay, thank you! \o/
>
>     Floris Bruhin, Switzerland
>     Florian Bruynooghe, UK
>
> *cough* *cough* ;)
>
> If you're busy I can fix it myself later, still haven't figured out
> that "sync password manager database between multiple machines" thing
> reliably.
>
> Is this "flexible funding"? It seems to me like it isn't, i.e. if we
> don't get the 8kEUR, we'll get no money at all? Might make more sense
> to get the money even if we reach, say, 5kEUR, and then see what we
> can do to make it happen with that?
>
> > I am particular unsure about the "perks" ...
>
> Stickers sound good. Maybe T-Shirts as well, for something between
> EUR 50 and EUR 500? If I wasn't involved in pytest but liking it a
> lot, I'd be willing to spend EUR 100 or so, but I'd like something
> more than 10 stickers in return ;)
>
> OTOH it's some work and logistic overhead someone would need to
> tackle.
>
> "fix an issue" sounds a bit problematic. I'd rather not give the
> blanket promise of fixing a particular thing or introducing a feature,
> this has the potential to "force" us to do things nobody considers a
> good idea, if things go bad. Maybe more something like "vote on a
> specific bug/feature we'll consider a priority"?
>
> What about some document about the sprint where funders will be
> listed, with higher perks with (company) logo/URL? That's something
> I've seen a lot with other campaigns and seems reasonable to me.
>
> What do you think about perks for pytest trainings? Maybe that'd be a
> good incentive for companies - fund the sprint *and* get a training
> for pytest (or pytest/tox/devpi - not including travel/stay for the
> training of course).
>
> Florian
>
> --
> http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
>    GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
>          I love long mails! | http://email.is-not-s.ms/
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160204/b5fe4953/attachment-0001.html>

From holger at merlinux.eu  Thu Feb  4 05:14:11 2016
From: holger at merlinux.eu (holger krekel)
Date: Thu, 4 Feb 2016 10:14:11 +0000
Subject: [pytest-dev] RFC: pytest sprint indiegogo page (draft)
In-Reply-To: <CA+RQFffJS6jtpwjJhck8fx6k4z+FWt4AW_L1PPY0FyE5chm6Zg@mail.gmail.com>
References: <20160203100027.GT3793@merlinux.eu> <20160203102047.GL542@tonks>
 <CA+RQFffJS6jtpwjJhck8fx6k4z+FWt4AW_L1PPY0FyE5chm6Zg@mail.gmail.com>
Message-ID: <20160204101411.GI3793@merlinux.eu>

On Thu, Feb 04, 2016 at 00:26 +0000, Bruno Oliveira wrote:
> Hi all,
> 
> Sorry for chipping in so late, I didn't have a chance of looking more
> carefully at the draft until now.
> 
> I think it looks great so far, and I like most of the suggestions given by
> others. I would like to stress on the part about it being flexible funding
> though, as I think this sprint should happen even if not all the funding we
> ask for is reached, even if that means some people can't attend the sprint
> (myself included of course). After all, better to have a sprint with most
> developers present than not having a sprint at all. :)

Totally agree.  I configured it as flexible funding almost from the beginning.  
If you look at the campaign as an editor can you see that?
What makes you and others believe it is fixed funding?

holger



> Cheers,
> Bruno.
> 
> 
> On Wed, Feb 3, 2016 at 8:20 AM Florian Bruhin <me at the-compiler.org> wrote:
> 
> > Hey Holger,
> >
> > * holger krekel <holger at merlinux.eu> [2016-02-03 10:00:27 +0000]:
> > > Hey all,
> > >
> > > i've done a indiegogo sprint page which is still in draft mode, see here:
> > >
> > >     https://www.indiegogo.com/project/preview/ee72990c#/
> >
> > Yay, thank you! \o/
> >
> >     Floris Bruhin, Switzerland
> >     Florian Bruynooghe, UK
> >
> > *cough* *cough* ;)
> >
> > If you're busy I can fix it myself later, still haven't figured out
> > that "sync password manager database between multiple machines" thing
> > reliably.
> >
> > Is this "flexible funding"? It seems to me like it isn't, i.e. if we
> > don't get the 8kEUR, we'll get no money at all? Might make more sense
> > to get the money even if we reach, say, 5kEUR, and then see what we
> > can do to make it happen with that?
> >
> > > I am particular unsure about the "perks" ...
> >
> > Stickers sound good. Maybe T-Shirts as well, for something between
> > EUR 50 and EUR 500? If I wasn't involved in pytest but liking it a
> > lot, I'd be willing to spend EUR 100 or so, but I'd like something
> > more than 10 stickers in return ;)
> >
> > OTOH it's some work and logistic overhead someone would need to
> > tackle.
> >
> > "fix an issue" sounds a bit problematic. I'd rather not give the
> > blanket promise of fixing a particular thing or introducing a feature,
> > this has the potential to "force" us to do things nobody considers a
> > good idea, if things go bad. Maybe more something like "vote on a
> > specific bug/feature we'll consider a priority"?
> >
> > What about some document about the sprint where funders will be
> > listed, with higher perks with (company) logo/URL? That's something
> > I've seen a lot with other campaigns and seems reasonable to me.
> >
> > What do you think about perks for pytest trainings? Maybe that'd be a
> > good incentive for companies - fund the sprint *and* get a training
> > for pytest (or pytest/tox/devpi - not including travel/stay for the
> > training of course).
> >
> > Florian
> >
> > --
> > http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
> >    GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
> >          I love long mails! | http://email.is-not-s.ms/
> > _______________________________________________
> > 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


-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From holger at merlinux.eu  Thu Feb  4 05:15:16 2016
From: holger at merlinux.eu (holger krekel)
Date: Thu, 4 Feb 2016 10:15:16 +0000
Subject: [pytest-dev] RFC: pytest sprint indiegogo page (draft)
In-Reply-To: <CAPjwCju9dM-Vi_miAP3AhfahC3gUgZMaarKdQjjsinTTxbKq_w@mail.gmail.com>
References: <20160203100027.GT3793@merlinux.eu>
 <20160203162330.GE3793@merlinux.eu>
 <CAPjwCju9dM-Vi_miAP3AhfahC3gUgZMaarKdQjjsinTTxbKq_w@mail.gmail.com>
Message-ID: <20160204101516.GJ3793@merlinux.eu>

On Thu, Feb 04, 2016 at 08:56 +1100, Brianna Laugher wrote:
> I think a dedicated page on the pytest site is a good idea (as well as a
> banner), then when it is over we can put the supporters names there (if
> they wish).
> 
> 55 days is a long time, maybe a 30 day campaign is better?

I went for fourty.  I wanted to give medium/large companies some time because
they usually can not allocate money very quickly.

> I would suggest to include even more context about what pytest is, maybe
> some numbers like pypi downloads, founded in 200x.

Could you add that where you see fit?

holger


> 
> Cheers
> Brianna
> On 04/02/2016 3:23 AM, "holger krekel" <holger at merlinux.eu> wrote:
> 
> > Hey all,
> >
> > i adapted the indiegogo draft page below according to suggestions here.
> > I didn't include yet Brianna's idea on allowing "voting", see my comment
> > to her mail.
> >
> > Feel free to edit or comment here further.  I'd like to publish tomorrow
> > european evening and i think pytestorg/Brianna should tweet then and we
> > retweet or so.
> >
> > Also i think we should put a banner on all pytest.org pages, what do you
> > think?  Anything else?
> >
> > best,
> > holger
> >
> >
> > On Wed, Feb 03, 2016 at 10:00 +0000, holger krekel wrote:
> > > Hey all,
> > >
> > > i've done a indiegogo sprint page which is still in draft mode, see here:
> > >
> > >     https://www.indiegogo.com/project/preview/ee72990c#/
> > >
> > > I also invited Bruno, Brianna, Floris and Florian as editors.
> > > If other wants to help edit, or comment on the setup, please send
> > > a mail here.  I am particular unsure about the "perks" ...
> > >
> > > I'd like to get it online tomorrow or latest friday if possible.
> > >
> > > cheers,
> > > holger
> > >
> > > --
> > > about me:    http://holgerkrekel.net/about-me/
> > > contracting: http://merlinux.eu
> > > _______________________________________________
> > > pytest-dev mailing list
> > > pytest-dev at python.org
> > > https://mail.python.org/mailman/listinfo/pytest-dev
> > >
> >
> > --
> > about me:    http://holgerkrekel.net/about-me/
> > contracting: http://merlinux.eu
> > _______________________________________________
> > pytest-dev mailing list
> > pytest-dev at python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
> >

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From nicoddemus at gmail.com  Thu Feb  4 05:30:06 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 04 Feb 2016 10:30:06 +0000
Subject: [pytest-dev] RFC: pytest sprint indiegogo page (draft)
In-Reply-To: <20160204101411.GI3793@merlinux.eu>
References: <20160203100027.GT3793@merlinux.eu> <20160203102047.GL542@tonks>
 <CA+RQFffJS6jtpwjJhck8fx6k4z+FWt4AW_L1PPY0FyE5chm6Zg@mail.gmail.com>
 <20160204101411.GI3793@merlinux.eu>
Message-ID: <CA+RQFfeXbX5LE6aQtsRRcNsWBUwdg7FdjzCJ3_x=2sY3XgFUZA@mail.gmail.com>

On Thu, Feb 4, 2016 at 8:14 AM holger krekel <holger at merlinux.eu> wrote:

>
> Totally agree.  I configured it as flexible funding almost from the
> beginning.
> If you look at the campaign as an editor can you see that?
> What makes you and others believe it is fixed funding?
>

Oh I was looking only at the preview page, if I access it in edit mode I
see that flexible is selected, sorry about that.

As a "preview", I think it should really display how the page will look
like once published. :P

Bruno.


>
> holger
>
>
>
> > Cheers,
> > Bruno.
> >
> >
> > On Wed, Feb 3, 2016 at 8:20 AM Florian Bruhin <me at the-compiler.org>
> wrote:
> >
> > > Hey Holger,
> > >
> > > * holger krekel <holger at merlinux.eu> [2016-02-03 10:00:27 +0000]:
> > > > Hey all,
> > > >
> > > > i've done a indiegogo sprint page which is still in draft mode, see
> here:
> > > >
> > > >     https://www.indiegogo.com/project/preview/ee72990c#/
> > >
> > > Yay, thank you! \o/
> > >
> > >     Floris Bruhin, Switzerland
> > >     Florian Bruynooghe, UK
> > >
> > > *cough* *cough* ;)
> > >
> > > If you're busy I can fix it myself later, still haven't figured out
> > > that "sync password manager database between multiple machines" thing
> > > reliably.
> > >
> > > Is this "flexible funding"? It seems to me like it isn't, i.e. if we
> > > don't get the 8kEUR, we'll get no money at all? Might make more sense
> > > to get the money even if we reach, say, 5kEUR, and then see what we
> > > can do to make it happen with that?
> > >
> > > > I am particular unsure about the "perks" ...
> > >
> > > Stickers sound good. Maybe T-Shirts as well, for something between
> > > EUR 50 and EUR 500? If I wasn't involved in pytest but liking it a
> > > lot, I'd be willing to spend EUR 100 or so, but I'd like something
> > > more than 10 stickers in return ;)
> > >
> > > OTOH it's some work and logistic overhead someone would need to
> > > tackle.
> > >
> > > "fix an issue" sounds a bit problematic. I'd rather not give the
> > > blanket promise of fixing a particular thing or introducing a feature,
> > > this has the potential to "force" us to do things nobody considers a
> > > good idea, if things go bad. Maybe more something like "vote on a
> > > specific bug/feature we'll consider a priority"?
> > >
> > > What about some document about the sprint where funders will be
> > > listed, with higher perks with (company) logo/URL? That's something
> > > I've seen a lot with other campaigns and seems reasonable to me.
> > >
> > > What do you think about perks for pytest trainings? Maybe that'd be a
> > > good incentive for companies - fund the sprint *and* get a training
> > > for pytest (or pytest/tox/devpi - not including travel/stay for the
> > > training of course).
> > >
> > > Florian
> > >
> > > --
> > > http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
> > >    GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
> > >          I love long mails! | http://email.is-not-s.ms/
> > > _______________________________________________
> > > 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
>
>
> --
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160204/24d8fab5/attachment.html>

From me at the-compiler.org  Thu Feb  4 05:33:05 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Thu, 4 Feb 2016 11:33:05 +0100
Subject: [pytest-dev] RFC: pytest sprint indiegogo page (draft)
In-Reply-To: <20160204101411.GI3793@merlinux.eu>
References: <20160203100027.GT3793@merlinux.eu> <20160203102047.GL542@tonks>
 <CA+RQFffJS6jtpwjJhck8fx6k4z+FWt4AW_L1PPY0FyE5chm6Zg@mail.gmail.com>
 <20160204101411.GI3793@merlinux.eu>
Message-ID: <20160204103305.GQ542@tonks>

* holger krekel <holger at merlinux.eu> [2016-02-04 10:14:11 +0000]:
> On Thu, Feb 04, 2016 at 00:26 +0000, Bruno Oliveira wrote:
> > Hi all,
> > 
> > Sorry for chipping in so late, I didn't have a chance of looking more
> > carefully at the draft until now.
> > 
> > I think it looks great so far, and I like most of the suggestions given by
> > others. I would like to stress on the part about it being flexible funding
> > though, as I think this sprint should happen even if not all the funding we
> > ask for is reached, even if that means some people can't attend the sprint
> > (myself included of course). After all, better to have a sprint with most
> > developers present than not having a sprint at all. :)
> 
> Totally agree.  I configured it as flexible funding almost from the beginning.  
> If you look at the campaign as an editor can you see that?
> What makes you and others believe it is fixed funding?

If you e.g. look at this project:
https://www.indiegogo.com/projects/cinestill-120-medium-format-film#/

You'll see a "Flexible funding" text under the goal. That isn't there
in the preview. Maybe it's just because it's still a draft, but it's
definitely strange.

When editing it however, I see "flexible funding" indeed.

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160204/bcb95d9d/attachment-0001.sig>

From me at the-compiler.org  Thu Feb  4 05:46:41 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Thu, 4 Feb 2016 11:46:41 +0100
Subject: [pytest-dev] RFC: pytest sprint indiegogo page (draft)
In-Reply-To: <20160204101516.GJ3793@merlinux.eu>
References: <20160203100027.GT3793@merlinux.eu>
 <20160203162330.GE3793@merlinux.eu>
 <CAPjwCju9dM-Vi_miAP3AhfahC3gUgZMaarKdQjjsinTTxbKq_w@mail.gmail.com>
 <20160204101516.GJ3793@merlinux.eu>
Message-ID: <20160204104641.GR542@tonks>

* holger krekel <holger at merlinux.eu> [2016-02-04 10:15:16 +0000]:
> On Thu, Feb 04, 2016 at 08:56 +1100, Brianna Laugher wrote:
> > I think a dedicated page on the pytest site is a good idea (as well as a
> > banner), then when it is over we can put the supporters names there (if
> > they wish).
> > 
> > 55 days is a long time, maybe a 30 day campaign is better?
> 
> I went for fourty.  I wanted to give medium/large companies some time because
> they usually can not allocate money very quickly.
> 
> > I would suggest to include even more context about what pytest is, maybe
> > some numbers like pypi downloads, founded in 200x.
> 
> Could you add that where you see fit?

It's quite hard to find more about the history of pytest - when was it
actually founded?

The first thing I found are some commits in the pytest-commit ML
archive from 2004:

https://mail.python.org/pipermail/pytest-commit/2004-October/000003.html

It seems like most of the concepts were already there though - so is
there some earlier history (perhaps as part of PyPy) I haven't found
out about yet?

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160204/11e77120/attachment.sig>

From holger at merlinux.eu  Thu Feb  4 05:56:41 2016
From: holger at merlinux.eu (holger krekel)
Date: Thu, 4 Feb 2016 10:56:41 +0000
Subject: [pytest-dev] pytest assertions / podcast / javascript
Message-ID: <20160204105641.GM3793@merlinux.eu>


Brian Okken did a postcast on pytest assertions, see
http://pythontesting.net/

And i recently encountered a Javascript-project "power-assert" which
takes up the "no API is the best API" slogan that came with pytest back
in 2005 or so:

https://github.com/power-assert-js/power-assert

FWIW i once had an accepted Pycon talk about "no API is the best API"
but then couldn't make the conference.  Some day i'd like to give a talk
about the topic :)

holger

From holger at merlinux.eu  Thu Feb  4 10:52:36 2016
From: holger at merlinux.eu (holger krekel)
Date: Thu, 4 Feb 2016 15:52:36 +0000
Subject: [pytest-dev] RFC: pytest sprint indiegogo page (draft)
In-Reply-To: <20160204104641.GR542@tonks>
References: <20160203100027.GT3793@merlinux.eu>
 <20160203162330.GE3793@merlinux.eu>
 <CAPjwCju9dM-Vi_miAP3AhfahC3gUgZMaarKdQjjsinTTxbKq_w@mail.gmail.com>
 <20160204101516.GJ3793@merlinux.eu> <20160204104641.GR542@tonks>
Message-ID: <20160204155236.GU3793@merlinux.eu>

On Thu, Feb 04, 2016 at 11:46 +0100, Florian Bruhin wrote:
> * holger krekel <holger at merlinux.eu> [2016-02-04 10:15:16 +0000]:
> > On Thu, Feb 04, 2016 at 08:56 +1100, Brianna Laugher wrote:
> > > I think a dedicated page on the pytest site is a good idea (as well as a
> > > banner), then when it is over we can put the supporters names there (if
> > > they wish).
> > > 
> > > 55 days is a long time, maybe a 30 day campaign is better?
> > 
> > I went for fourty.  I wanted to give medium/large companies some time because
> > they usually can not allocate money very quickly.
> > 
> > > I would suggest to include even more context about what pytest is, maybe
> > > some numbers like pypi downloads, founded in 200x.
> > 
> > Could you add that where you see fit?
> 
> It's quite hard to find more about the history of pytest - when was it
> actually founded?
> 
> The first thing I found are some commits in the pytest-commit ML
> archive from 2004:
> 
> https://mail.python.org/pipermail/pytest-commit/2004-October/000003.html
> 
> It seems like most of the concepts were already there though - so is
> there some earlier history (perhaps as part of PyPy) I haven't found
> out about yet?

Not sure myself :)

But I updated the story page for the campaign to include a bit of history.

I now also mention tox a bit more: I added two tox-specific perks to see if
there are people who would like to influence me/others to work a bit more
on tox.  One thing it'd like to do is exposing tox's API in such a way
that you can use it to write functional tests which require more complex
setup.  For example, having a devpi-server-2.3 export some data and a
devpi-server-3.0 import it -- this requires two virtualenvs and it would
be good to reuse tox's mechanics to manage them, start services etc.
I also think that we are reaching out to a broader circle of people
and many tox improvements are relatively easy to tackle.

could someone review the update? does this make sense to you?

I also sent a mail to indiegogo support to inquire if we can rely
on the "flexible funding" setting even though the "draft campaign"
doesn't show it.

holger


> Florian
> 
> -- 
> http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
>    GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
>          I love long mails! | http://email.is-not-s.ms/



-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From omarkohl at gmail.com  Fri Feb  5 02:48:48 2016
From: omarkohl at gmail.com (Omar Kohl)
Date: Fri, 5 Feb 2016 08:48:48 +0100
Subject: [pytest-dev] RFC: pytest sprint indiegogo page (draft)
In-Reply-To: <20160204155236.GU3793@merlinux.eu>
References: <20160203100027.GT3793@merlinux.eu>
 <20160203162330.GE3793@merlinux.eu>
 <CAPjwCju9dM-Vi_miAP3AhfahC3gUgZMaarKdQjjsinTTxbKq_w@mail.gmail.com>
 <20160204101516.GJ3793@merlinux.eu> <20160204104641.GR542@tonks>
 <20160204155236.GU3793@merlinux.eu>
Message-ID: <CAOmG0uVh0nBYp3iBDqqYgCcAyDnY0HrO+eBM+Y3um7TZth-oyg@mail.gmail.com>

Hi all,

looks great! As has been suggested before including the download numbers
and maybe also a list of projects/companies that are using pytest? Also
maybe someone has some good quotes by "Python gurus" praising pytest.

The company where I work has agreed to make a contribution, so as soon as
the page is ready I'll forward it.

Is there anything I can help with? I'm not a great pytest expert but I do
use it A LOT for testing, I wrote a small plugin (pytest-datafiles) and I
will brush up on the code and internals until June :-)

Kind regards,
Omar
Am 04.02.2016 16:52 schrieb "holger krekel" <holger at merlinux.eu>:

> On Thu, Feb 04, 2016 at 11:46 +0100, Florian Bruhin wrote:
> > * holger krekel <holger at merlinux.eu> [2016-02-04 10:15:16 +0000]:
> > > On Thu, Feb 04, 2016 at 08:56 +1100, Brianna Laugher wrote:
> > > > I think a dedicated page on the pytest site is a good idea (as well
> as a
> > > > banner), then when it is over we can put the supporters names there
> (if
> > > > they wish).
> > > >
> > > > 55 days is a long time, maybe a 30 day campaign is better?
> > >
> > > I went for fourty.  I wanted to give medium/large companies some time
> because
> > > they usually can not allocate money very quickly.
> > >
> > > > I would suggest to include even more context about what pytest is,
> maybe
> > > > some numbers like pypi downloads, founded in 200x.
> > >
> > > Could you add that where you see fit?
> >
> > It's quite hard to find more about the history of pytest - when was it
> > actually founded?
> >
> > The first thing I found are some commits in the pytest-commit ML
> > archive from 2004:
> >
> > https://mail.python.org/pipermail/pytest-commit/2004-October/000003.html
> >
> > It seems like most of the concepts were already there though - so is
> > there some earlier history (perhaps as part of PyPy) I haven't found
> > out about yet?
>
> Not sure myself :)
>
> But I updated the story page for the campaign to include a bit of history.
>
> I now also mention tox a bit more: I added two tox-specific perks to see if
> there are people who would like to influence me/others to work a bit more
> on tox.  One thing it'd like to do is exposing tox's API in such a way
> that you can use it to write functional tests which require more complex
> setup.  For example, having a devpi-server-2.3 export some data and a
> devpi-server-3.0 import it -- this requires two virtualenvs and it would
> be good to reuse tox's mechanics to manage them, start services etc.
> I also think that we are reaching out to a broader circle of people
> and many tox improvements are relatively easy to tackle.
>
> could someone review the update? does this make sense to you?
>
> I also sent a mail to indiegogo support to inquire if we can rely
> on the "flexible funding" setting even though the "draft campaign"
> doesn't show it.
>
> holger
>
>
> > Florian
> >
> > --
> > http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
> >    GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
> >          I love long mails! | http://email.is-not-s.ms/
>
>
>
> --
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160205/08a57f2a/attachment.html>

From holger at merlinux.eu  Fri Feb  5 08:08:18 2016
From: holger at merlinux.eu (holger krekel)
Date: Fri, 5 Feb 2016 13:08:18 +0000
Subject: [pytest-dev] python testing sprint June 2016 (pytest/tox) / funding
 needed
Message-ID: <20160205130818.GH15751@merlinux.eu>

Hello all,

we are heading for a one-week python testing sprint focusing on
improving the open source pytest and tox tools in June 20th-26th 2016 in
Freiburg, Germany. We have around 10 core maintainers from all across
the globe who want to participate.  We just started an indiegogo
campaign to get the neccessary funding for travel/accomodation and hope
you or your organisation help to make it happen and/or even participate
yourself.

See here for more details on the sprint: 

    http://pytest.org/latest/announce/sprint2016.html

and here for donating to make it happen:

    http://igg.me/at/pytest-sprint/x/4034848

thanks!
holger

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From patrickdepinguin at gmail.com  Sat Feb  6 04:09:50 2016
From: patrickdepinguin at gmail.com (Thomas De Schampheleire)
Date: Sat, 6 Feb 2016 10:09:50 +0100
Subject: [pytest-dev] pytest-sugar: tests skipped with pytest.mark.skipif
 not shown as such
Message-ID: <CAAXf6LVyERQZviFeqnLjwvTr8j7p6yWDotQ4ZZGEaxwjm0HaSA@mail.gmail.com>

Hi,

(I asked this question on IRC but had to leave before I got an answer)

I have been recommended to use pytest-sugar and so far have liked it a lot.
However, I now noticed a problem in reporting of skipped tests.

If I use pytest.mark.skipif for a test, the test is not shown as
'skipped' with pytest-sugar, while regular pytest does.
If I use nose.plugins.skip.SkipTest from a test instead, pytest-sugar
_does_ see it as skipped.

Am I incorrect in expecting to see tests that are skipped with skipif
to be marked as 'skipped' in pytest-sugar?

Example code is the following:

import pytest
import nose

def test_foo():
    assert True

@pytest.mark.skipif(True, reason='testing skipping')
def test_skipped():
    assert False

def test_nose_skipped():
    raise nose.plugins.skip.SkipTest('nose skipping')
    assert False



I tried to add some debug statements in pytest_sugar.py, and noticed
that for the skipif test there is a 'setup' trigger where
report.status says 'skipped' but it becomes 'passed' in the 'teardown'
trigger. There is no 'call' trigger for that skipped test.
I have not been able to determine any useful things further.

Please let me know if this is expected behavior, and what I should do
to display skipped tests.

Thanks,
Thomas

From nicoddemus at gmail.com  Sat Feb  6 09:07:03 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Sat, 06 Feb 2016 14:07:03 +0000
Subject: [pytest-dev] pytest-sugar: tests skipped with
 pytest.mark.skipif not shown as such
In-Reply-To: <CAAXf6LVyERQZviFeqnLjwvTr8j7p6yWDotQ4ZZGEaxwjm0HaSA@mail.gmail.com>
References: <CAAXf6LVyERQZviFeqnLjwvTr8j7p6yWDotQ4ZZGEaxwjm0HaSA@mail.gmail.com>
Message-ID: <CA+RQFfdsnZYNi1wQvL=iG=nb0i3DsiMhL4w0LiDpy5fng92X5w@mail.gmail.com>

Hi Thomas,

It seems to be a bug in pytest-sugar. Could you please create a new issue
in their issue tracker[1]?

[1] https://github.com/Frozenball/pytest-sugar/issues

Cheers,
Bruno.

On Sat, Feb 6, 2016 at 7:10 AM Thomas De Schampheleire <
patrickdepinguin at gmail.com> wrote:

> Hi,
>
> (I asked this question on IRC but had to leave before I got an answer)
>
> I have been recommended to use pytest-sugar and so far have liked it a lot.
> However, I now noticed a problem in reporting of skipped tests.
>
> If I use pytest.mark.skipif for a test, the test is not shown as
> 'skipped' with pytest-sugar, while regular pytest does.
> If I use nose.plugins.skip.SkipTest from a test instead, pytest-sugar
> _does_ see it as skipped.
>
> Am I incorrect in expecting to see tests that are skipped with skipif
> to be marked as 'skipped' in pytest-sugar?
>
> Example code is the following:
>
> import pytest
> import nose
>
> def test_foo():
>     assert True
>
> @pytest.mark.skipif(True, reason='testing skipping')
> def test_skipped():
>     assert False
>
> def test_nose_skipped():
>     raise nose.plugins.skip.SkipTest('nose skipping')
>     assert False
>
>
>
> I tried to add some debug statements in pytest_sugar.py, and noticed
> that for the skipif test there is a 'setup' trigger where
> report.status says 'skipped' but it becomes 'passed' in the 'teardown'
> trigger. There is no 'call' trigger for that skipped test.
> I have not been able to determine any useful things further.
>
> Please let me know if this is expected behavior, and what I should do
> to display skipped tests.
>
> Thanks,
> Thomas
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160206/eba22823/attachment.html>

From patrickdepinguin at gmail.com  Sat Feb  6 10:05:44 2016
From: patrickdepinguin at gmail.com (Thomas De Schampheleire)
Date: Sat, 6 Feb 2016 16:05:44 +0100
Subject: [pytest-dev] pytest-sugar: tests skipped with
 pytest.mark.skipif not shown as such
In-Reply-To: <CA+RQFfdsnZYNi1wQvL=iG=nb0i3DsiMhL4w0LiDpy5fng92X5w@mail.gmail.com>
References: <CAAXf6LVyERQZviFeqnLjwvTr8j7p6yWDotQ4ZZGEaxwjm0HaSA@mail.gmail.com>
 <CA+RQFfdsnZYNi1wQvL=iG=nb0i3DsiMhL4w0LiDpy5fng92X5w@mail.gmail.com>
Message-ID: <CAAXf6LUN92v53vvQ+FoUik4yQeWhdkhgZ1BeKcZc8L3G1LzTeg@mail.gmail.com>

On Sat, Feb 6, 2016 at 3:07 PM, Bruno Oliveira <nicoddemus at gmail.com> wrote:
> Hi Thomas,
>
> It seems to be a bug in pytest-sugar. Could you please create a new issue in
> their issue tracker[1]?
>
> [1] https://github.com/Frozenball/pytest-sugar/issues
>

Thanks, done: https://github.com/Frozenball/pytest-sugar/issues/75

From goncalo.magno at gmail.com  Sat Feb  6 22:53:39 2016
From: goncalo.magno at gmail.com (Goncalo Morgado)
Date: Sun, 7 Feb 2016 03:53:39 +0000
Subject: [pytest-dev] Fixtures and test cases parametrization -- the clever
 way
Message-ID: <CAPNH_L-KAAHeE4sLPmkdtZoC-oK2yJ212x8nXRPWcrNDQh_ZQw@mail.gmail.com>

Hi,

Thank you for this great lib!

I have an app that takes a config file with key/value pairs, that I would
like to test thoroughly, i.e all possible combinations of parameters in the
config file. I thought about taking advantage of the fixture
parametrization functionality pytest provides, but not sure how... and end
up with what I believe is a silly idea (please see example code below). I
say silly because I will end up with a huge amount of *.mark.parametrize()*
entries and the test case function with a number of arguments... Any idea
on how to do this an elegant way?

*import* pytest
@pytest.mark.parametrize("key1", [0, 1, etc, etc])
@pytest.mark.parametrize("key2", [2, 3, etc, etc, etc])
@pytest.mark.parametrize("key3", [4, 5, etc, etc, etc, etc])
... # an infinitiy amount of @pytest.mark.parametrize("keyN", [bla, bla,
bla])
*def* test_app_param_combination(key1, key2, key3, ....)
    # implementation of the test
    # run app with combination of key/value pair and check exit code
    *assert* app_exit_code == 0

Many thanks
Go
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160207/69e70b52/attachment.html>

From holger at merlinux.eu  Sun Feb  7 03:42:38 2016
From: holger at merlinux.eu (Holger Krekel)
Date: Sun, 07 Feb 2016 09:42:38 +0100
Subject: [pytest-dev] Fixtures and test cases parametrization -- the
 clever way
In-Reply-To: <CAPNH_L-KAAHeE4sLPmkdtZoC-oK2yJ212x8nXRPWcrNDQh_ZQw@mail.gmail.com>
References: <CAPNH_L-KAAHeE4sLPmkdtZoC-oK2yJ212x8nXRPWcrNDQh_ZQw@mail.gmail.com>
Message-ID: <AAB3D3FA-FE87-46DC-B36D-C5DD31E43D77@merlinux.eu>

Hi Gonzalo, 

Probably the pytest_generate_tests hook helps, see http://pytest.org/latest/example/parametrize.html#generating-parameters-combinations-depending-on-command-line

Cheers holger

On February 7, 2016 4:53:39 AM GMT+01:00, Goncalo Morgado <goncalo.magno at gmail.com> wrote:
>Hi,
>
>Thank you for this great lib!
>
>I have an app that takes a config file with key/value pairs, that I
>would
>like to test thoroughly, i.e all possible combinations of parameters in
>the
>config file. I thought about taking advantage of the fixture
>parametrization functionality pytest provides, but not sure how... and
>end
>up with what I believe is a silly idea (please see example code below).
>I
>say silly because I will end up with a huge amount of
>*.mark.parametrize()*
>entries and the test case function with a number of arguments... Any
>idea
>on how to do this an elegant way?
>
>*import* pytest
>@pytest.mark.parametrize("key1", [0, 1, etc, etc])
>@pytest.mark.parametrize("key2", [2, 3, etc, etc, etc])
>@pytest.mark.parametrize("key3", [4, 5, etc, etc, etc, etc])
>... # an infinitiy amount of @pytest.mark.parametrize("keyN", [bla,
>bla,
>bla])
>*def* test_app_param_combination(key1, key2, key3, ....)
>    # implementation of the test
>    # run app with combination of key/value pair and check exit code
>    *assert* app_exit_code == 0
>
>Many thanks
>Go
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>pytest-dev mailing list
>pytest-dev at python.org
>https://mail.python.org/mailman/listinfo/pytest-dev

-- 
Sent using mobile touch keys, increased chances for errors and misunderstandings. Enjoy! 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160207/6fd16240/attachment.html>

From florian.schulze at gmx.net  Sun Feb  7 03:53:55 2016
From: florian.schulze at gmx.net (Florian Schulze)
Date: Sun, 07 Feb 2016 09:53:55 +0100
Subject: [pytest-dev] Fixtures and test cases parametrization -- the
 clever way
In-Reply-To: <CAPNH_L-KAAHeE4sLPmkdtZoC-oK2yJ212x8nXRPWcrNDQh_ZQw@mail.gmail.com>
References: <CAPNH_L-KAAHeE4sLPmkdtZoC-oK2yJ212x8nXRPWcrNDQh_ZQw@mail.gmail.com>
Message-ID: <F49FBCC4-FAFA-4CB3-AC35-092639522F9A@gmx.net>

Maybe https://pypi.python.org/pypi/hypothesis is a better fit for this 
than parametrization. At first it might seem a bit foreign (it felt so 
to me), but it allows you to test in very interesting ways and to find 
corner cases quickly. Just testing all the keys is pretty boring and 
most likely won't lead to errors, so it's pretty much a waste of your 
time and CPU time.

Regards,
Florian Schulze


On 7 Feb 2016, at 4:53, Goncalo Morgado wrote:

> Hi,
>
> Thank you for this great lib!
>
> I have an app that takes a config file with key/value pairs, that I 
> would
> like to test thoroughly, i.e all possible combinations of parameters 
> in the
> config file. I thought about taking advantage of the fixture
> parametrization functionality pytest provides, but not sure how... and 
> end
> up with what I believe is a silly idea (please see example code 
> below). I
> say silly because I will end up with a huge amount of 
> *.mark.parametrize()*
> entries and the test case function with a number of arguments... Any 
> idea
> on how to do this an elegant way?
>
> *import* pytest
> @pytest.mark.parametrize("key1", [0, 1, etc, etc])
> @pytest.mark.parametrize("key2", [2, 3, etc, etc, etc])
> @pytest.mark.parametrize("key3", [4, 5, etc, etc, etc, etc])
> ... # an infinitiy amount of @pytest.mark.parametrize("keyN", [bla, 
> bla,
> bla])
> *def* test_app_param_combination(key1, key2, key3, ....)
>   # implementation of the test
>   # run app with combination of key/value pair and check exit code
>   *assert* app_exit_code == 0
>
> Many thanks
> Go
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev

From goncalo.magno at gmail.com  Sun Feb  7 19:29:13 2016
From: goncalo.magno at gmail.com (Goncalo Morgado)
Date: Mon, 8 Feb 2016 00:29:13 +0000
Subject: [pytest-dev] Fixtures and test cases parametrization -- the
 clever way
In-Reply-To: <F49FBCC4-FAFA-4CB3-AC35-092639522F9A@gmx.net>
References: <CAPNH_L-KAAHeE4sLPmkdtZoC-oK2yJ212x8nXRPWcrNDQh_ZQw@mail.gmail.com>
 <F49FBCC4-FAFA-4CB3-AC35-092639522F9A@gmx.net>
Message-ID: <CAPNH_L_v-N3uCLSZdP1++ET7Nresdz++SzQCDqj=ZQ-S3qSXXg@mail.gmail.com>

Hi Florian,

Thanks for the reply.
Very useful! I am reconsidering the amount of tests I was trying to
parametrize in a single test case, and split it in multiple test_*
functions for different groups of tests. Also creating a fixture for
default parameters, those that are not parametrized get set by this fixture.

Regards
Goncalo




On Sun, Feb 7, 2016 at 8:53 AM, Florian Schulze <florian.schulze at gmx.net>
wrote:

> Maybe https://pypi.python.org/pypi/hypothesis is a better fit for this
> than parametrization. At first it might seem a bit foreign (it felt so to
> me), but it allows you to test in very interesting ways and to find corner
> cases quickly. Just testing all the keys is pretty boring and most likely
> won't lead to errors, so it's pretty much a waste of your time and CPU time.
>
> Regards,
> Florian Schulze
>
>
> On 7 Feb 2016, at 4:53, Goncalo Morgado wrote:
>
> Hi,
>>
>> Thank you for this great lib!
>>
>> I have an app that takes a config file with key/value pairs, that I would
>> like to test thoroughly, i.e all possible combinations of parameters in
>> the
>> config file. I thought about taking advantage of the fixture
>> parametrization functionality pytest provides, but not sure how... and end
>> up with what I believe is a silly idea (please see example code below). I
>> say silly because I will end up with a huge amount of
>> *.mark.parametrize()*
>> entries and the test case function with a number of arguments... Any idea
>> on how to do this an elegant way?
>>
>> *import* pytest
>> @pytest.mark.parametrize("key1", [0, 1, etc, etc])
>> @pytest.mark.parametrize("key2", [2, 3, etc, etc, etc])
>> @pytest.mark.parametrize("key3", [4, 5, etc, etc, etc, etc])
>> ... # an infinitiy amount of @pytest.mark.parametrize("keyN", [bla, bla,
>> bla])
>> *def* test_app_param_combination(key1, key2, key3, ....)
>>   # implementation of the test
>>   # run app with combination of key/value pair and check exit code
>>   *assert* app_exit_code == 0
>>
>> Many thanks
>> Go
>> _______________________________________________
>> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160208/5e53bd0b/attachment.html>

From holger at merlinux.eu  Mon Feb  8 14:03:59 2016
From: holger at merlinux.eu (Holger Krekel)
Date: Mon, 08 Feb 2016 20:03:59 +0100
Subject: [pytest-dev] Sprint participants writing a blog post?
Message-ID: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>

What about if each of us who wants to participate writes a small blog (lacking a blog a pytest-dev) post of where he/she comes from, past core or plugin work for example, and main areas of interest for the sprint? 

We could publish them via updates every few days. Any takers? 
-- 
Sent using mobile touch keys, increased chances for errors and misunderstandings. Enjoy! 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160208/b13c7700/attachment.html>

From brianna.laugher at gmail.com  Mon Feb  8 15:05:24 2016
From: brianna.laugher at gmail.com (Brianna Laugher)
Date: Tue, 9 Feb 2016 07:05:24 +1100
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>
References: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>
Message-ID: <CAPjwCjsH-ooSzQ4pTQKhq=14vAG9pasJmQurzbqWcGcX4cs8yQ@mail.gmail.com>

Heh, I had the exact same idea last night :)

I was thinking
1) how did you get involved with pytest?
2) What is your favourite feature/plugin of pytest that is relatively
unknown?
3) What are you planning to work on during the sprint?

Cheers
Brianna
On 09/02/2016 6:04 AM, "Holger Krekel" <holger at merlinux.eu> wrote:

> What about if each of us who wants to participate writes a small blog
> (lacking a blog a pytest-dev) post of where he/she comes from, past core or
> plugin work for example, and main areas of interest for the sprint?
>
> We could publish them via updates every few days. Any takers?
> --
> Sent using mobile touch keys, increased chances for errors and
> misunderstandings. Enjoy!
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160209/859ec0d0/attachment.html>

From dhunt at mozilla.com  Tue Feb  9 05:40:22 2016
From: dhunt at mozilla.com (Dave Hunt)
Date: Tue, 9 Feb 2016 10:40:22 +0000
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <CAPjwCjsH-ooSzQ4pTQKhq=14vAG9pasJmQurzbqWcGcX4cs8yQ@mail.gmail.com>
References: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>
 <CAPjwCjsH-ooSzQ4pTQKhq=14vAG9pasJmQurzbqWcGcX4cs8yQ@mail.gmail.com>
Message-ID: <DFF0964C-990E-41C2-90E0-51F1C21223CD@mozilla.com>

I think this is a great idea! I have had approval to join you all during the sprint, so I?d be happy to write a blog post about how I came to pytest and what I?d like to work on during the week.

Cheers,
Dave

> On 8 Feb 2016, at 20:05, Brianna Laugher <brianna.laugher at gmail.com> wrote:
> 
> Heh, I had the exact same idea last night :)
> 
> I was thinking
> 1) how did you get involved with pytest?
> 2) What is your favourite feature/plugin of pytest that is relatively unknown?
> 3) What are you planning to work on during the sprint?
> 
> Cheers
> Brianna
> 
> On 09/02/2016 6:04 AM, "Holger Krekel" <holger at merlinux.eu <mailto:holger at merlinux.eu>> wrote:
> What about if each of us who wants to participate writes a small blog (lacking a blog a pytest-dev) post of where he/she comes from, past core or plugin work for example, and main areas of interest for the sprint? 
> 
> We could publish them via updates every few days. Any takers? 
> -- 
> Sent using mobile touch keys, increased chances for errors and misunderstandings. Enjoy! 
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org <mailto:pytest-dev at python.org>
> https://mail.python.org/mailman/listinfo/pytest-dev <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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160209/0992bf49/attachment.html>

From dhunt at mozilla.com  Tue Feb  9 05:43:38 2016
From: dhunt at mozilla.com (Dave Hunt)
Date: Tue, 9 Feb 2016 10:43:38 +0000
Subject: [pytest-dev] pytest sprint 2016 / getting started
In-Reply-To: <20160107104028.GB3793@merlinux.eu>
References: <20160107104028.GB3793@merlinux.eu>
Message-ID: <0BDDFBA5-BA37-420A-B9E7-73278EBB3BE4@mozilla.com>

It looks like I?ll be joining you during the sprint! Is it reasonable to go ahead and book flights now, or should I wait for the campaign to reach a certain amount of funding? My costs will be covered my by company, so it?s not dependant on the campaign. For accommodation, are we all going to try to book the same hotel, or should I just go ahead and find something myself?

Cheers,
Dave

> On 7 Jan 2016, at 10:40, holger krekel <holger at merlinux.eu> wrote:
> 
> Hey all,
> 
> let's try to find out if we can make a pytest sprint happen in 2016.
> Here are some suggestions/thoughts on key points.
> 
> Participants: anyway who has contributed to pytest in recent years but also
> interested newcomers/wanna-be-contributors.  Contributors are eligible
> for getting their travel costs reimbursed (see funding below).
> 
> Location: somewhere around Freiburg, black forest, Germany.
> 
> Date ranges:
> 
>    20-26th June or
> 
>    30th June - 6th July.
> 
> Travel: arrive on the first day, leave the last.
> 
> Funding: we'll do a Indiegogo or betterplace.org campaign and ask
> companies and individuals to help come up with funding for travel
> costs, lodging and food for participants.  If participants can come
> on their company's time and money even better.  In fact, the gathering
> will be a great opportunity to dive deeper into pytest and make the best
> use of it for your company.
> 
> sprint contents: pytest-3.0 and a major new revision of the xdist plugin?
> Cleaning up wards, introducing new features (to be continued ...).
> 
> deadline for funding compaign: maybe February/March
> so everybody can start booking.
> 
> Who'd be up for it?  how much do you estimate you need for travel?
> Would the date range fit?
> 
> best,
> holger
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev


From andreas at pelme.se  Tue Feb  9 05:55:17 2016
From: andreas at pelme.se (Andreas Pelme)
Date: Tue, 9 Feb 2016 11:55:17 +0100
Subject: [pytest-dev] pytest sprint 2016 / getting started
In-Reply-To: <0BDDFBA5-BA37-420A-B9E7-73278EBB3BE4@mozilla.com>
References: <20160107104028.GB3793@merlinux.eu>
 <0BDDFBA5-BA37-420A-B9E7-73278EBB3BE4@mozilla.com>
Message-ID: <E4490FCE-9184-4B90-87B3-0BA385A416FE@pelme.se>

Good to hear Dave! :)

I was just going to ask about accommodation. I was thinking that I can book a reasonably large multi bedroom apartment that I can pay via my company. Others would then be welcome to share. Preferably people which the company does not already pay. :)

What are your thoughts about something like that?

Holger, do you know of local accommodation that you recommend or should I look into airbnb?

Cheers,
Andreas


> On 9 feb. 2016, at 11:43, Dave Hunt <dhunt at mozilla.com> wrote:
> 
> It looks like I?ll be joining you during the sprint! Is it reasonable to go ahead and book flights now, or should I wait for the campaign to reach a certain amount of funding? My costs will be covered my by company, so it?s not dependant on the campaign. For accommodation, are we all going to try to book the same hotel, or should I just go ahead and find something myself?
> 
> Cheers,
> Dave
> 
>> On 7 Jan 2016, at 10:40, holger krekel <holger at merlinux.eu> wrote:
>> 
>> Hey all,
>> 
>> let's try to find out if we can make a pytest sprint happen in 2016.
>> Here are some suggestions/thoughts on key points.
>> 
>> Participants: anyway who has contributed to pytest in recent years but also
>> interested newcomers/wanna-be-contributors.  Contributors are eligible
>> for getting their travel costs reimbursed (see funding below).
>> 
>> Location: somewhere around Freiburg, black forest, Germany.
>> 
>> Date ranges:
>> 
>>   20-26th June or
>> 
>>   30th June - 6th July.
>> 
>> Travel: arrive on the first day, leave the last.
>> 
>> Funding: we'll do a Indiegogo or betterplace.org campaign and ask
>> companies and individuals to help come up with funding for travel
>> costs, lodging and food for participants.  If participants can come
>> on their company's time and money even better.  In fact, the gathering
>> will be a great opportunity to dive deeper into pytest and make the best
>> use of it for your company.
>> 
>> sprint contents: pytest-3.0 and a major new revision of the xdist plugin?
>> Cleaning up wards, introducing new features (to be continued ...).
>> 
>> deadline for funding compaign: maybe February/March
>> so everybody can start booking.
>> 
>> Who'd be up for it?  how much do you estimate you need for travel?
>> Would the date range fit?
>> 
>> best,
>> holger
>> _______________________________________________
>> 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  Tue Feb  9 09:09:53 2016
From: holger at merlinux.eu (holger krekel)
Date: Tue, 9 Feb 2016 14:09:53 +0000
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <A926C829-CB10-429D-9782-C96256271D0A@mozilla.com>
References: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>
 <CAPjwCjsH-ooSzQ4pTQKhq=14vAG9pasJmQurzbqWcGcX4cs8yQ@mail.gmail.com>
 <DFF0964C-990E-41C2-90E0-51F1C21223CD@mozilla.com>
 <A926C829-CB10-429D-9782-C96256271D0A@mozilla.com>
Message-ID: <20160209140953.GH15751@merlinux.eu>

On Tue, Feb 09, 2016 at 14:07 +0000, Dave Hunt wrote:
> I have a public preview of my blog post. Feedback welcome:
> http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07 <http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07>
 
reads good!

holger

> Dave
> 
> > On 9 Feb 2016, at 10:40, Dave Hunt <dhunt at mozilla.com> wrote:
> > 
> > I think this is a great idea! I have had approval to join you all during the sprint, so I?d be happy to write a blog post about how I came to pytest and what I?d like to work on during the week.
> > 
> > Cheers,
> > Dave
> > 
> >> On 8 Feb 2016, at 20:05, Brianna Laugher <brianna.laugher at gmail.com <mailto:brianna.laugher at gmail.com>> wrote:
> >> 
> >> Heh, I had the exact same idea last night :)
> >> 
> >> I was thinking
> >> 1) how did you get involved with pytest?
> >> 2) What is your favourite feature/plugin of pytest that is relatively unknown?
> >> 3) What are you planning to work on during the sprint?
> >> 
> >> Cheers
> >> Brianna
> >> 
> >> On 09/02/2016 6:04 AM, "Holger Krekel" <holger at merlinux.eu <mailto:holger at merlinux.eu>> wrote:
> >> What about if each of us who wants to participate writes a small blog (lacking a blog a pytest-dev) post of where he/she comes from, past core or plugin work for example, and main areas of interest for the sprint? 
> >> 
> >> We could publish them via updates every few days. Any takers? 
> >> -- 
> >> Sent using mobile touch keys, increased chances for errors and misunderstandings. Enjoy! 
> >> _______________________________________________
> >> pytest-dev mailing list
> >> pytest-dev at python.org <mailto:pytest-dev at python.org>
> >> https://mail.python.org/mailman/listinfo/pytest-dev <https://mail.python.org/mailman/listinfo/pytest-dev>
> >> 
> >> _______________________________________________
> >> pytest-dev mailing list
> >> pytest-dev at python.org <mailto:pytest-dev at python.org>
> >> https://mail.python.org/mailman/listinfo/pytest-dev
> > 
> 

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From dhunt at mozilla.com  Tue Feb  9 09:07:12 2016
From: dhunt at mozilla.com (Dave Hunt)
Date: Tue, 9 Feb 2016 14:07:12 +0000
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <DFF0964C-990E-41C2-90E0-51F1C21223CD@mozilla.com>
References: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>
 <CAPjwCjsH-ooSzQ4pTQKhq=14vAG9pasJmQurzbqWcGcX4cs8yQ@mail.gmail.com>
 <DFF0964C-990E-41C2-90E0-51F1C21223CD@mozilla.com>
Message-ID: <A926C829-CB10-429D-9782-C96256271D0A@mozilla.com>

I have a public preview of my blog post. Feedback welcome:
http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07 <http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07>

Cheers,
Dave

> On 9 Feb 2016, at 10:40, Dave Hunt <dhunt at mozilla.com> wrote:
> 
> I think this is a great idea! I have had approval to join you all during the sprint, so I?d be happy to write a blog post about how I came to pytest and what I?d like to work on during the week.
> 
> Cheers,
> Dave
> 
>> On 8 Feb 2016, at 20:05, Brianna Laugher <brianna.laugher at gmail.com <mailto:brianna.laugher at gmail.com>> wrote:
>> 
>> Heh, I had the exact same idea last night :)
>> 
>> I was thinking
>> 1) how did you get involved with pytest?
>> 2) What is your favourite feature/plugin of pytest that is relatively unknown?
>> 3) What are you planning to work on during the sprint?
>> 
>> Cheers
>> Brianna
>> 
>> On 09/02/2016 6:04 AM, "Holger Krekel" <holger at merlinux.eu <mailto:holger at merlinux.eu>> wrote:
>> What about if each of us who wants to participate writes a small blog (lacking a blog a pytest-dev) post of where he/she comes from, past core or plugin work for example, and main areas of interest for the sprint? 
>> 
>> We could publish them via updates every few days. Any takers? 
>> -- 
>> Sent using mobile touch keys, increased chances for errors and misunderstandings. Enjoy! 
>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org <mailto:pytest-dev at python.org>
>> https://mail.python.org/mailman/listinfo/pytest-dev <https://mail.python.org/mailman/listinfo/pytest-dev>
>> 
>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org <mailto:pytest-dev at python.org>
>> https://mail.python.org/mailman/listinfo/pytest-dev
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160209/9de2e703/attachment.html>

From holger at merlinux.eu  Tue Feb  9 09:27:49 2016
From: holger at merlinux.eu (holger krekel)
Date: Tue, 9 Feb 2016 14:27:49 +0000
Subject: [pytest-dev] pytest sprint 2016 / getting started
In-Reply-To: <E4490FCE-9184-4B90-87B3-0BA385A416FE@pelme.se>
References: <20160107104028.GB3793@merlinux.eu>
 <0BDDFBA5-BA37-420A-B9E7-73278EBB3BE4@mozilla.com>
 <E4490FCE-9184-4B90-87B3-0BA385A416FE@pelme.se>
Message-ID: <20160209142749.GI15751@merlinux.eu>

On Tue, Feb 09, 2016 at 11:55 +0100, Andreas Pelme wrote:
> Good to hear Dave! :)
> 
> I was just going to ask about accommodation. I was thinking that I can book a reasonably large multi bedroom apartment that I can pay via my company. Others would then be welcome to share. Preferably people which the company does not already pay. :)
> 
> What are your thoughts about something like that?

sounds like a great idea!

> Holger, do you know of local accommodation that you recommend or should I look into airbnb?

I'd like to first try to get clear on where we are going to do the
sprint and then recommend accomodation around it.  This might last until
beginning march which i think is still perfectly fine.  Also 1-2 persons
can easily sleep in a guest room of my private flat, maybe i can arrange more.
We should reserve these for those whose company does not pay their accomodation.

I've started a page to record arrival/departure dates and travelcost
funding (if applicable):

    https://github.com/pytest-dev/pytest/wiki/sprint2016

If everyone could edit their current planning in that'd be helpful.

best,
holger


> Cheers,
> Andreas
> 
> 
> > On 9 feb. 2016, at 11:43, Dave Hunt <dhunt at mozilla.com> wrote:
> > 
> > It looks like I?ll be joining you during the sprint! Is it reasonable to go ahead and book flights now, or should I wait for the campaign to reach a certain amount of funding? My costs will be covered my by company, so it?s not dependant on the campaign. For accommodation, are we all going to try to book the same hotel, or should I just go ahead and find something myself?
> > 
> > Cheers,
> > Dave
> > 
> >> On 7 Jan 2016, at 10:40, holger krekel <holger at merlinux.eu> wrote:
> >> 
> >> Hey all,
> >> 
> >> let's try to find out if we can make a pytest sprint happen in 2016.
> >> Here are some suggestions/thoughts on key points.
> >> 
> >> Participants: anyway who has contributed to pytest in recent years but also
> >> interested newcomers/wanna-be-contributors.  Contributors are eligible
> >> for getting their travel costs reimbursed (see funding below).
> >> 
> >> Location: somewhere around Freiburg, black forest, Germany.
> >> 
> >> Date ranges:
> >> 
> >>   20-26th June or
> >> 
> >>   30th June - 6th July.
> >> 
> >> Travel: arrive on the first day, leave the last.
> >> 
> >> Funding: we'll do a Indiegogo or betterplace.org campaign and ask
> >> companies and individuals to help come up with funding for travel
> >> costs, lodging and food for participants.  If participants can come
> >> on their company's time and money even better.  In fact, the gathering
> >> will be a great opportunity to dive deeper into pytest and make the best
> >> use of it for your company.
> >> 
> >> sprint contents: pytest-3.0 and a major new revision of the xdist plugin?
> >> Cleaning up wards, introducing new features (to be continued ...).
> >> 
> >> deadline for funding compaign: maybe February/March
> >> so everybody can start booking.
> >> 
> >> Who'd be up for it?  how much do you estimate you need for travel?
> >> Would the date range fit?
> >> 
> >> best,
> >> holger
> >> _______________________________________________
> >> 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
> 

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From me at the-compiler.org  Tue Feb  9 09:41:42 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Tue, 9 Feb 2016 15:41:42 +0100
Subject: [pytest-dev] pytest sprint 2016 / getting started
In-Reply-To: <20160209142749.GI15751@merlinux.eu>
References: <20160107104028.GB3793@merlinux.eu>
 <0BDDFBA5-BA37-420A-B9E7-73278EBB3BE4@mozilla.com>
 <E4490FCE-9184-4B90-87B3-0BA385A416FE@pelme.se>
 <20160209142749.GI15751@merlinux.eu>
Message-ID: <20160209144142.GG10579@tonks>

* holger krekel <holger at merlinux.eu> [2016-02-09 14:27:49 +0000]:
> On Tue, Feb 09, 2016 at 11:55 +0100, Andreas Pelme wrote:
> > Good to hear Dave! :)
> > 
> > I was just going to ask about accommodation. I was thinking that I can book a reasonably large multi bedroom apartment that I can pay via my company. Others would then be welcome to share. Preferably people which the company does not already pay. :)
> > 
> > What are your thoughts about something like that?
> 
> sounds like a great idea!
> 
> > Holger, do you know of local accommodation that you recommend or should I look into airbnb?
> 
> I'd like to first try to get clear on where we are going to do the
> sprint and then recommend accomodation around it.  This might last until
> beginning march which i think is still perfectly fine.  Also 1-2 persons
> can easily sleep in a guest room of my private flat, maybe i can arrange more.
> We should reserve these for those whose company does not pay their accomodation.
> 
> I've started a page to record arrival/departure dates and travelcost
> funding (if applicable):
> 
>     https://github.com/pytest-dev/pytest/wiki/sprint2016
> 
> If everyone could edit their current planning in that'd be helpful.

We already have a wiki page:
https://github.com/pytest-dev/pytest/wiki/2016-dev-sprint

I think it'd make more sense to update that one?

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160209/ff975349/attachment-0001.sig>

From dhunt at mozilla.com  Tue Feb  9 12:16:41 2016
From: dhunt at mozilla.com (Dave Hunt)
Date: Tue, 9 Feb 2016 17:16:41 +0000
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <20160209140953.GH15751@merlinux.eu>
References: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>
 <CAPjwCjsH-ooSzQ4pTQKhq=14vAG9pasJmQurzbqWcGcX4cs8yQ@mail.gmail.com>
 <DFF0964C-990E-41C2-90E0-51F1C21223CD@mozilla.com>
 <A926C829-CB10-429D-9782-C96256271D0A@mozilla.com>
 <20160209140953.GH15751@merlinux.eu>
Message-ID: <6857A31A-FD3E-434C-8F40-189FBAC5D88C@mozilla.com>

Published:
http://blargon7.com/2016/02/python-testing-sprint-2016/ <http://blargon7.com/2016/02/python-testing-sprint-2016/>

Dave

> On 9 Feb 2016, at 14:09, holger krekel <holger at merlinux.eu> wrote:
> 
> On Tue, Feb 09, 2016 at 14:07 +0000, Dave Hunt wrote:
>> I have a public preview of my blog post. Feedback welcome:
>> http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07 <http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07>
> 
> reads good!
> 
> holger
> 
>> Dave
>> 
>>> On 9 Feb 2016, at 10:40, Dave Hunt <dhunt at mozilla.com> wrote:
>>> 
>>> I think this is a great idea! I have had approval to join you all during the sprint, so I?d be happy to write a blog post about how I came to pytest and what I?d like to work on during the week.
>>> 
>>> Cheers,
>>> Dave
>>> 
>>>> On 8 Feb 2016, at 20:05, Brianna Laugher <brianna.laugher at gmail.com <mailto:brianna.laugher at gmail.com>> wrote:
>>>> 
>>>> Heh, I had the exact same idea last night :)
>>>> 
>>>> I was thinking
>>>> 1) how did you get involved with pytest?
>>>> 2) What is your favourite feature/plugin of pytest that is relatively unknown?
>>>> 3) What are you planning to work on during the sprint?
>>>> 
>>>> Cheers
>>>> Brianna
>>>> 
>>>> On 09/02/2016 6:04 AM, "Holger Krekel" <holger at merlinux.eu <mailto:holger at merlinux.eu>> wrote:
>>>> What about if each of us who wants to participate writes a small blog (lacking a blog a pytest-dev) post of where he/she comes from, past core or plugin work for example, and main areas of interest for the sprint? 
>>>> 
>>>> We could publish them via updates every few days. Any takers? 
>>>> -- 
>>>> Sent using mobile touch keys, increased chances for errors and misunderstandings. Enjoy! 
>>>> _______________________________________________
>>>> pytest-dev mailing list
>>>> pytest-dev at python.org <mailto:pytest-dev at python.org>
>>>> https://mail.python.org/mailman/listinfo/pytest-dev <https://mail.python.org/mailman/listinfo/pytest-dev>
>>>> 
>>>> _______________________________________________
>>>> pytest-dev mailing list
>>>> pytest-dev at python.org <mailto:pytest-dev at python.org>
>>>> https://mail.python.org/mailman/listinfo/pytest-dev
>>> 
>> 
> 
> -- 
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160209/c84d2ef6/attachment.html>

From brianna.laugher at gmail.com  Wed Feb 10 07:19:39 2016
From: brianna.laugher at gmail.com (Brianna Laugher)
Date: Wed, 10 Feb 2016 23:19:39 +1100
Subject: [pytest-dev] Twitter update
Message-ID: <CAPjwCjub+o4EV_3TvtTgE4x4HptU7TVseUQwDUggVa+sJ=zDwQ@mail.gmail.com>

Hi,

I added Holger @hpk42 and Raphael @hackebrot to the pytestdotorg twitter
account so they can tweet from it (via tweetdeck.twitter.com). If anyone
else feels like they might be inspired to tweet on behalf of pytest, let me
know offlist.

cheers
Brianna


-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160210/36ac10ee/attachment.html>

From me at the-compiler.org  Wed Feb 10 07:59:42 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Wed, 10 Feb 2016 13:59:42 +0100
Subject: [pytest-dev] Google Summer Of Code
Message-ID: <20160210125942.GJ10579@tonks>

Hey,

I was asked by qutebrowser users if I want to participate as an
organization for Google's Summer Of Code - while I don't think it
makes sense for a "smaller" project like qutebrowser, I think it'd
make a lot of sense for pytest!

The idea of GSoC is that opensource projects apply for it, then
students apply to a given project, then contribute a significant
amount of work (being mentored by project members) and in exchange get
a stipend (~USD 5000) from Google.

Applications are open until Feburary 19th (Friday in a week...) - what
about trying with pytest?

What we'd need are two (or more) administrative organisators (I'd
volunteer) and mentors.

The PSF is also available as an umbrella organization:
https://wiki.python.org/moin/SummerOfCode/2016

What do you think?

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160210/c6c3363a/attachment.sig>

From tom at viner.tv  Wed Feb 10 15:04:16 2016
From: tom at viner.tv (Tom Viner)
Date: Wed, 10 Feb 2016 20:04:16 +0000
Subject: [pytest-dev] Google Summer Of Code
Message-ID: <CANBSuyGePu7qaik19KCZRU+L67vqxCKdwg625cDSiWDbV2Cx0A@mail.gmail.com>

Hi Florian,

I've seen some amazing things achieved with GSOCs. Take Django's Meta API
by Daniel Pyrathon [1] as a good example.

See here how Django GSOC devs/mentors wrote some really nice ideas for
students to pick from (including the Meta API idea) [2] [3].

[1]
https://www.google-melange.com/gsoc/project/details/google/gsoc2014/pirosb3/5649050225344512
[2] https://code.djangoproject.com/wiki/SummerOfCode2014
[3] https://code.djangoproject.com/wiki/SummerOfCode2015

Tom

On 10 February 2016 at 17:00, <pytest-dev-request at python.org> wrote:

> Date: Wed, 10 Feb 2016 13:59:42 +0100
> From: Florian Bruhin <me at the-compiler.org>
> To: pytest-dev at python.org
> Subject: [pytest-dev] Google Summer Of Code
> Message-ID: <20160210125942.GJ10579 at tonks>
> Content-Type: text/plain; charset="us-ascii"
>
> Hey,
>
> I was asked by qutebrowser users if I want to participate as an
> organization for Google's Summer Of Code - while I don't think it
> makes sense for a "smaller" project like qutebrowser, I think it'd
> make a lot of sense for pytest!
>
> The idea of GSoC is that opensource projects apply for it, then
> students apply to a given project, then contribute a significant
> amount of work (being mentored by project members) and in exchange get
> a stipend (~USD 5000) from Google.
>
> Applications are open until Feburary 19th (Friday in a week...) - what
> about trying with pytest?
>
> What we'd need are two (or more) administrative organisators (I'd
> volunteer) and mentors.
>
> The PSF is also available as an umbrella organization:
> https://wiki.python.org/moin/SummerOfCode/2016
>
> What do you think?
>
> Florian
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160210/20462c2b/attachment.html>

From dhunt at mozilla.com  Wed Feb 10 15:14:44 2016
From: dhunt at mozilla.com (Dave Hunt)
Date: Wed, 10 Feb 2016 20:14:44 +0000
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <6857A31A-FD3E-434C-8F40-189FBAC5D88C@mozilla.com>
References: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>
 <CAPjwCjsH-ooSzQ4pTQKhq=14vAG9pasJmQurzbqWcGcX4cs8yQ@mail.gmail.com>
 <DFF0964C-990E-41C2-90E0-51F1C21223CD@mozilla.com>
 <A926C829-CB10-429D-9782-C96256271D0A@mozilla.com>
 <20160209140953.GH15751@merlinux.eu>
 <6857A31A-FD3E-434C-8F40-189FBAC5D88C@mozilla.com>
Message-ID: <D36ADF22-B6B7-48DA-AA08-0AB7E33F44BA@mozilla.com>

We have an invitation to be discuss/promote the sprint on the Python Test Podcast if anyone wants to volunteer!
https://twitter.com/brianokken/status/697419561797160960 <https://twitter.com/brianokken/status/697419561797160960>

Cheers,
Dave

> On 9 Feb 2016, at 17:16, Dave Hunt <dhunt at mozilla.com> wrote:
> 
> Published:
> http://blargon7.com/2016/02/python-testing-sprint-2016/ <http://blargon7.com/2016/02/python-testing-sprint-2016/>
> 
> Dave
> 
>> On 9 Feb 2016, at 14:09, holger krekel <holger at merlinux.eu <mailto:holger at merlinux.eu>> wrote:
>> 
>> On Tue, Feb 09, 2016 at 14:07 +0000, Dave Hunt wrote:
>>> I have a public preview of my blog post. Feedback welcome:
>>> http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07 <http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07> <http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07 <http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07>>
>> 
>> reads good!
>> 
>> holger
>> 
>>> Dave
>>> 
>>>> On 9 Feb 2016, at 10:40, Dave Hunt <dhunt at mozilla.com <mailto:dhunt at mozilla.com>> wrote:
>>>> 
>>>> I think this is a great idea! I have had approval to join you all during the sprint, so I?d be happy to write a blog post about how I came to pytest and what I?d like to work on during the week.
>>>> 
>>>> Cheers,
>>>> Dave
>>>> 
>>>>> On 8 Feb 2016, at 20:05, Brianna Laugher <brianna.laugher at gmail.com <mailto:brianna.laugher at gmail.com> <mailto:brianna.laugher at gmail.com <mailto:brianna.laugher at gmail.com>>> wrote:
>>>>> 
>>>>> Heh, I had the exact same idea last night :)
>>>>> 
>>>>> I was thinking
>>>>> 1) how did you get involved with pytest?
>>>>> 2) What is your favourite feature/plugin of pytest that is relatively unknown?
>>>>> 3) What are you planning to work on during the sprint?
>>>>> 
>>>>> Cheers
>>>>> Brianna
>>>>> 
>>>>> On 09/02/2016 6:04 AM, "Holger Krekel" <holger at merlinux.eu <mailto:holger at merlinux.eu> <mailto:holger at merlinux.eu <mailto:holger at merlinux.eu>>> wrote:
>>>>> What about if each of us who wants to participate writes a small blog (lacking a blog a pytest-dev) post of where he/she comes from, past core or plugin work for example, and main areas of interest for the sprint? 
>>>>> 
>>>>> We could publish them via updates every few days. Any takers? 
>>>>> -- 
>>>>> Sent using mobile touch keys, increased chances for errors and misunderstandings. Enjoy! 
>>>>> _______________________________________________
>>>>> pytest-dev mailing list
>>>>> pytest-dev at python.org <mailto:pytest-dev at python.org> <mailto:pytest-dev at python.org <mailto:pytest-dev at python.org>>
>>>>> https://mail.python.org/mailman/listinfo/pytest-dev <https://mail.python.org/mailman/listinfo/pytest-dev> <https://mail.python.org/mailman/listinfo/pytest-dev <https://mail.python.org/mailman/listinfo/pytest-dev>>
>>>>> 
>>>>> _______________________________________________
>>>>> pytest-dev mailing list
>>>>> pytest-dev at python.org <mailto:pytest-dev at python.org> <mailto:pytest-dev at python.org <mailto:pytest-dev at python.org>>
>>>>> https://mail.python.org/mailman/listinfo/pytest-dev <https://mail.python.org/mailman/listinfo/pytest-dev>
>>>> 
>>> 
>> 
>> -- 
>> about me:    http://holgerkrekel.net/about-me/ <http://holgerkrekel.net/about-me/>
>> contracting: http://merlinux.eu <http://merlinux.eu/>
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160210/32b08b56/attachment.html>

From raphael at hackebrot.de  Wed Feb 10 16:58:24 2016
From: raphael at hackebrot.de (Raphael Pierzina)
Date: Wed, 10 Feb 2016 21:58:24 +0000
Subject: [pytest-dev] Twitter update
In-Reply-To: <CAPjwCjub+o4EV_3TvtTgE4x4HptU7TVseUQwDUggVa+sJ=zDwQ@mail.gmail.com>
References: <CAPjwCjub+o4EV_3TvtTgE4x4HptU7TVseUQwDUggVa+sJ=zDwQ@mail.gmail.com>
Message-ID: <C71B1625-6F86-4594-8FBF-E24960A47B04@hackebrot.de>

Thank you Brianna!

> On 10 Feb 2016, at 12:19, Brianna Laugher <brianna.laugher at gmail.com> wrote:
> 
> Hi,
> 
> I added Holger @hpk42 and Raphael @hackebrot to the pytestdotorg twitter account so they can tweet from it (via tweetdeck.twitter.com <http://tweetdeck.twitter.com/>). If anyone else feels like they might be inspired to tweet on behalf of pytest, let me know offlist.
> 
> cheers
> Brianna
> 
> 
> -- 
> They've just been waiting in a mountain for the right moment: http://modernthings.org/ <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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160210/b8899170/attachment-0001.html>

From alexamici at gmail.com  Thu Feb 11 03:33:09 2016
From: alexamici at gmail.com (Alessandro Amici)
Date: Thu, 11 Feb 2016 08:33:09 +0000
Subject: [pytest-dev] How to sandbox test execution with pytest
Message-ID: <CACnxfA_vT9wyKxgsJ7UfzpvE0ndcfAVmNgbywnV6dXjA_qOPtA@mail.gmail.com>

Hi,

I asked the following question on StackOverflow first
http://stackoverflow.com/questions/35322452, but someone quickly (and
wrongly in my opinion) marked that as duplicate of the general "sandboxing
in python", so I can't get answers there anymore :(

Here is the question:

I'm interested in executing potentially untrusted tests with pytest in some
kind of sandbox, similarly to what continuous integration services do.

I understand that to properly sandbox a python process you need OS-level
isolation, like running the tests in a disposable chroot/container, but in
my use case I don't need to protect against intentionally malicious code,
only from dangerous behaviour of pairing "randomly" functions with
arguments. So lesser strict sandboxing may still be acceptable. But I
didn't find any plugin that enables any form of sandboxing.

What is the best way to sandbox tests execution in pytest?

**Update**: This question is not about [python sandboxing in general](
http://stackoverflow.com/questions/3068139/how-can-i-sandbox-python-in-pure-python)
as the tests' code is run by pytest and I can't change the way it is
executed to use `exec` or `ast` or whatever. Also using pypy-sandbox is not
an option unfortunately as it is "a prototype only" as per the [PyPy
feature page](http://pypy.org/features.html).

End of question.

For context I'm writing a pytest plugin that lets you search installed
modules for functions that pass the given feature-specification tests
(still alpha):

https://github.com/alexamici/pytest-wish

If you find the question useful and not answered already on stackoverflow,
the best course of action would be to reopen it and answer there, but I'll
take also an answer here :)

Alessandro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160211/ee15dd3c/attachment.html>

From holger at merlinux.eu  Thu Feb 11 04:09:55 2016
From: holger at merlinux.eu (holger krekel)
Date: Thu, 11 Feb 2016 09:09:55 +0000
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <D36ADF22-B6B7-48DA-AA08-0AB7E33F44BA@mozilla.com>
References: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>
 <CAPjwCjsH-ooSzQ4pTQKhq=14vAG9pasJmQurzbqWcGcX4cs8yQ@mail.gmail.com>
 <DFF0964C-990E-41C2-90E0-51F1C21223CD@mozilla.com>
 <A926C829-CB10-429D-9782-C96256271D0A@mozilla.com>
 <20160209140953.GH15751@merlinux.eu>
 <6857A31A-FD3E-434C-8F40-189FBAC5D88C@mozilla.com>
 <D36ADF22-B6B7-48DA-AA08-0AB7E33F44BA@mozilla.com>
Message-ID: <20160211090955.GQ15751@merlinux.eu>


Hey Bruno,

what about you?  You have been incredibly active and it'd be cool to see
you interviewed :)  I think apart from the campaign it'd be interesting
to talk about pytest-3.0 and xdist improvements that we are looking into ...

best,
holger


On Wed, Feb 10, 2016 at 20:14 +0000, Dave Hunt wrote:
> We have an invitation to be discuss/promote the sprint on the Python Test Podcast if anyone wants to volunteer!
> https://twitter.com/brianokken/status/697419561797160960 <https://twitter.com/brianokken/status/697419561797160960>
> 
> Cheers,
> Dave
> 
> > On 9 Feb 2016, at 17:16, Dave Hunt <dhunt at mozilla.com> wrote:
> > 
> > Published:
> > http://blargon7.com/2016/02/python-testing-sprint-2016/ <http://blargon7.com/2016/02/python-testing-sprint-2016/>
> > 
> > Dave
> > 
> >> On 9 Feb 2016, at 14:09, holger krekel <holger at merlinux.eu <mailto:holger at merlinux.eu>> wrote:
> >> 
> >> On Tue, Feb 09, 2016 at 14:07 +0000, Dave Hunt wrote:
> >>> I have a public preview of my blog post. Feedback welcome:
> >>> http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07 <http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07> <http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07 <http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07>>
> >> 
> >> reads good!
> >> 
> >> holger
> >> 
> >>> Dave
> >>> 
> >>>> On 9 Feb 2016, at 10:40, Dave Hunt <dhunt at mozilla.com <mailto:dhunt at mozilla.com>> wrote:
> >>>> 
> >>>> I think this is a great idea! I have had approval to join you all during the sprint, so I?d be happy to write a blog post about how I came to pytest and what I?d like to work on during the week.
> >>>> 
> >>>> Cheers,
> >>>> Dave
> >>>> 
> >>>>> On 8 Feb 2016, at 20:05, Brianna Laugher <brianna.laugher at gmail.com <mailto:brianna.laugher at gmail.com> <mailto:brianna.laugher at gmail.com <mailto:brianna.laugher at gmail.com>>> wrote:
> >>>>> 
> >>>>> Heh, I had the exact same idea last night :)
> >>>>> 
> >>>>> I was thinking
> >>>>> 1) how did you get involved with pytest?
> >>>>> 2) What is your favourite feature/plugin of pytest that is relatively unknown?
> >>>>> 3) What are you planning to work on during the sprint?
> >>>>> 
> >>>>> Cheers
> >>>>> Brianna
> >>>>> 
> >>>>> On 09/02/2016 6:04 AM, "Holger Krekel" <holger at merlinux.eu <mailto:holger at merlinux.eu> <mailto:holger at merlinux.eu <mailto:holger at merlinux.eu>>> wrote:
> >>>>> What about if each of us who wants to participate writes a small blog (lacking a blog a pytest-dev) post of where he/she comes from, past core or plugin work for example, and main areas of interest for the sprint? 
> >>>>> 
> >>>>> We could publish them via updates every few days. Any takers? 
> >>>>> -- 
> >>>>> Sent using mobile touch keys, increased chances for errors and misunderstandings. Enjoy! 
> >>>>> _______________________________________________
> >>>>> pytest-dev mailing list
> >>>>> pytest-dev at python.org <mailto:pytest-dev at python.org> <mailto:pytest-dev at python.org <mailto:pytest-dev at python.org>>
> >>>>> https://mail.python.org/mailman/listinfo/pytest-dev <https://mail.python.org/mailman/listinfo/pytest-dev> <https://mail.python.org/mailman/listinfo/pytest-dev <https://mail.python.org/mailman/listinfo/pytest-dev>>
> >>>>> 
> >>>>> _______________________________________________
> >>>>> pytest-dev mailing list
> >>>>> pytest-dev at python.org <mailto:pytest-dev at python.org> <mailto:pytest-dev at python.org <mailto:pytest-dev at python.org>>
> >>>>> https://mail.python.org/mailman/listinfo/pytest-dev <https://mail.python.org/mailman/listinfo/pytest-dev>
> >>>> 
> >>> 
> >> 
> >> -- 
> >> about me:    http://holgerkrekel.net/about-me/ <http://holgerkrekel.net/about-me/>
> >> contracting: http://merlinux.eu <http://merlinux.eu/>
> > 
> 

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From contact at ionelmc.ro  Thu Feb 11 04:39:13 2016
From: contact at ionelmc.ro (=?UTF-8?Q?Ionel_Cristian_M=C4=83rie=C8=99?=)
Date: Thu, 11 Feb 2016 11:39:13 +0200
Subject: [pytest-dev] How to sandbox test execution with pytest
In-Reply-To: <CACnxfA_vT9wyKxgsJ7UfzpvE0ndcfAVmNgbywnV6dXjA_qOPtA@mail.gmail.com>
References: <CACnxfA_vT9wyKxgsJ7UfzpvE0ndcfAVmNgbywnV6dXjA_qOPtA@mail.gmail.com>
Message-ID: <CANkHFr_HksRaVZpn-BTM-4rerGLwsiDt0+cCm4+7O-gb288y8A@mail.gmail.com>

There's the `--boxed` option (from https://pypi.python.org/pypi/pytest-xdist)
but you can easily do your own "insulator" by using fork syscall.


Thanks,
-- Ionel Cristian M?rie?, http://blog.ionelmc.ro

On Thu, Feb 11, 2016 at 10:33 AM, Alessandro Amici <alexamici at gmail.com>
wrote:

> Hi,
>
> I asked the following question on StackOverflow first
> http://stackoverflow.com/questions/35322452, but someone quickly (and
> wrongly in my opinion) marked that as duplicate of the general "sandboxing
> in python", so I can't get answers there anymore :(
>
> Here is the question:
>
> I'm interested in executing potentially untrusted tests with pytest in
> some kind of sandbox, similarly to what continuous integration services do.
>
> I understand that to properly sandbox a python process you need OS-level
> isolation, like running the tests in a disposable chroot/container, but in
> my use case I don't need to protect against intentionally malicious code,
> only from dangerous behaviour of pairing "randomly" functions with
> arguments. So lesser strict sandboxing may still be acceptable. But I
> didn't find any plugin that enables any form of sandboxing.
>
> What is the best way to sandbox tests execution in pytest?
>
> **Update**: This question is not about [python sandboxing in general](
> http://stackoverflow.com/questions/3068139/how-can-i-sandbox-python-in-pure-python)
> as the tests' code is run by pytest and I can't change the way it is
> executed to use `exec` or `ast` or whatever. Also using pypy-sandbox is not
> an option unfortunately as it is "a prototype only" as per the [PyPy
> feature page](http://pypy.org/features.html).
>
> End of question.
>
> For context I'm writing a pytest plugin that lets you search installed
> modules for functions that pass the given feature-specification tests
> (still alpha):
>
> https://github.com/alexamici/pytest-wish
>
> If you find the question useful and not answered already on stackoverflow,
> the best course of action would be to reopen it and answer there, but I'll
> take also an answer here :)
>
> Alessandro
>
>
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160211/edbf34d2/attachment.html>

From holger at merlinux.eu  Thu Feb 11 04:44:22 2016
From: holger at merlinux.eu (holger krekel)
Date: Thu, 11 Feb 2016 09:44:22 +0000
Subject: [pytest-dev] How to sandbox test execution with pytest
In-Reply-To: <CANkHFr_HksRaVZpn-BTM-4rerGLwsiDt0+cCm4+7O-gb288y8A@mail.gmail.com>
References: <CACnxfA_vT9wyKxgsJ7UfzpvE0ndcfAVmNgbywnV6dXjA_qOPtA@mail.gmail.com>
 <CANkHFr_HksRaVZpn-BTM-4rerGLwsiDt0+cCm4+7O-gb288y8A@mail.gmail.com>
Message-ID: <20160211094422.GT15751@merlinux.eu>

On Thu, Feb 11, 2016 at 11:39 +0200, Ionel Cristian M?rie? wrote:
> There's the `--boxed` option (from https://pypi.python.org/pypi/pytest-xdist)
> but you can easily do your own "insulator" by using fork syscall.

Also one can use plain "xdist" which provides process-level isolation.
It shouldn't be too hard to also use another unix user via e.g.:

    py.test --tx ssh=OTHERUSER at localhost --dist=each 

but you need to have setup rsyncing, see https://pypi.python.org/pypi/pytest-xdist
for some more info.  The current "remote" test running is a bit limited
and we plan to improve xdist distribution during the upcoming pytest sprint,
see https://www.indiegogo.com/projects/python-testing-sprint-mid-2016/x/4034848#/
creating an issue for "user-level separation of running tests" or something
similar and adding a little donation is one way to help it :)

best,
holger


> 
> Thanks,
> -- Ionel Cristian M?rie?, http://blog.ionelmc.ro
> 
> On Thu, Feb 11, 2016 at 10:33 AM, Alessandro Amici <alexamici at gmail.com>
> wrote:
> 
> > Hi,
> >
> > I asked the following question on StackOverflow first
> > http://stackoverflow.com/questions/35322452, but someone quickly (and
> > wrongly in my opinion) marked that as duplicate of the general "sandboxing
> > in python", so I can't get answers there anymore :(
> >
> > Here is the question:
> >
> > I'm interested in executing potentially untrusted tests with pytest in
> > some kind of sandbox, similarly to what continuous integration services do.
> >
> > I understand that to properly sandbox a python process you need OS-level
> > isolation, like running the tests in a disposable chroot/container, but in
> > my use case I don't need to protect against intentionally malicious code,
> > only from dangerous behaviour of pairing "randomly" functions with
> > arguments. So lesser strict sandboxing may still be acceptable. But I
> > didn't find any plugin that enables any form of sandboxing.
> >
> > What is the best way to sandbox tests execution in pytest?
> >
> > **Update**: This question is not about [python sandboxing in general](
> > http://stackoverflow.com/questions/3068139/how-can-i-sandbox-python-in-pure-python)
> > as the tests' code is run by pytest and I can't change the way it is
> > executed to use `exec` or `ast` or whatever. Also using pypy-sandbox is not
> > an option unfortunately as it is "a prototype only" as per the [PyPy
> > feature page](http://pypy.org/features.html).
> >
> > End of question.
> >
> > For context I'm writing a pytest plugin that lets you search installed
> > modules for functions that pass the given feature-specification tests
> > (still alpha):
> >
> > https://github.com/alexamici/pytest-wish
> >
> > If you find the question useful and not answered already on stackoverflow,
> > the best course of action would be to reopen it and answer there, but I'll
> > take also an answer here :)
> >
> > Alessandro
> >
> >
> > _______________________________________________
> > 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


-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From alexamici at gmail.com  Thu Feb 11 05:07:59 2016
From: alexamici at gmail.com (Alessandro Amici)
Date: Thu, 11 Feb 2016 10:07:59 +0000
Subject: [pytest-dev] How to sandbox test execution with pytest
In-Reply-To: <20160211094422.GT15751@merlinux.eu>
References: <CACnxfA_vT9wyKxgsJ7UfzpvE0ndcfAVmNgbywnV6dXjA_qOPtA@mail.gmail.com>
 <CANkHFr_HksRaVZpn-BTM-4rerGLwsiDt0+cCm4+7O-gb288y8A@mail.gmail.com>
 <20160211094422.GT15751@merlinux.eu>
Message-ID: <CACnxfA_i4J3=xW3AFpEHHBMd+sUYbg3uK65v2fNsJjg9jq-eMw@mail.gmail.com>

Ionel and Holger,

I had considered the --box option, but it only implements process-level
isolation which is not enough for my use case as I want to protect also
from unrestricted filesystem read/write access. Sorry, I should have
mentioned it in the question.

Holger's suggestion instead looks almost good enough as user-level
isolation is strong and highly customizable. The only problem is that you
need administration access to the machine to create and configure a new
user. I'll look into it as I've never used the --tx option.

Thanks,
Alessandro


On Thu, 11 Feb 2016 at 10:44 holger krekel <holger at merlinux.eu> wrote:

> On Thu, Feb 11, 2016 at 11:39 +0200, Ionel Cristian M?rie? wrote:
> > There's the `--boxed` option (from
> https://pypi.python.org/pypi/pytest-xdist)
> > but you can easily do your own "insulator" by using fork syscall.
>
> Also one can use plain "xdist" which provides process-level isolation.
> It shouldn't be too hard to also use another unix user via e.g.:
>
>     py.test --tx ssh=OTHERUSER at localhost --dist=each
>
> but you need to have setup rsyncing, see
> https://pypi.python.org/pypi/pytest-xdist
> for some more info.  The current "remote" test running is a bit limited
> and we plan to improve xdist distribution during the upcoming pytest
> sprint,
> see
> https://www.indiegogo.com/projects/python-testing-sprint-mid-2016/x/4034848#/
> creating an issue for "user-level separation of running tests" or something
> similar and adding a little donation is one way to help it :)
>
> best,
> holger
>
>
> >
> > Thanks,
> > -- Ionel Cristian M?rie?, http://blog.ionelmc.ro
> >
> > On Thu, Feb 11, 2016 at 10:33 AM, Alessandro Amici <alexamici at gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > I asked the following question on StackOverflow first
> > > http://stackoverflow.com/questions/35322452, but someone quickly (and
> > > wrongly in my opinion) marked that as duplicate of the general
> "sandboxing
> > > in python", so I can't get answers there anymore :(
> > >
> > > Here is the question:
> > >
> > > I'm interested in executing potentially untrusted tests with pytest in
> > > some kind of sandbox, similarly to what continuous integration
> services do.
> > >
> > > I understand that to properly sandbox a python process you need
> OS-level
> > > isolation, like running the tests in a disposable chroot/container,
> but in
> > > my use case I don't need to protect against intentionally malicious
> code,
> > > only from dangerous behaviour of pairing "randomly" functions with
> > > arguments. So lesser strict sandboxing may still be acceptable. But I
> > > didn't find any plugin that enables any form of sandboxing.
> > >
> > > What is the best way to sandbox tests execution in pytest?
> > >
> > > **Update**: This question is not about [python sandboxing in general](
> > >
> http://stackoverflow.com/questions/3068139/how-can-i-sandbox-python-in-pure-python
> )
> > > as the tests' code is run by pytest and I can't change the way it is
> > > executed to use `exec` or `ast` or whatever. Also using pypy-sandbox
> is not
> > > an option unfortunately as it is "a prototype only" as per the [PyPy
> > > feature page](http://pypy.org/features.html).
> > >
> > > End of question.
> > >
> > > For context I'm writing a pytest plugin that lets you search installed
> > > modules for functions that pass the given feature-specification tests
> > > (still alpha):
> > >
> > > https://github.com/alexamici/pytest-wish
> > >
> > > If you find the question useful and not answered already on
> stackoverflow,
> > > the best course of action would be to reopen it and answer there, but
> I'll
> > > take also an answer here :)
> > >
> > > Alessandro
> > >
> > >
> > > _______________________________________________
> > > 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
>
>
> --
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160211/fd7f75b3/attachment.html>

From holger at merlinux.eu  Thu Feb 11 05:14:06 2016
From: holger at merlinux.eu (holger krekel)
Date: Thu, 11 Feb 2016 10:14:06 +0000
Subject: [pytest-dev] Google Summer Of Code
In-Reply-To: <CANBSuyGePu7qaik19KCZRU+L67vqxCKdwg625cDSiWDbV2Cx0A@mail.gmail.com>
References: <CANBSuyGePu7qaik19KCZRU+L67vqxCKdwg625cDSiWDbV2Cx0A@mail.gmail.com>
Message-ID: <20160211101406.GW15751@merlinux.eu>

Hi Florian, Tom,

I've mentored in the past but won't go for it this year.
Maybe it would help to list ideas wiki/web page which briefly
discuss some larger scale ideas about testing/pytest/tox?

holger


On Wed, Feb 10, 2016 at 20:04 +0000, Tom Viner wrote:
> Hi Florian,
> 
> I've seen some amazing things achieved with GSOCs. Take Django's Meta API
> by Daniel Pyrathon [1] as a good example.
> 
> See here how Django GSOC devs/mentors wrote some really nice ideas for
> students to pick from (including the Meta API idea) [2] [3].
> 
> [1]
> https://www.google-melange.com/gsoc/project/details/google/gsoc2014/pirosb3/5649050225344512
> [2] https://code.djangoproject.com/wiki/SummerOfCode2014
> [3] https://code.djangoproject.com/wiki/SummerOfCode2015
> 
> Tom
> 
> On 10 February 2016 at 17:00, <pytest-dev-request at python.org> wrote:
> 
> > Date: Wed, 10 Feb 2016 13:59:42 +0100
> > From: Florian Bruhin <me at the-compiler.org>
> > To: pytest-dev at python.org
> > Subject: [pytest-dev] Google Summer Of Code
> > Message-ID: <20160210125942.GJ10579 at tonks>
> > Content-Type: text/plain; charset="us-ascii"
> >
> > Hey,
> >
> > I was asked by qutebrowser users if I want to participate as an
> > organization for Google's Summer Of Code - while I don't think it
> > makes sense for a "smaller" project like qutebrowser, I think it'd
> > make a lot of sense for pytest!
> >
> > The idea of GSoC is that opensource projects apply for it, then
> > students apply to a given project, then contribute a significant
> > amount of work (being mentored by project members) and in exchange get
> > a stipend (~USD 5000) from Google.
> >
> > Applications are open until Feburary 19th (Friday in a week...) - what
> > about trying with pytest?
> >
> > What we'd need are two (or more) administrative organisators (I'd
> > volunteer) and mentors.
> >
> > The PSF is also available as an umbrella organization:
> > https://wiki.python.org/moin/SummerOfCode/2016
> >
> > What do you think?
> >
> > Florian
> >

> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev


-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From nicoddemus at gmail.com  Thu Feb 11 16:01:52 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 11 Feb 2016 21:01:52 +0000
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <20160211090955.GQ15751@merlinux.eu>
References: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>
 <CAPjwCjsH-ooSzQ4pTQKhq=14vAG9pasJmQurzbqWcGcX4cs8yQ@mail.gmail.com>
 <DFF0964C-990E-41C2-90E0-51F1C21223CD@mozilla.com>
 <A926C829-CB10-429D-9782-C96256271D0A@mozilla.com>
 <20160209140953.GH15751@merlinux.eu>
 <6857A31A-FD3E-434C-8F40-189FBAC5D88C@mozilla.com>
 <D36ADF22-B6B7-48DA-AA08-0AB7E33F44BA@mozilla.com>
 <20160211090955.GQ15751@merlinux.eu>
Message-ID: <CA+RQFfeqTJ06dPCzXv-ZdKXXk4vRkWSvTS3fyt5y1J=oTt_=mg@mail.gmail.com>

Hi Holger,

TBH I'm a little shy of my english speaking skills, so I rather don't do
the interview. :S

Someone else might be more suited!


On Thu, Feb 11, 2016 at 7:10 AM holger krekel <holger at merlinux.eu> wrote:

>
> Hey Bruno,
>
> what about you?  You have been incredibly active and it'd be cool to see
> you interviewed :)  I think apart from the campaign it'd be interesting
> to talk about pytest-3.0 and xdist improvements that we are looking into
> ...
>
> best,
> holger
>
>
> On Wed, Feb 10, 2016 at 20:14 +0000, Dave Hunt wrote:
> > We have an invitation to be discuss/promote the sprint on the Python
> Test Podcast if anyone wants to volunteer!
> > https://twitter.com/brianokken/status/697419561797160960 <
> https://twitter.com/brianokken/status/697419561797160960>
> >
> > Cheers,
> > Dave
> >
> > > On 9 Feb 2016, at 17:16, Dave Hunt <dhunt at mozilla.com> wrote:
> > >
> > > Published:
> > > http://blargon7.com/2016/02/python-testing-sprint-2016/ <
> http://blargon7.com/2016/02/python-testing-sprint-2016/>
> > >
> > > Dave
> > >
> > >> On 9 Feb 2016, at 14:09, holger krekel <holger at merlinux.eu <mailto:
> holger at merlinux.eu>> wrote:
> > >>
> > >> On Tue, Feb 09, 2016 at 14:07 +0000, Dave Hunt wrote:
> > >>> I have a public preview of my blog post. Feedback welcome:
> > >>> http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07 <
> http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07> <
> http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07 <
> http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07>>
> > >>
> > >> reads good!
> > >>
> > >> holger
> > >>
> > >>> Dave
> > >>>
> > >>>> On 9 Feb 2016, at 10:40, Dave Hunt <dhunt at mozilla.com <mailto:
> dhunt at mozilla.com>> wrote:
> > >>>>
> > >>>> I think this is a great idea! I have had approval to join you all
> during the sprint, so I?d be happy to write a blog post about how I came to
> pytest and what I?d like to work on during the week.
> > >>>>
> > >>>> Cheers,
> > >>>> Dave
> > >>>>
> > >>>>> On 8 Feb 2016, at 20:05, Brianna Laugher <
> brianna.laugher at gmail.com <mailto:brianna.laugher at gmail.com> <mailto:
> brianna.laugher at gmail.com <mailto:brianna.laugher at gmail.com>>> wrote:
> > >>>>>
> > >>>>> Heh, I had the exact same idea last night :)
> > >>>>>
> > >>>>> I was thinking
> > >>>>> 1) how did you get involved with pytest?
> > >>>>> 2) What is your favourite feature/plugin of pytest that is
> relatively unknown?
> > >>>>> 3) What are you planning to work on during the sprint?
> > >>>>>
> > >>>>> Cheers
> > >>>>> Brianna
> > >>>>>
> > >>>>> On 09/02/2016 6:04 AM, "Holger Krekel" <holger at merlinux.eu
> <mailto:holger at merlinux.eu> <mailto:holger at merlinux.eu <mailto:
> holger at merlinux.eu>>> wrote:
> > >>>>> What about if each of us who wants to participate writes a small
> blog (lacking a blog a pytest-dev) post of where he/she comes from, past
> core or plugin work for example, and main areas of interest for the sprint?
> > >>>>>
> > >>>>> We could publish them via updates every few days. Any takers?
> > >>>>> --
> > >>>>> Sent using mobile touch keys, increased chances for errors and
> misunderstandings. Enjoy!
> > >>>>> _______________________________________________
> > >>>>> pytest-dev mailing list
> > >>>>> pytest-dev at python.org <mailto:pytest-dev at python.org> <mailto:
> pytest-dev at python.org <mailto:pytest-dev at python.org>>
> > >>>>> https://mail.python.org/mailman/listinfo/pytest-dev <
> https://mail.python.org/mailman/listinfo/pytest-dev> <
> https://mail.python.org/mailman/listinfo/pytest-dev <
> https://mail.python.org/mailman/listinfo/pytest-dev>>
> > >>>>>
> > >>>>> _______________________________________________
> > >>>>> pytest-dev mailing list
> > >>>>> pytest-dev at python.org <mailto:pytest-dev at python.org> <mailto:
> pytest-dev at python.org <mailto:pytest-dev at python.org>>
> > >>>>> https://mail.python.org/mailman/listinfo/pytest-dev <
> https://mail.python.org/mailman/listinfo/pytest-dev>
> > >>>>
> > >>>
> > >>
> > >> --
> > >> about me:    http://holgerkrekel.net/about-me/ <
> http://holgerkrekel.net/about-me/>
> > >> contracting: http://merlinux.eu <http://merlinux.eu/>
> > >
> >
>
> --
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160211/af832e37/attachment.html>

From holger at merlinux.eu  Thu Feb 11 17:02:49 2016
From: holger at merlinux.eu (Holger Krekel)
Date: Thu, 11 Feb 2016 23:02:49 +0100
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <CA+RQFfeqTJ06dPCzXv-ZdKXXk4vRkWSvTS3fyt5y1J=oTt_=mg@mail.gmail.com>
References: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>
 <CAPjwCjsH-ooSzQ4pTQKhq=14vAG9pasJmQurzbqWcGcX4cs8yQ@mail.gmail.com>
 <DFF0964C-990E-41C2-90E0-51F1C21223CD@mozilla.com>
 <A926C829-CB10-429D-9782-C96256271D0A@mozilla.com>
 <20160209140953.GH15751@merlinux.eu>
 <6857A31A-FD3E-434C-8F40-189FBAC5D88C@mozilla.com>
 <D36ADF22-B6B7-48DA-AA08-0AB7E33F44BA@mozilla.com>
 <20160211090955.GQ15751@merlinux.eu>
 <CA+RQFfeqTJ06dPCzXv-ZdKXXk4vRkWSvTS3fyt5y1J=oTt_=mg@mail.gmail.com>
Message-ID: <1FF4AFBC-F983-4315-B9F0-0FE232C6097C@merlinux.eu>

Your written English is pretty good so you feel youbare rather missing practice in pronunciation?  But when we did the hangout I wasn't aware of it :) 



On February 11, 2016 10:01:52 PM GMT+01:00, Bruno Oliveira <nicoddemus at gmail.com> wrote:
>Hi Holger,
>
>TBH I'm a little shy of my english speaking skills, so I rather don't
>do
>the interview. :S
>
>Someone else might be more suited!
>
>
>On Thu, Feb 11, 2016 at 7:10 AM holger krekel <holger at merlinux.eu>
>wrote:
>
>>
>> Hey Bruno,
>>
>> what about you?  You have been incredibly active and it'd be cool to
>see
>> you interviewed :)  I think apart from the campaign it'd be
>interesting
>> to talk about pytest-3.0 and xdist improvements that we are looking
>into
>> ...
>>
>> best,
>> holger
>>
>>
>> On Wed, Feb 10, 2016 at 20:14 +0000, Dave Hunt wrote:
>> > We have an invitation to be discuss/promote the sprint on the
>Python
>> Test Podcast if anyone wants to volunteer!
>> > https://twitter.com/brianokken/status/697419561797160960 <
>> https://twitter.com/brianokken/status/697419561797160960>
>> >
>> > Cheers,
>> > Dave
>> >
>> > > On 9 Feb 2016, at 17:16, Dave Hunt <dhunt at mozilla.com> wrote:
>> > >
>> > > Published:
>> > > http://blargon7.com/2016/02/python-testing-sprint-2016/ <
>> http://blargon7.com/2016/02/python-testing-sprint-2016/>
>> > >
>> > > Dave
>> > >
>> > >> On 9 Feb 2016, at 14:09, holger krekel <holger at merlinux.eu
><mailto:
>> holger at merlinux.eu>> wrote:
>> > >>
>> > >> On Tue, Feb 09, 2016 at 14:07 +0000, Dave Hunt wrote:
>> > >>> I have a public preview of my blog post. Feedback welcome:
>> > >>> http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07 <
>> http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07> <
>> http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07 <
>> http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07>>
>> > >>
>> > >> reads good!
>> > >>
>> > >> holger
>> > >>
>> > >>> Dave
>> > >>>
>> > >>>> On 9 Feb 2016, at 10:40, Dave Hunt <dhunt at mozilla.com <mailto:
>> dhunt at mozilla.com>> wrote:
>> > >>>>
>> > >>>> I think this is a great idea! I have had approval to join you
>all
>> during the sprint, so I?d be happy to write a blog post about how I
>came to
>> pytest and what I?d like to work on during the week.
>> > >>>>
>> > >>>> Cheers,
>> > >>>> Dave
>> > >>>>
>> > >>>>> On 8 Feb 2016, at 20:05, Brianna Laugher <
>> brianna.laugher at gmail.com <mailto:brianna.laugher at gmail.com> <mailto:
>> brianna.laugher at gmail.com <mailto:brianna.laugher at gmail.com>>> wrote:
>> > >>>>>
>> > >>>>> Heh, I had the exact same idea last night :)
>> > >>>>>
>> > >>>>> I was thinking
>> > >>>>> 1) how did you get involved with pytest?
>> > >>>>> 2) What is your favourite feature/plugin of pytest that is
>> relatively unknown?
>> > >>>>> 3) What are you planning to work on during the sprint?
>> > >>>>>
>> > >>>>> Cheers
>> > >>>>> Brianna
>> > >>>>>
>> > >>>>> On 09/02/2016 6:04 AM, "Holger Krekel" <holger at merlinux.eu
>> <mailto:holger at merlinux.eu> <mailto:holger at merlinux.eu <mailto:
>> holger at merlinux.eu>>> wrote:
>> > >>>>> What about if each of us who wants to participate writes a
>small
>> blog (lacking a blog a pytest-dev) post of where he/she comes from,
>past
>> core or plugin work for example, and main areas of interest for the
>sprint?
>> > >>>>>
>> > >>>>> We could publish them via updates every few days. Any takers?
>> > >>>>> --
>> > >>>>> Sent using mobile touch keys, increased chances for errors
>and
>> misunderstandings. Enjoy!
>> > >>>>> _______________________________________________
>> > >>>>> pytest-dev mailing list
>> > >>>>> pytest-dev at python.org <mailto:pytest-dev at python.org> <mailto:
>> pytest-dev at python.org <mailto:pytest-dev at python.org>>
>> > >>>>> https://mail.python.org/mailman/listinfo/pytest-dev <
>> https://mail.python.org/mailman/listinfo/pytest-dev> <
>> https://mail.python.org/mailman/listinfo/pytest-dev <
>> https://mail.python.org/mailman/listinfo/pytest-dev>>
>> > >>>>>
>> > >>>>> _______________________________________________
>> > >>>>> pytest-dev mailing list
>> > >>>>> pytest-dev at python.org <mailto:pytest-dev at python.org> <mailto:
>> pytest-dev at python.org <mailto:pytest-dev at python.org>>
>> > >>>>> https://mail.python.org/mailman/listinfo/pytest-dev <
>> https://mail.python.org/mailman/listinfo/pytest-dev>
>> > >>>>
>> > >>>
>> > >>
>> > >> --
>> > >> about me:    http://holgerkrekel.net/about-me/ <
>> http://holgerkrekel.net/about-me/>
>> > >> contracting: http://merlinux.eu <http://merlinux.eu/>
>> > >
>> >
>>
>> --
>> about me:    http://holgerkrekel.net/about-me/
>> contracting: http://merlinux.eu
>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>

-- 
Sent using mobile touch keys, increased chances for errors and misunderstandings. Enjoy! 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160211/afc9d0d8/attachment-0001.html>

From alexamici at gmail.com  Fri Feb 12 03:06:18 2016
From: alexamici at gmail.com (Alessandro Amici)
Date: Fri, 12 Feb 2016 08:06:18 +0000
Subject: [pytest-dev] How to sandbox test execution with pytest
In-Reply-To: <CACnxfA_i4J3=xW3AFpEHHBMd+sUYbg3uK65v2fNsJjg9jq-eMw@mail.gmail.com>
References: <CACnxfA_vT9wyKxgsJ7UfzpvE0ndcfAVmNgbywnV6dXjA_qOPtA@mail.gmail.com>
 <CANkHFr_HksRaVZpn-BTM-4rerGLwsiDt0+cCm4+7O-gb288y8A@mail.gmail.com>
 <20160211094422.GT15751@merlinux.eu>
 <CACnxfA_i4J3=xW3AFpEHHBMd+sUYbg3uK65v2fNsJjg9jq-eMw@mail.gmail.com>
Message-ID: <CACnxfA_M0UV7wN_bGj-pVxncuR5OtjCKWV55PD30qFnxi7zKPQ@mail.gmail.com>

Hi,

while researching the use of pytest-xdist for my CI-like use case and I
realised that having a "disposable" environment is as important as having a
isolated one, so that every test or every session runs from the same
initial state and it is not influenced by what older sessions might have
left on folders writable by the *testuser* (/home/testuser, /tmp, /var/tmp,
etc).

This made me go back searching the web again for a way to use pytest with
docker and I'm currently evaluating the following projects:

https://github.com/search?q=pytest+docker

Does anybody have experience with pytest/docker integration or with any of
these projects?

I'll report back what I find.

Thanks,
Alessandro

On Thu, 11 Feb 2016 at 11:07 Alessandro Amici <alexamici at gmail.com> wrote:

> Ionel and Holger,
>
> I had considered the --box option, but it only implements process-level
> isolation which is not enough for my use case as I want to protect also
> from unrestricted filesystem read/write access. Sorry, I should have
> mentioned it in the question.
>
> Holger's suggestion instead looks almost good enough as user-level
> isolation is strong and highly customizable. The only problem is that you
> need administration access to the machine to create and configure a new
> user. I'll look into it as I've never used the --tx option.
>
> Thanks,
> Alessandro
>
>
> On Thu, 11 Feb 2016 at 10:44 holger krekel <holger at merlinux.eu> wrote:
>
>> On Thu, Feb 11, 2016 at 11:39 +0200, Ionel Cristian M?rie? wrote:
>> > There's the `--boxed` option (from
>> https://pypi.python.org/pypi/pytest-xdist)
>> > but you can easily do your own "insulator" by using fork syscall.
>>
>> Also one can use plain "xdist" which provides process-level isolation.
>> It shouldn't be too hard to also use another unix user via e.g.:
>>
>>     py.test --tx ssh=OTHERUSER at localhost --dist=each
>>
>> but you need to have setup rsyncing, see
>> https://pypi.python.org/pypi/pytest-xdist
>> for some more info.  The current "remote" test running is a bit limited
>> and we plan to improve xdist distribution during the upcoming pytest
>> sprint,
>> see
>> https://www.indiegogo.com/projects/python-testing-sprint-mid-2016/x/4034848#/
>> creating an issue for "user-level separation of running tests" or
>> something
>> similar and adding a little donation is one way to help it :)
>>
>> best,
>> holger
>>
>>
>> >
>> > Thanks,
>> > -- Ionel Cristian M?rie?, http://blog.ionelmc.ro
>> >
>> > On Thu, Feb 11, 2016 at 10:33 AM, Alessandro Amici <alexamici at gmail.com
>> >
>> > wrote:
>> >
>> > > Hi,
>> > >
>> > > I asked the following question on StackOverflow first
>> > > http://stackoverflow.com/questions/35322452, but someone quickly (and
>> > > wrongly in my opinion) marked that as duplicate of the general
>> "sandboxing
>> > > in python", so I can't get answers there anymore :(
>> > >
>> > > Here is the question:
>> > >
>> > > I'm interested in executing potentially untrusted tests with pytest in
>> > > some kind of sandbox, similarly to what continuous integration
>> services do.
>> > >
>> > > I understand that to properly sandbox a python process you need
>> OS-level
>> > > isolation, like running the tests in a disposable chroot/container,
>> but in
>> > > my use case I don't need to protect against intentionally malicious
>> code,
>> > > only from dangerous behaviour of pairing "randomly" functions with
>> > > arguments. So lesser strict sandboxing may still be acceptable. But I
>> > > didn't find any plugin that enables any form of sandboxing.
>> > >
>> > > What is the best way to sandbox tests execution in pytest?
>> > >
>> > > **Update**: This question is not about [python sandboxing in general](
>> > >
>> http://stackoverflow.com/questions/3068139/how-can-i-sandbox-python-in-pure-python
>> )
>> > > as the tests' code is run by pytest and I can't change the way it is
>> > > executed to use `exec` or `ast` or whatever. Also using pypy-sandbox
>> is not
>> > > an option unfortunately as it is "a prototype only" as per the [PyPy
>> > > feature page](http://pypy.org/features.html).
>> > >
>> > > End of question.
>> > >
>> > > For context I'm writing a pytest plugin that lets you search installed
>> > > modules for functions that pass the given feature-specification tests
>> > > (still alpha):
>> > >
>> > > https://github.com/alexamici/pytest-wish
>> > >
>> > > If you find the question useful and not answered already on
>> stackoverflow,
>> > > the best course of action would be to reopen it and answer there, but
>> I'll
>> > > take also an answer here :)
>> > >
>> > > Alessandro
>> > >
>> > >
>> > > _______________________________________________
>> > > 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
>>
>>
>> --
>> about me:    http://holgerkrekel.net/about-me/
>> contracting: http://merlinux.eu
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160212/e85fdebf/attachment.html>

From holger at merlinux.eu  Fri Feb 12 06:21:56 2016
From: holger at merlinux.eu (holger krekel)
Date: Fri, 12 Feb 2016 11:21:56 +0000
Subject: [pytest-dev] devpi-server/web-3.0: generalized mirroring, speed,
 new backends
Message-ID: <20160212112156.GT28566@merlinux.eu>


We just released devpi-{server,web}-3.0 and devpi-client-2.5.0 with some
major new features, see the announcement below.  didn't want to cram
too many mailing lists into it in case someone hits "reply all" :)

have fun,
holger

----- Forwarded message from holger krekel <holger at merlinux.eu> -----

Date: Fri, 12 Feb 2016 11:13:36 +0000
From: holger krekel <holger at merlinux.eu>
To: python announce <python-announce-list at python.org>,
	Testing in Python <testing-in-python at lists.idyll.org>,
	disutils-sig <distutils-sig at python.org>
Subject: devpi-server/web-3.0: generalized mirroring, speed, new backends


The 3.0 releases of devpi-server and devpi-web, the python packaging and 
work flow system for handling release files, documentation, testing and staging,
bring several major improvements:

- Due to popular demand we now support generalized mirroring, i.e. you can 
  create mirror indexes which proxy and cache release files from other pypi 
  servers.  Even if the mirror goes down, pip-installing will continue to work
  with your devpi-server instance.  Previously we only supported mirroring 
  of pypi.python.org.  Using it is simple:
  http://doc.devpi.net/3.0/userman/devpi_indices.html#mirror-index

- For our enterprise clients we majorly worked on improving the speed
  of serving simple pages which is now several times faster with
  private indexes.  We now also support multiple worker processes
  both on master and replica sites.
  http://doc.devpi.net/3.0/adminman/server.html#multiple-server-instances

- For our enterprise clients we also introduced a new backend
  architecture which allows to store server state in sqlite or
  postgres (which is supported through a separately released plugin).
  The default remains to use the "sqlite" backend and store files
  on the filesystem. See
  http://doc.devpi.net/3.0/adminman/server.html#storage-backend-selection

- we started a new "admin" manual for devpi-server which describes
  features relating to server configuration, replication and security
  aspects.  It's a bit work-in-progress but should already be helpful.
  http://doc.devpi.net/3.0/adminman/

- A few option names changed and we also released devpi-client-2.5 
  where we took great care to keep it forward and backward compatible
  so it should run against devpi-server-2.1 and upwards all the way
  to 3.0.

- The "3.0" major release number increase means that you will need to run 
  through an export/import cycle to upgrade your devpi-2.X installation.

For more details, see the changelog and the referenced documentation
with the main entry point here:

    http://doc.devpi.net

Many thanks to my partner Florian Schulze and to the several companies
who funded parts of the work on 3.0.  We are especially grateful for
their support to not only cover their own direct issues but also support
community driven demands.  I'd also like to express my gratitude to
Rackspace and Jesse Noller who provide VMs for our open source work and
which help a lot with the testing of our releases.

We are open towards entering more support contracts to make sure you get
what you need out of devpi, tox and pytest which together provide a
mature tool chain for professional python development.  And speaking of
showing support, if you or your company is interested to donate to or
attend the largest python testing sprint in history with a particular
focus to pytest or tox, please see

    https://www.indiegogo.com/projects/python-testing-sprint-mid-2016/

have fun,

holger krekel, http://merlinux.eu



server-3.0.0 (2016-02-12)
-------------------------

- dropped support for python2.6

- block most ascii symbols for user and index names except ``-. at _``.
  unicode characters are fine.

- add ``--no-root-pypi`` option which prevents the creation of the
  ``root/pypi`` mirror instance on first startup.

- added optional ``title`` and ``description`` options to users and indexes.

- new indexes have no bases by default anymore. If you want to be able to
  install pypi packages, then you have to explicitly add ``root/pypi`` to
  the ``bases`` option of your index.

- added optional ``custom_data`` option to users.

- generalized mirroring to allow adding mirror indexes other than only PyPI

- renamed ``pypi_whitelist`` to ``mirror_whitelist``

- speed up simple-page serving for private indexes. A private index
  with 200 release files should now be some 5 times faster.

- internally use normalized project names everywhere, simplifying
  code and slightly speeding up some operations.

- change {name} in route_urls to {project} to disambiguate.
  This is potentially incompatible for plugins which have registered
  on existing route_urls.

- use "project" variable naming consistently in APIs

- drop calling of devpi_pypi_initial hook in favor of
  the new "devpi_mirror_initialnames(stage, projectnames)" hook
  which is called when a mirror is initialized.

- introduce new "devpiserver_stage_created(stage)" hook which is
  called for each index which is created.

- simplify and unify internal mirroring code some more
  with "normal" stage handling.

- don't persist the list of mirrored project names anymore
  but rely on a per-process RAM cache and the fact
  that neither the UI nor pip/easy_install typically
  need the projectnames list, anyway.

- introduce new "devpiserver_storage_backend" hook which allows plugins to
  provide custom storage backends. When there is more than one backend
  available, the "--storage" option becomes required for startup.

- introduce new "--requests-only" option to start devpi-server in
  "worker" mode.  It can be used both for master and replica sites.  It
  starts devpi-server without event processing and replication threads and
  thus depends on respective "main" instances (those not using
  "--request-only") to perform event and hook processing.  Each
  worker instance needs to share the filesystem with a main instance.
  Worker instances can not serve the "/+status" URL which must
  always be routed to the main instance.

- add more info when importing data.  Thanks Marc Abramowitz for the PR.


web-3.0.0 (2016-02-12)
----------------------

- dropped support for python2.6

- index.pt, root.pt, style.css: added title and description to
  users and indexes.

- root.pt, style.css: more compact styling of user/index overview using
  flexbox, resulting in three columns at most sizes

- cleanup previously unpacked documentation to remove obsolete files.

- store hash of doczip with the unpacked data to avoid unpacking if the data
  already exists.

- project.pt, version.pt: renamed ``pypi_whitelist`` related things to
  ``mirror_whitelist``.

- require and adapt to devpi-server-3.0.0 which always uses
  normalized project names internally and offers new hooks.
  devpi-web-3.0.0 is incompatible to devpi-server-2.X.

- doc.pt, macros.pt, style.css, docview.js: use scrollbar of documentation
  iframe, so documentation that contains dynamically resizing elements works
  correctly. For that to work, the search from and navigation was moved into a
  wrapping div with class ``header``, so it can overlap the top of the iframe.


2.5.0 (2016-02-08)
------------------

- the ``user`` command now behaves slightly more like ``index`` to show
  current user settings and modify them.

- fix issue309: print server versions with ``devpi --version`` if available.
  This is only supported on Python 3.x because of shortcomings in older
  argparse versions for Python 2.x.

- fix issue310: with --set-cfg the ``index`` setting in the ``[search]``
  section would be set multiple times.

- fix getjson to work when no index but a server is selected

- allow full urls for getjson

- "devpi quickstart" is not documented anymore and will be removed
  in a later release.

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

----- End forwarded message -----

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From jaraco at jaraco.com  Fri Feb 12 20:19:25 2016
From: jaraco at jaraco.com (Jason R. Coombs)
Date: Sat, 13 Feb 2016 01:19:25 +0000
Subject: [pytest-dev] Move pytest-runner to github
Message-ID: <5E4F63DB-BF06-4569-BC53-29E60D511454@jaraco.com>

I?ve been moving most of my projects to Github. I?d like to do the same with pytest-runner. Would someone create the repo and/or grant me the necessary access, including admin access to the created repo? Probably /pytest-dev/pytest-runner.

Thanks,
Jason (jaraco)

From nicoddemus at gmail.com  Fri Feb 12 22:34:17 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Sat, 13 Feb 2016 03:34:17 +0000
Subject: [pytest-dev] Move pytest-runner to github
In-Reply-To: <5E4F63DB-BF06-4569-BC53-29E60D511454@jaraco.com>
References: <5E4F63DB-BF06-4569-BC53-29E60D511454@jaraco.com>
Message-ID: <CA+RQFfdFNfnj4RY=X32SjSvBcx35Lr3MRfHB3uxQw4DNey6a7g@mail.gmail.com>

Hi Jason,

I've invited you and created an empty repository at
https://github.com/pytest-dev/pytest-runner, you should have admins right
to that so feel free to add others as you see fit. :)

Thanks,
Bruno.

On Sat, Feb 13, 2016 at 12:52 AM Jason R. Coombs <jaraco at jaraco.com> wrote:

> I?ve been moving most of my projects to Github. I?d like to do the same
> with pytest-runner. Would someone create the repo and/or grant me the
> necessary access, including admin access to the created repo? Probably
> /pytest-dev/pytest-runner.
>
> Thanks,
> Jason (jaraco)
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160213/1794d698/attachment.html>

From nicoddemus at gmail.com  Fri Feb 12 22:45:56 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Sat, 13 Feb 2016 03:45:56 +0000
Subject: [pytest-dev] Visibility of project members
Message-ID: <CA+RQFfd74vSVoPzH4QU2AggHuc+XCKdwh-=W=qCRS3POvvCG2g@mail.gmail.com>

Hi all,

I was browsing the peoples page at
https://github.com/orgs/pytest-dev/people and
noticed that most members have their membership set as "private". I believe
most people left that setting as private because it is the default. You can
easily see your setting to members outside the organization by browsing
that page in incognito mode.

Just a heads up in case anyone wants their membership as public. :)

Thanks,
Bruno.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160213/01cfeb67/attachment.html>

From brianna.laugher at gmail.com  Fri Feb 12 23:06:15 2016
From: brianna.laugher at gmail.com (Brianna Laugher)
Date: Sat, 13 Feb 2016 15:06:15 +1100
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <1FF4AFBC-F983-4315-B9F0-0FE232C6097C@merlinux.eu>
References: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>
 <CAPjwCjsH-ooSzQ4pTQKhq=14vAG9pasJmQurzbqWcGcX4cs8yQ@mail.gmail.com>
 <DFF0964C-990E-41C2-90E0-51F1C21223CD@mozilla.com>
 <A926C829-CB10-429D-9782-C96256271D0A@mozilla.com>
 <20160209140953.GH15751@merlinux.eu>
 <6857A31A-FD3E-434C-8F40-189FBAC5D88C@mozilla.com>
 <D36ADF22-B6B7-48DA-AA08-0AB7E33F44BA@mozilla.com>
 <20160211090955.GQ15751@merlinux.eu>
 <CA+RQFfeqTJ06dPCzXv-ZdKXXk4vRkWSvTS3fyt5y1J=oTt_=mg@mail.gmail.com>
 <1FF4AFBC-F983-4315-B9F0-0FE232C6097C@merlinux.eu>
Message-ID: <CAPjwCjscXJ3=ji8MzunZd_Tc_z1JQx-BumqP_uoqn1z6gyv32Q@mail.gmail.com>

Your writing is great Bruno! If you wanted I would be happy to edit a draft
though.

Andreas, how about you? You could speak about your company's support too :)

Brianna

On 12 February 2016 at 09:02, Holger Krekel <holger at merlinux.eu> wrote:

> Your written English is pretty good so you feel youbare rather missing
> practice in pronunciation? But when we did the hangout I wasn't aware of it
> :)
>
>
>
> On February 11, 2016 10:01:52 PM GMT+01:00, Bruno Oliveira <
> nicoddemus at gmail.com> wrote:
>>
>> Hi Holger,
>>
>> TBH I'm a little shy of my english speaking skills, so I rather don't do
>> the interview. :S
>>
>> Someone else might be more suited!
>>
>>
>> On Thu, Feb 11, 2016 at 7:10 AM holger krekel <holger at merlinux.eu> wrote:
>>
>>>
>>> Hey Bruno,
>>>
>>> what about you?  You have been incredibly active and it'd be cool to see
>>> you interviewed :)  I think apart from the campaign it'd be interesting
>>> to talk about pytest-3.0 and xdist improvements that we are looking into
>>> ...
>>>
>>> best,
>>> holger
>>>
>>>
>>> On Wed, Feb 10, 2016 at 20:14 +0000, Dave Hunt wrote:
>>> > We have an invitation to be discuss/promote the sprint on the Python
>>> Test Podcast if anyone wants to volunteer!
>>> > https://twitter.com/brianokken/status/697419561797160960 <
>>> https://twitter.com/brianokken/status/697419561797160960>
>>> >
>>> > Cheers,
>>> > Dave
>>> >
>>> > > On 9 Feb 2016, at 17:16, Dave Hunt <dhunt at mozilla.com> wrote:
>>> > >
>>> > > Published:
>>> > > http://blargon7.com/2016/02/python-testing-sprint-2016/ <
>>> http://blargon7.com/2016/02/python-testing-sprint-2016/>
>>> > >
>>> > > Dave
>>> > >
>>> > >> On 9 Feb 2016, at 14:09, holger krekel <holger at merlinux.eu <mailto:
>>> holger at merlinux.eu>> wrote:
>>> > >>
>>> > >> On Tue, Feb 09, 2016 at 14:07 +0000, Dave Hunt wrote:
>>> > >>> I have a public preview of my blog post. Feedback welcome:
>>> > >>> http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07 <
>>> http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07> <
>>> http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07 <
>>> http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07>>
>>> > >>
>>> > >> reads good!
>>> > >>
>>> > >> holger
>>> > >>
>>> > >>> Dave
>>> > >>>
>>> > >>>> On 9 Feb 2016, at 10:40, Dave Hunt <dhunt at mozilla.com <mailto:
>>> dhunt at mozilla.com>> wrote:
>>> > >>>>
>>> > >>>> I think this is a great idea! I have had approval to join you all
>>> during the sprint, so I?d be happy to write a blog post about how I came to
>>> pytest and what I?d like to work on during the week.
>>> > >>>>
>>> > >>>> Cheers,
>>> > >>>> Dave
>>> > >>>>
>>> > >>>>> On 8 Feb 2016, at 20:05, Brianna Laugher <
>>> brianna.laugher at gmail.com <mailto:brianna.laugher at gmail.com> <mailto:
>>> brianna.laugher at gmail.com <mailto:brianna.laugher at gmail.com>>> wrote:
>>> > >>>>>
>>> > >>>>> Heh, I had the exact same idea last night :)
>>> > >>>>>
>>> > >>>>> I was thinking
>>> > >>>>> 1) how did you get involved with pytest?
>>> > >>>>> 2) What is your favourite feature/plugin of pytest that is
>>> relatively unknown?
>>> > >>>>> 3) What are you planning to work on during the sprint?
>>> > >>>>>
>>> > >>>>> Cheers
>>> > >>>>> Brianna
>>> > >>>>>
>>> > >>>>> On 09/02/2016 6:04 AM, "Holger Krekel" <holger at merlinux.eu
>>> <mailto:holger at merlinux.eu> <mailto:holger at merlinux.eu <mailto:
>>> holger at merlinux.eu>>> wrote:
>>> > >>>>> What about if each of us who wants to participate writes a small
>>> blog (lacking a blog a pytest-dev) post of where he/she comes from, past
>>> core or plugin work for example, and main areas of interest for the sprint?
>>> > >>>>>
>>> > >>>>> We could publish them via updates every few days. Any takers?
>>> > >>>>> --
>>> > >>>>> Sent using mobile touch keys, increased chances for errors and
>>> misunderstandings. Enjoy!
>>> > >>>>> _______________________________________________
>>> > >>>>> pytest-dev mailing list
>>> > >>>>> pytest-dev at python.org <mailto:pytest-dev at python.org> <mailto:
>>> pytest-dev at python.org <mailto:pytest-dev at python.org>>
>>> > >>>>> https://mail.python.org/mailman/listinfo/pytest-dev <
>>> https://mail.python.org/mailman/listinfo/pytest-dev> <
>>> https://mail.python.org/mailman/listinfo/pytest-dev <
>>> https://mail.python.org/mailman/listinfo/pytest-dev>>
>>> > >>>>>
>>> > >>>>> _______________________________________________
>>> > >>>>> pytest-dev mailing list
>>> > >>>>> pytest-dev at python.org <mailto:pytest-dev at python.org> <mailto:
>>> pytest-dev at python.org <mailto:pytest-dev at python.org>>
>>> > >>>>> https://mail.python.org/mailman/listinfo/pytest-dev <
>>> https://mail.python.org/mailman/listinfo/pytest-dev>
>>> > >>>>
>>> > >>>
>>> > >>
>>> > >> --
>>> > >> about me:    http://holgerkrekel.net/about-me/ <
>>> http://holgerkrekel.net/about-me/>
>>> > >> contracting: http://merlinux.eu <http://merlinux.eu/>
>>> > >
>>> >
>>>
>>> --
>>> about me:    http://holgerkrekel.net/about-me/
>>> contracting: http://merlinux.eu
>>> _______________________________________________
>>> pytest-dev mailing list
>>> pytest-dev at python.org
>>> https://mail.python.org/mailman/listinfo/pytest-dev
>>>
>>
> --
> Sent using mobile touch keys, increased chances for errors and
> misunderstandings. Enjoy!
>



-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160213/cd5fdff6/attachment-0001.html>

From nicoddemus at gmail.com  Fri Feb 12 23:20:28 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Sat, 13 Feb 2016 04:20:28 +0000
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <CAPjwCjscXJ3=ji8MzunZd_Tc_z1JQx-BumqP_uoqn1z6gyv32Q@mail.gmail.com>
References: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>
 <CAPjwCjsH-ooSzQ4pTQKhq=14vAG9pasJmQurzbqWcGcX4cs8yQ@mail.gmail.com>
 <DFF0964C-990E-41C2-90E0-51F1C21223CD@mozilla.com>
 <A926C829-CB10-429D-9782-C96256271D0A@mozilla.com>
 <20160209140953.GH15751@merlinux.eu>
 <6857A31A-FD3E-434C-8F40-189FBAC5D88C@mozilla.com>
 <D36ADF22-B6B7-48DA-AA08-0AB7E33F44BA@mozilla.com>
 <20160211090955.GQ15751@merlinux.eu>
 <CA+RQFfeqTJ06dPCzXv-ZdKXXk4vRkWSvTS3fyt5y1J=oTt_=mg@mail.gmail.com>
 <1FF4AFBC-F983-4315-B9F0-0FE232C6097C@merlinux.eu>
 <CAPjwCjscXJ3=ji8MzunZd_Tc_z1JQx-BumqP_uoqn1z6gyv32Q@mail.gmail.com>
Message-ID: <CA+RQFffOB2VfmDbMQKkyTe99EqyC3PaRsZmBZH84mkoYetbtQw@mail.gmail.com>

On Sat, Feb 13, 2016 at 2:06 AM Brianna Laugher <brianna.laugher at gmail.com>
wrote:

> Your writing is great Bruno! If you wanted I would be happy to edit a
> draft though.
>

> On 12 February 2016 at 09:02, Holger Krekel <holger at merlinux.eu> wrote:
>
>> Your written English is pretty good so you feel youbare rather missing
>> practice in pronunciation? But when we did the hangout I wasn't aware of it
>> :)
>>
>
Thanks for the compliments! :)

I will setup a blog post about the sprint tomorrow, just have to remember
how to use Pelican. :)

Cheers,
Bruno.

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160213/92e999cb/attachment.html>

From nicoddemus at gmail.com  Sat Feb 13 09:35:18 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Sat, 13 Feb 2016 14:35:18 +0000
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <CA+RQFffOB2VfmDbMQKkyTe99EqyC3PaRsZmBZH84mkoYetbtQw@mail.gmail.com>
References: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>
 <CAPjwCjsH-ooSzQ4pTQKhq=14vAG9pasJmQurzbqWcGcX4cs8yQ@mail.gmail.com>
 <DFF0964C-990E-41C2-90E0-51F1C21223CD@mozilla.com>
 <A926C829-CB10-429D-9782-C96256271D0A@mozilla.com>
 <20160209140953.GH15751@merlinux.eu>
 <6857A31A-FD3E-434C-8F40-189FBAC5D88C@mozilla.com>
 <D36ADF22-B6B7-48DA-AA08-0AB7E33F44BA@mozilla.com>
 <20160211090955.GQ15751@merlinux.eu>
 <CA+RQFfeqTJ06dPCzXv-ZdKXXk4vRkWSvTS3fyt5y1J=oTt_=mg@mail.gmail.com>
 <1FF4AFBC-F983-4315-B9F0-0FE232C6097C@merlinux.eu>
 <CAPjwCjscXJ3=ji8MzunZd_Tc_z1JQx-BumqP_uoqn1z6gyv32Q@mail.gmail.com>
 <CA+RQFffOB2VfmDbMQKkyTe99EqyC3PaRsZmBZH84mkoYetbtQw@mail.gmail.com>
Message-ID: <CA+RQFfd-4ASRXcZvkAkFcB=tDX4ai4zxELtUMeUOKsQOzYGNmg@mail.gmail.com>

On Sat, Feb 13, 2016 at 2:19 AM Bruno Oliveira <nicoddemus at gmail.com> wrote:

> I will setup a blog post about the sprint tomorrow, just have to remember
> how to use Pelican.
>

Published a draft at: http://nicoddemus.github.io/drafts/pytest-2016-sprint

Feedback is welcome! :)

Cheers,
Bruno.

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160213/6ad329ad/attachment.html>

From holger at merlinux.eu  Sat Feb 13 11:14:35 2016
From: holger at merlinux.eu (holger krekel)
Date: Sat, 13 Feb 2016 16:14:35 +0000
Subject: [pytest-dev] release process feature/master merge
Message-ID: <20160213161435.GB26343@merlinux.eu>

Hi,

i suggest we move to the following git related procedure for doing
feature releases:

- merge from master to make sure all bugfixes are in
- release from feature, also tag the release
- merge feature into master which now becomes the new bugfix line

Currently for pytest-2.9 features was merged to master but not yet
released.  Meanwhile i tried to update the website to have a sprint-
banner to the indiegogo campaign and after merging to master i now
can't do it (unless i poke around with git where i'd easily produce
accidents :).  So i am hoping pytest-2.9 is not too far out but
also suggest to avoid this race condition with the above procedure.

holger

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From nicoddemus at gmail.com  Sat Feb 13 11:46:55 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Sat, 13 Feb 2016 16:46:55 +0000
Subject: [pytest-dev] release process feature/master merge
In-Reply-To: <20160213161435.GB26343@merlinux.eu>
References: <20160213161435.GB26343@merlinux.eu>
Message-ID: <CA+RQFffbVSGSEzmvr+kXu3Jk3GkjR=XE-Ega8dJB8ALYAyTWHA@mail.gmail.com>

Hi Holger,

On Sat, Feb 13, 2016 at 2:14 PM holger krekel <holger at merlinux.eu> wrote:

> Hi,
>
> i suggest we move to the following git related procedure for doing
> feature releases:
>
> - merge from master to make sure all bugfixes are in
> - release from feature, also tag the release
> - merge feature into master which now becomes the new bugfix line
>

I agree, it makes sense.



> So i am hoping pytest-2.9 is not too far out but
> also suggest to avoid this race condition with the above procedure.
>

I'm under the impression that 2.9 is meant to be released this week.

Cheers,
Bruno.


>
> holger
>
> --
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160213/e3bfa36f/attachment.html>

From holger at merlinux.eu  Sat Feb 13 12:02:31 2016
From: holger at merlinux.eu (holger krekel)
Date: Sat, 13 Feb 2016 17:02:31 +0000
Subject: [pytest-dev] release process feature/master merge
In-Reply-To: <CA+RQFffbVSGSEzmvr+kXu3Jk3GkjR=XE-Ega8dJB8ALYAyTWHA@mail.gmail.com>
References: <20160213161435.GB26343@merlinux.eu>
 <CA+RQFffbVSGSEzmvr+kXu3Jk3GkjR=XE-Ega8dJB8ALYAyTWHA@mail.gmail.com>
Message-ID: <20160213170231.GB15751@merlinux.eu>

On Sat, Feb 13, 2016 at 16:46 +0000, Bruno Oliveira wrote:
> Hi Holger,
> 
> On Sat, Feb 13, 2016 at 2:14 PM holger krekel <holger at merlinux.eu> wrote:
> 
> > Hi,
> >
> > i suggest we move to the following git related procedure for doing
> > feature releases:
> >
> > - merge from master to make sure all bugfixes are in
> > - release from feature, also tag the release
> > - merge feature into master which now becomes the new bugfix line
> >
> 
> I agree, it makes sense.
> 
> 
> 
> > So i am hoping pytest-2.9 is not too far out but
> > also suggest to avoid this race condition with the above procedure.
> >
> 
> I'm under the impression that 2.9 is meant to be released this week.

You mean this weekend or the coming couple of days?

I guess it's ok although if it drags any further i'd very much 
appreciate if someone could "backport" the doc changes such that we can
push it to pytest.org rather sooner -- after all it's about
getting some of the ~37K monthly users to the site to donate.

best,
holger


> Cheers,
> Bruno.
> 
> 
> >
> > holger
> >
> > --
> > about me:    http://holgerkrekel.net/about-me/
> > contracting: http://merlinux.eu
> > _______________________________________________
> > pytest-dev mailing list
> > pytest-dev at python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
> >

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From nicoddemus at gmail.com  Sat Feb 13 12:34:26 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Sat, 13 Feb 2016 17:34:26 +0000
Subject: [pytest-dev] release process feature/master merge
In-Reply-To: <20160213170231.GB15751@merlinux.eu>
References: <20160213161435.GB26343@merlinux.eu>
 <CA+RQFffbVSGSEzmvr+kXu3Jk3GkjR=XE-Ega8dJB8ALYAyTWHA@mail.gmail.com>
 <20160213170231.GB15751@merlinux.eu>
Message-ID: <CA+RQFfdqMVDO-xGXT-fUd+KiQqOrhAfFFx9iW144m3cCKgM7KQ@mail.gmail.com>

On Sat, Feb 13, 2016 at 3:02 PM holger krekel <holger at merlinux.eu> wrote:

> On Sat, Feb 13, 2016 at 16:46 +0000, Bruno Oliveira wrote:
> > I'm under the impression that 2.9 is meant to be released this week.
>
> You mean this weekend or the coming couple of days?
>

I was thinking the coming couple of days (say Thursday)... what do you
think Ronny?

Hmmm on the other hand it would be nice IMO to make a release candidate and
ask users to test it to get some field testing, so this might push the
release further in the week...

I guess it's ok although if it drags any further i'd very much
> appreciate if someone could "backport" the doc changes such that we can
> push it to pytest.org rather sooner -- after all it's about
> getting some of the ~37K monthly users to the site to donate.
>

Backporting the doc changes would mean cherry-picking the changes in a
branch over the 2.8.7 tag and making a 2.8.8 release... if 2.9.0 is not
released next week we can go with this plan.

Another option would be to copy just the relevant html files to the live
server... but that feels hackish. On the other hand is quick to do.

Bruno.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160213/86834bb3/attachment.html>

From nicoddemus at gmail.com  Sat Feb 13 12:54:13 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Sat, 13 Feb 2016 17:54:13 +0000
Subject: [pytest-dev] Redirect pytest.org over readthedocs
Message-ID: <CA+RQFffPy-5c_B1Lg4_9EoC5_ghgbtv1bKcObowE5T21vn9i=A@mail.gmail.com>

Hi guys,

I think the next step to complete the docs move to readthedocs is a server
side configuration
to redirect all requests from pytest.org to pytest.readthedocs.org... don't
know anything about the subject, but a quick google search suggests its
easy and quick to setup and test:

http://www.inmotionhosting.com/support/website/redirects/setting-up-a-301-permanent-redirect-via-htaccess

(yeah what a terrible website)

I understand it's just the matter of writing a .htaccess file in the
pytest.org folder with these contents:

RewriteEngine on
RewriteCond %{HTTP_HOST} ^pytest.org [NC,OR]
RewriteCond %{HTTP_HOST} ^https://pytest.org [NC]
RewriteRule ^(.*)$ https://pytest.readthedocs.org/en/$1 [L,R=301,NC]

I wanted to go over the list first in case I'm missing anything obvious,
also I'm wary of messing with the .htaccess site of 37k daily accesses and
I know there are people in the list who knows their way around linux
servers (The-Compiler for example). :)

Cheers,
Bruno.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160213/fec33587/attachment.html>

From holger at merlinux.eu  Sat Feb 13 12:54:34 2016
From: holger at merlinux.eu (holger krekel)
Date: Sat, 13 Feb 2016 17:54:34 +0000
Subject: [pytest-dev] release process feature/master merge
In-Reply-To: <CA+RQFfdqMVDO-xGXT-fUd+KiQqOrhAfFFx9iW144m3cCKgM7KQ@mail.gmail.com>
References: <20160213161435.GB26343@merlinux.eu>
 <CA+RQFffbVSGSEzmvr+kXu3Jk3GkjR=XE-Ega8dJB8ALYAyTWHA@mail.gmail.com>
 <20160213170231.GB15751@merlinux.eu>
 <CA+RQFfdqMVDO-xGXT-fUd+KiQqOrhAfFFx9iW144m3cCKgM7KQ@mail.gmail.com>
Message-ID: <20160213175434.GG15751@merlinux.eu>

On Sat, Feb 13, 2016 at 17:34 +0000, Bruno Oliveira wrote:
> On Sat, Feb 13, 2016 at 3:02 PM holger krekel <holger at merlinux.eu> wrote:
> 
> > On Sat, Feb 13, 2016 at 16:46 +0000, Bruno Oliveira wrote:
> > > I'm under the impression that 2.9 is meant to be released this week.
> >
> > You mean this weekend or the coming couple of days?
> >
> 
> I was thinking the coming couple of days (say Thursday)... what do you
> think Ronny?
> 
> Hmmm on the other hand it would be nice IMO to make a release candidate and
> ask users to test it to get some field testing, so this might push the
> release further in the week...
> 
> I guess it's ok although if it drags any further i'd very much
> > appreciate if someone could "backport" the doc changes such that we can
> > push it to pytest.org rather sooner -- after all it's about
> > getting some of the ~37K monthly users to the site to donate.
> >
> 
> Backporting the doc changes would mean cherry-picking the changes in a
> branch over the 2.8.7 tag and making a 2.8.8 release... if 2.9.0 is not
> released next week we can go with this plan.
> 
> Another option would be to copy just the relevant html files to the live
> server... but that feels hackish. On the other hand is quick to do.

can you do the latter really?  You'd have to transfer all html files
because they have the generated link at the top of each page.

Seems easier to transfer current master's _template/* and annouce/* onto the
2.8.7 tag in a new branch and generate and push docs from there.
Could you do that?  With a bit of git-fu i suspect it's just a couple
of minutes ... not for me, though, and i have two children to care 
for currently :)

holger


> Bruno.

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From holger at merlinux.eu  Sat Feb 13 12:59:26 2016
From: holger at merlinux.eu (holger krekel)
Date: Sat, 13 Feb 2016 17:59:26 +0000
Subject: [pytest-dev] Redirect pytest.org over readthedocs
In-Reply-To: <CA+RQFffPy-5c_B1Lg4_9EoC5_ghgbtv1bKcObowE5T21vn9i=A@mail.gmail.com>
References: <CA+RQFffPy-5c_B1Lg4_9EoC5_ghgbtv1bKcObowE5T21vn9i=A@mail.gmail.com>
Message-ID: <20160213175926.GH15751@merlinux.eu>

On Sat, Feb 13, 2016 at 17:54 +0000, Bruno Oliveira wrote:
> Hi guys,
> 
> I think the next step to complete the docs move to readthedocs is a server
> side configuration
> to redirect all requests from pytest.org to pytest.readthedocs.org... don't
> know anything about the subject, but a quick google search suggests its
> easy and quick to setup and test:
> 
> http://www.inmotionhosting.com/support/website/redirects/setting-up-a-301-permanent-redirect-via-htaccess
> 
> (yeah what a terrible website)
> 
> I understand it's just the matter of writing a .htaccess file in the
> pytest.org folder with these contents:
> 
> RewriteEngine on
> RewriteCond %{HTTP_HOST} ^pytest.org [NC,OR]
> RewriteCond %{HTTP_HOST} ^https://pytest.org [NC]
> RewriteRule ^(.*)$ https://pytest.readthedocs.org/en/$1 [L,R=301,NC]

pytest.org is using nginx, however.

> I wanted to go over the list first in case I'm missing anything obvious,
> also I'm wary of messing with the .htaccess site of 37k daily accesses and
> I know there are people in the list who knows their way around linux
> servers (The-Compiler for example). :)

FWIW I just granted pytest-dev sudo rights for the time being.
Use with care, please.

holger

> Cheers,
> Bruno.

> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev


-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From holger at merlinux.eu  Sat Feb 13 13:07:08 2016
From: holger at merlinux.eu (holger krekel)
Date: Sat, 13 Feb 2016 18:07:08 +0000
Subject: [pytest-dev] Redirect pytest.org over readthedocs
In-Reply-To: <CA+RQFffPy-5c_B1Lg4_9EoC5_ghgbtv1bKcObowE5T21vn9i=A@mail.gmail.com>
References: <CA+RQFffPy-5c_B1Lg4_9EoC5_ghgbtv1bKcObowE5T21vn9i=A@mail.gmail.com>
Message-ID: <20160213180708.GI15751@merlinux.eu>

On Sat, Feb 13, 2016 at 17:54 +0000, Bruno Oliveira wrote:

> 
> I think the next step to complete the docs move to readthedocs is a server
> side configuration
> to redirect all requests from pytest.org to pytest.readthedocs.org... don't
> know anything about the subject, but a quick google search suggests its
> easy and quick to setup and test:
> 
> http://www.inmotionhosting.com/support/website/redirects/setting-up-a-301-permanent-redirect-via-htaccess
> 
> (yeah what a terrible website)
> 
> I understand it's just the matter of writing a .htaccess file in the
> pytest.org folder with these contents:
> 
> RewriteEngine on
> RewriteCond %{HTTP_HOST} ^pytest.org [NC,OR]
> RewriteCond %{HTTP_HOST} ^https://pytest.org [NC]
> RewriteRule ^(.*)$ https://pytest.readthedocs.org/en/$1 [L,R=301,NC]
> 
> I wanted to go over the list first in case I'm missing anything obvious,
> also I'm wary of messing with the .htaccess site of 37k daily accesses and

monthly accesses btw.  Let's move back quickly, though, if there are any problems.
So far i have not heart many complaints about pytest.org not working apart
from the recent ssl hickup which should be automated now with letsencrypt.

holger


> I know there are people in the list who knows their way around linux
> servers (The-Compiler for example). :)
> 
> Cheers,
> Bruno.

> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev


-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From nicoddemus at gmail.com  Sat Feb 13 13:13:25 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Sat, 13 Feb 2016 18:13:25 +0000
Subject: [pytest-dev] release process feature/master merge
In-Reply-To: <20160213175434.GG15751@merlinux.eu>
References: <20160213161435.GB26343@merlinux.eu>
 <CA+RQFffbVSGSEzmvr+kXu3Jk3GkjR=XE-Ega8dJB8ALYAyTWHA@mail.gmail.com>
 <20160213170231.GB15751@merlinux.eu>
 <CA+RQFfdqMVDO-xGXT-fUd+KiQqOrhAfFFx9iW144m3cCKgM7KQ@mail.gmail.com>
 <20160213175434.GG15751@merlinux.eu>
Message-ID: <CA+RQFfdHpXNU5KchPZbz6hChTtAvVP6pnm5r_G2DUrog2ph61g@mail.gmail.com>

On Sat, Feb 13, 2016 at 3:54 PM holger krekel <holger at merlinux.eu> wrote:

> can you do the latter really?  You'd have to transfer all html files
> because they have the generated link at the top of each page.
>
> Seems easier to transfer current master's _template/* and annouce/* onto
> the
> 2.8.7 tag in a new branch and generate and push docs from there.
> Could you do that?  With a bit of git-fu i suspect it's just a couple
> of minutes ... not for me, though, and i have two children to care
> for currently :)
>

Sure, and then throw away the branch. I will get to it later or tomorrow,
as I have to leave just now. :)

Bruno.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160213/728d0863/attachment.html>

From holger at merlinux.eu  Sat Feb 13 14:06:18 2016
From: holger at merlinux.eu (Holger Krekel)
Date: Sat, 13 Feb 2016 20:06:18 +0100
Subject: [pytest-dev] release process feature/master merge
In-Reply-To: <56BF7E50.7060101@ronnypfannschmidt.de>
References: <20160213161435.GB26343@merlinux.eu>
 <CA+RQFffbVSGSEzmvr+kXu3Jk3GkjR=XE-Ega8dJB8ALYAyTWHA@mail.gmail.com>
 <20160213170231.GB15751@merlinux.eu>
 <CA+RQFfdqMVDO-xGXT-fUd+KiQqOrhAfFFx9iW144m3cCKgM7KQ@mail.gmail.com>
 <20160213175434.GG15751@merlinux.eu>
 <CA+RQFfdHpXNU5KchPZbz6hChTtAvVP6pnm5r_G2DUrog2ph61g@mail.gmail.com>
 <56BF7E50.7060101@ronnypfannschmidt.de>
Message-ID: <E0A451F4-D98B-4421-A898-6784104C9443@merlinux.eu>

Cool, thank youand Enjoy your weekend as well! 

On February 13, 2016 8:04:48 PM GMT+01:00, Ronny Pfannschmidt <ich at ronnypfannschmidt.de> wrote:
>HI all,
>
>since the issue is my mistake to begin with, i just did a backport +
>upload of the changes and did put them into a branch at my repo
>next step is updating the docs on the release process
>
>enjoy the weekend :)
>
>-- Ronny
>
>
>
>Am 13.02.2016 um 19:13 schrieb Bruno Oliveira:
>>
>> On Sat, Feb 13, 2016 at 3:54 PM holger krekel <holger at merlinux.eu
>> <mailto:holger at merlinux.eu>> wrote:
>>
>>     can you do the latter really?  You'd have to transfer all html
>files
>>     because they have the generated link at the top of each page.
>>
>>     Seems easier to transfer current master's _template/* and
>>     annouce/* onto the
>>     2.8.7 tag in a new branch and generate and push docs from there.
>>     Could you do that?  With a bit of git-fu i suspect it's just a
>couple
>>     of minutes ... not for me, though, and i have two children to
>care
>>     for currently :)
>>
>>
>> Sure, and then throw away the branch. I will get to it later or
>> tomorrow, as I have to leave just now. :)
>>
>> Bruno.
>>
>>
>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev

-- 
Sent using mobile touch keys, increased chances for errors and misunderstandings. Enjoy! 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160213/d31f2b80/attachment.html>

From brianna.laugher at gmail.com  Sat Feb 13 16:56:58 2016
From: brianna.laugher at gmail.com (Brianna Laugher)
Date: Sun, 14 Feb 2016 08:56:58 +1100
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <CA+RQFfd-4ASRXcZvkAkFcB=tDX4ai4zxELtUMeUOKsQOzYGNmg@mail.gmail.com>
References: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>
 <CAPjwCjsH-ooSzQ4pTQKhq=14vAG9pasJmQurzbqWcGcX4cs8yQ@mail.gmail.com>
 <DFF0964C-990E-41C2-90E0-51F1C21223CD@mozilla.com>
 <A926C829-CB10-429D-9782-C96256271D0A@mozilla.com>
 <20160209140953.GH15751@merlinux.eu>
 <6857A31A-FD3E-434C-8F40-189FBAC5D88C@mozilla.com>
 <D36ADF22-B6B7-48DA-AA08-0AB7E33F44BA@mozilla.com>
 <20160211090955.GQ15751@merlinux.eu>
 <CA+RQFfeqTJ06dPCzXv-ZdKXXk4vRkWSvTS3fyt5y1J=oTt_=mg@mail.gmail.com>
 <1FF4AFBC-F983-4315-B9F0-0FE232C6097C@merlinux.eu>
 <CAPjwCjscXJ3=ji8MzunZd_Tc_z1JQx-BumqP_uoqn1z6gyv32Q@mail.gmail.com>
 <CA+RQFffOB2VfmDbMQKkyTe99EqyC3PaRsZmBZH84mkoYetbtQw@mail.gmail.com>
 <CA+RQFfd-4ASRXcZvkAkFcB=tDX4ai4zxELtUMeUOKsQOzYGNmg@mail.gmail.com>
Message-ID: <CAPjwCjucygD5QCdiGzG+XO0WYRfYfSag9iukTpHLR9QDCHQDdA@mail.gmail.com>

Hey,

Well your post looks good, but you don't talk very much about your
contributions to pytest, which are many! At the moment the reader would
have no idea you are one of the most active contributors!
Maybe you could expand it a bit and list some of the features you have
worked on, talk about the move to github, or a particularly annoying bug
you have fixed?

Also maybe you could mention what you hope to do at the sprint?

Cheers
Brianna
On 14/02/2016 1:35 AM, "Bruno Oliveira" <nicoddemus at gmail.com> wrote:

> On Sat, Feb 13, 2016 at 2:19 AM Bruno Oliveira <nicoddemus at gmail.com>
> wrote:
>
>> I will setup a blog post about the sprint tomorrow, just have to remember
>> how to use Pelican.
>>
>
> Published a draft at:
> http://nicoddemus.github.io/drafts/pytest-2016-sprint
>
> Feedback is welcome! :)
>
> Cheers,
> Bruno.
>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160214/73508c20/attachment.html>

From nicoddemus at gmail.com  Sat Feb 13 23:02:32 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Sun, 14 Feb 2016 04:02:32 +0000
Subject: [pytest-dev] Redirect pytest.org over readthedocs
In-Reply-To: <20160213180708.GI15751@merlinux.eu>
References: <CA+RQFffPy-5c_B1Lg4_9EoC5_ghgbtv1bKcObowE5T21vn9i=A@mail.gmail.com>
 <20160213180708.GI15751@merlinux.eu>
Message-ID: <CA+RQFff-mG5iTGdsHg+2D3Cvtk7prrm6W-BZpjZ50BkHojY0+A@mail.gmail.com>

On Sat, Feb 13, 2016 at 4:07 PM holger krekel <holger at merlinux.eu> wrote:

> Let's move back quickly, though, if there are any problems.
> So far i have not heart many complaints about pytest.org not working apart
> from the recent ssl hickup which should be automated now with letsencrypt.
>

Agreed!

Thanks, didn't know the server uses nginx. I poked around a little, and we
already have redirects in `/etc/nginx/sites-enabled/pytest.org.conf`:

    location @rewrites {
        rewrite ^(/)?$ http://pytest.org/latest/;
        rewrite ^/en/latest/(.*) http://pytest.org/latest/$1;
        rewrite ^/(assert.*)$ http://pytest.org/latest/$1;
    }

Would just change those rewrites to docs.pytest.org (and the variants
there) do the trick? Any help here is appreciated.

*Anyway*, IMHO we shouldn't make any redirect before releasing 2.9. The
recent doc changes are not available on pytest.readthedocs.org yet because
we copied over the files manually. Btw thanks Ronny again for stepping in.

Cheers,
Bruno.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160214/85202bac/attachment-0001.html>

From alexamici at gmail.com  Sun Feb 14 10:23:32 2016
From: alexamici at gmail.com (Alessandro Amici)
Date: Sun, 14 Feb 2016 15:23:32 +0000
Subject: [pytest-dev] Announce pytest-wish a local search engine for code
Message-ID: <CACnxfA9gOBTSq_0YT4x3h3JVamrKLsCkQBN7WUNjmhoqqU=HAA@mail.gmail.com>

Hello everybody out there using pytest,

last year a colleague of mine and I came up with the idea of using tests
for searching code that implements a particular feature.

As I didn't find anything similar on the internet I started writing a
pytest plugin that helps doing just that and I'm now ready to release the
first beta of pytest-wish:

https://github.com/alexamici/pytest-wish

See the 2 minutes hands-on overview for how it works:

https://pytest-wish.readthedocs.org/en/stable/quickstart.html

We are using pytest-wish at my company with some success and I consider it
feature complete for a 1.0 release. OTOH the documentation is lagging and
it is my top priority right now.

I'd like any feedback on things people like/dislike in the approach.

Thanks,
Alessandro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160214/2ca28f65/attachment.html>

From nicoddemus at gmail.com  Sun Feb 14 11:52:53 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Sun, 14 Feb 2016 16:52:53 +0000
Subject: [pytest-dev] Announce pytest-wish a local search engine for code
In-Reply-To: <CACnxfA9gOBTSq_0YT4x3h3JVamrKLsCkQBN7WUNjmhoqqU=HAA@mail.gmail.com>
References: <CACnxfA9gOBTSq_0YT4x3h3JVamrKLsCkQBN7WUNjmhoqqU=HAA@mail.gmail.com>
Message-ID: <CA+RQFfc_Q_SH4p60HywNXcS3egdepP=cU6cWCR5i04xv7ymfkw@mail.gmail.com>

On Sun, Feb 14, 2016 at 1:23 PM Alessandro Amici <alexamici at gmail.com>
wrote:

> Hello everybody out there using pytest,
>
> last year a colleague of mine and I came up with the idea of using tests
> for searching code that implements a particular feature.
>
> As I didn't find anything similar on the internet I started writing a
> pytest plugin that helps doing just that and I'm now ready to release the
> first beta of pytest-wish:
>
> https://github.com/alexamici/pytest-wish
>

Hi Alessandro,

This is a very interesting idea, I will certainly try it out.

Also, congratulations on working on the plugin such thoroughly, with
documentation, CI, etc. This is always appreciated by the community.

Cheers,
Bruno.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160214/deb9032c/attachment.html>

From opensource at ronnypfannschmidt.de  Sun Feb 14 18:06:33 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Mon, 15 Feb 2016 00:06:33 +0100
Subject: [pytest-dev] [Proposal] adapting the Collective Code Construction
 Contract (which includes a switch to a weak share-alike license and limits
 branching models)
Message-ID: <56C10879.5030302@ronnypfannschmidt.de>

Hi everyone,

in the last few weeks i researched the topic of Code of Conducts,
i found many of them lacking, however the zeromq model strikes me as
something designed much better

The contract is described here: http://rfc.zeromq.org/spec:22

A first point in that contract does look like a problem,
which is the insistence on a share-alike license.

After a reading i am under the strong impression that the MPL is
perfectly fine for the purposes and usage of py.test,
the main question is if our direct users (and/or their managers/law experts)
can be helped to arrive at that conclusion as well.


A second point that does look problematic is the limitation in branching
models,
however after poking Pieter Hintjens on the reason he promptly pointed me to

http://zguide.zeromq.org/page:all#Git-Branches-Considered-Harmful

and

http://hintjens.com/blog:106

I found myself agreeing with those 2 items, as well as a lot of the
followup of the zguide.

best, Ronny

From me at the-compiler.org  Mon Feb 15 00:56:21 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Mon, 15 Feb 2016 06:56:21 +0100
Subject: [pytest-dev] [Proposal] adapting the Collective Code
 Construction Contract (which includes a switch to a weak share-alike
 license and limits branching models)
In-Reply-To: <56C10879.5030302@ronnypfannschmidt.de>
References: <56C10879.5030302@ronnypfannschmidt.de>
Message-ID: <20160215055621.GA27155@tonks>

* Ronny Pfannschmidt <opensource at ronnypfannschmidt.de> [2016-02-15 00:06:33 +0100]:
> Hi everyone,
> 
> in the last few weeks i researched the topic of Code of Conducts,
> i found many of them lacking, however the zeromq model strikes me as
> something designed much better
> 
> The contract is described here: http://rfc.zeromq.org/spec:22

That doesn't look like a code of conduct at all.

> A first point in that contract does look like a problem,
> which is the insistence on a share-alike license.
> 
> After a reading i am under the strong impression that the MPL is
> perfectly fine for the purposes and usage of py.test,
> the main question is if our direct users (and/or their managers/law experts)
> can be helped to arrive at that conclusion as well.

Good luck relicensing a codebase with 140 contributors. What's the
point?

> A second point that does look problematic is the limitation in branching
> models,
> however after poking Pieter Hintjens on the reason he promptly pointed me to
> 
> http://zguide.zeromq.org/page:all#Git-Branches-Considered-Harmful
> 
> and
> 
> http://hintjens.com/blog:106

Merging without looking at the CI and without code-review... What?

I'm sorry, but that post is full of bullshit from my POV:

    Maintainers inherently strive to remain important in their
    project. If they can keep out potential competitors by delaying
    and blocking their patches, they will.

    Mediocre contributors who make patches that no-one notices or
    cares about. - PM: we get a flamewar and everyone wonders why the
    community is so hostile.

    Trollish contributors who ignore the rules, and who write toxic
    patches. - we get a flamewar which troll wins by sheer force of
    argument. Community explodes in fight-or-flee emotions. Bad
    patches get pushed through.

I... don't have any words.

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160215/af7f59b8/attachment.sig>

From florian.schulze at gmx.net  Mon Feb 15 03:38:38 2016
From: florian.schulze at gmx.net (Florian Schulze)
Date: Mon, 15 Feb 2016 09:38:38 +0100
Subject: [pytest-dev] [Proposal] adapting the Collective Code
 Construction Contract (which includes a switch to a weak share-alike
 license and limits branching models)
In-Reply-To: <56C10879.5030302@ronnypfannschmidt.de>
References: <56C10879.5030302@ronnypfannschmidt.de>
Message-ID: <47B3DD8A-F12B-44D5-9D0D-1E75B91A24D1@gmx.net>

> in the last few weeks i researched the topic of Code of Conducts,
> i found many of them lacking, however the zeromq model strikes me as
> something designed much better
>
> The contract is described here: http://rfc.zeromq.org/spec:22
>
> A first point in that contract does look like a problem,
> which is the insistence on a share-alike license.
>
> After a reading i am under the strong impression that the MPL is
> perfectly fine for the purposes and usage of py.test,
> the main question is if our direct users (and/or their managers/law 
> experts)
> can be helped to arrive at that conclusion as well.

I just recently learned that viral licenses like GPL can be a huge pain. 
They also did a lot of good though, allowing us to still have free 
choice of software on most routers for example. But especially for 
things like py.test, companies tend to avoid contributing or extending 
for understandable reasons. A very permissive license is much better for 
that imo.

> A second point that does look problematic is the limitation in 
> branching
> models,
> however after poking Pieter Hintjens on the reason he promptly pointed 
> me to
>
> http://zguide.zeromq.org/page:all#Git-Branches-Considered-Harmful

This is the only thing I agree with, feature branches belong to forks. 
The main repository should only contain released and agreed on upcoming 
stuff.

> http://hintjens.com/blog:106
>
> I found myself agreeing with those 2 items, as well as a lot of the
> followup of the zguide.

I don't like this approach at all.

Regards,
Florian Schulze

From opensource at ronnypfannschmidt.de  Mon Feb 15 08:30:25 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Mon, 15 Feb 2016 14:30:25 +0100
Subject: [pytest-dev] [Proposal] adapting the Collective Code
 Construction Contract (which includes a switch to a weak share-alike
 license and limits branching models)
In-Reply-To: <47B3DD8A-F12B-44D5-9D0D-1E75B91A24D1@gmx.net>
References: <56C10879.5030302@ronnypfannschmidt.de>
 <47B3DD8A-F12B-44D5-9D0D-1E75B91A24D1@gmx.net>
Message-ID: <56C1D2F1.6020500@ronnypfannschmidt.de>

Hi,

please see below

Am 15.02.2016 um 09:38 schrieb Florian Schulze:
>> in the last few weeks i researched the topic of Code of Conducts,
>> i found many of them lacking, however the zeromq model strikes me as
>> something designed much better
>>
>> The contract is described here: http://rfc.zeromq.org/spec:22
>>
>> A first point in that contract does look like a problem,
>> which is the insistence on a share-alike license.
>>
>> After a reading i am under the strong impression that the MPL is
>> perfectly fine for the purposes and usage of py.test,
>> the main question is if our direct users (and/or their managers/law
>> experts)
>> can be helped to arrive at that conclusion as well.
>
> I just recently learned that viral licenses like GPL can be a huge
> pain. They also did a lot of good though, allowing us to still have
> free choice of software on most routers for example. But especially
> for things like py.test, companies tend to avoid contributing or
> extending for understandable reasons. A very permissive license is
> much better for that imo.

my understanding is, MPL is non-viral, it does not infect other code, it
only applies to the code itself and vendor-ed copies.
in Fact its per design even weaker than LGPL, since it allows inclusion
without viral extension.
>
>> A second point that does look problematic is the limitation in branching
>> models,
>> however after poking Pieter Hintjens on the reason he promptly
>> pointed me to
>>
>> http://zguide.zeromq.org/page:all#Git-Branches-Considered-Harmful
>
> This is the only thing I agree with, feature branches belong to forks.
> The main repository should only contain released and agreed on
> upcoming stuff.
>
>> http://hintjens.com/blog:106
>>
>> I found myself agreeing with those 2 items, as well as a lot of the
>> followup of the zguide.
>
> I don't like this approach at all.
can you pinpoint what about the approach strikes you?
i find it practical, since upon reflection i realized it pretty
much works effectively against various of my own biases/mistakes and
mis-behaviours.

In particular wrt value judgments.

would it help if i created a more detailed blog post about my findings?

Regards, Ronny

>
> Regards,
> Florian Schulze


From alexamici at gmail.com  Mon Feb 15 09:53:16 2016
From: alexamici at gmail.com (Alessandro Amici)
Date: Mon, 15 Feb 2016 14:53:16 +0000
Subject: [pytest-dev] Announce pytest-wish a local search engine for code
In-Reply-To: <CA+RQFfc_Q_SH4p60HywNXcS3egdepP=cU6cWCR5i04xv7ymfkw@mail.gmail.com>
References: <CACnxfA9gOBTSq_0YT4x3h3JVamrKLsCkQBN7WUNjmhoqqU=HAA@mail.gmail.com>
 <CA+RQFfc_Q_SH4p60HywNXcS3egdepP=cU6cWCR5i04xv7ymfkw@mail.gmail.com>
Message-ID: <CACnxfA94KwkOzRQdDwBkc=pH7B7vjYTqYH1vLDWYWSUCi=qy=A@mail.gmail.com>

Bruno,

On Sun, 14 Feb 2016 at 17:53 Bruno Oliveira <nicoddemus at gmail.com> wrote:

> This is a very interesting idea, I will certainly try it out.
>

I'm somewhat surprised that I couldn't find anything similar, have anybody
heard of attempts to use tests to search code instead of the usual
keyword+metadata?

Also, congratulations on working on the plugin such thoroughly, with
> documentation, CI, etc. This is always appreciated by the community.
>

And your kind words are appreciated as well :)

Alessandro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160215/c4960d22/attachment-0001.html>

From florian.schulze at gmx.net  Mon Feb 15 11:45:05 2016
From: florian.schulze at gmx.net (Florian Schulze)
Date: Mon, 15 Feb 2016 17:45:05 +0100
Subject: [pytest-dev] [Proposal] adapting the Collective Code
 Construction Contract (which includes a switch to a weak share-alike
 license and limits branching models)
In-Reply-To: <56C1D2F1.6020500@ronnypfannschmidt.de>
References: <56C10879.5030302@ronnypfannschmidt.de>
 <47B3DD8A-F12B-44D5-9D0D-1E75B91A24D1@gmx.net>
 <56C1D2F1.6020500@ronnypfannschmidt.de>
Message-ID: <157753B2-62BA-4C74-8D4C-71BEF7EDD57D@gmx.net>



>>> The contract is described here: http://rfc.zeromq.org/spec:22
>>
>> I just recently learned that viral licenses like GPL can be a huge
>> pain. They also did a lot of good though, allowing us to still have
>> free choice of software on most routers for example. But especially
>> for things like py.test, companies tend to avoid contributing or
>> extending for understandable reasons. A very permissive license is
>> much better for that imo.
>
> my understanding is, MPL is non-viral, it does not infect other code, 
> it
> only applies to the code itself and vendor-ed copies.
> in Fact its per design even weaker than LGPL, since it allows 
> inclusion
> without viral extension.

The first thing I see in the above link is the License which directly 
refers to the GPL.

>>> http://hintjens.com/blog:106
>>>
>>> I found myself agreeing with those 2 items, as well as a lot of the
>>> followup of the zguide.
>>
>> I don't like this approach at all.
> can you pinpoint what about the approach strikes you?
> i find it practical, since upon reflection i realized it pretty
> much works effectively against various of my own biases/mistakes and
> mis-behaviours.
>
> In particular wrt value judgments.
>
> would it help if i created a more detailed blog post about my 
> findings?

The point about value judgments might be right. But just merging every 
pull request without review just creates more work. Personally in my 
projects, I look at test outcomes and do a quick review of what is being 
done. Based on that I decide whether I merge and just fix any problems 
myself, or whether I ask for a followup.

Regards,
Florian Schulze

From andreas at pelme.se  Mon Feb 15 16:43:31 2016
From: andreas at pelme.se (Andreas Pelme)
Date: Mon, 15 Feb 2016 22:43:31 +0100
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <CAPjwCjscXJ3=ji8MzunZd_Tc_z1JQx-BumqP_uoqn1z6gyv32Q@mail.gmail.com>
References: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>
 <CAPjwCjsH-ooSzQ4pTQKhq=14vAG9pasJmQurzbqWcGcX4cs8yQ@mail.gmail.com>
 <DFF0964C-990E-41C2-90E0-51F1C21223CD@mozilla.com>
 <A926C829-CB10-429D-9782-C96256271D0A@mozilla.com>
 <20160209140953.GH15751@merlinux.eu>
 <6857A31A-FD3E-434C-8F40-189FBAC5D88C@mozilla.com>
 <D36ADF22-B6B7-48DA-AA08-0AB7E33F44BA@mozilla.com>
 <20160211090955.GQ15751@merlinux.eu>
 <CA+RQFfeqTJ06dPCzXv-ZdKXXk4vRkWSvTS3fyt5y1J=oTt_=mg@mail.gmail.com>
 <1FF4AFBC-F983-4315-B9F0-0FE232C6097C@merlinux.eu>
 <CAPjwCjscXJ3=ji8MzunZd_Tc_z1JQx-BumqP_uoqn1z6gyv32Q@mail.gmail.com>
Message-ID: <7E9CA161-D07E-4D8D-B645-3A8E25275BAB@pelme.se>


> On 13 feb. 2016, at 05:06, Brianna Laugher <brianna.laugher at gmail.com> wrote:
> 
> Andreas, how about you? You could speak about your company's support too :)

I?ve put together a post at

http://andreas.pelme.se/pytest-sprint.html

I don?t really have a draft mode on my blog, but I?m quite sure it does not receive any traffic anyways. Feedback on the post is very welcome :)

Cheers,
Andreas


From brianna.laugher at gmail.com  Tue Feb 16 06:17:20 2016
From: brianna.laugher at gmail.com (Brianna Laugher)
Date: Tue, 16 Feb 2016 22:17:20 +1100
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <CA+RQFffOB2VfmDbMQKkyTe99EqyC3PaRsZmBZH84mkoYetbtQw@mail.gmail.com>
References: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>
 <CAPjwCjsH-ooSzQ4pTQKhq=14vAG9pasJmQurzbqWcGcX4cs8yQ@mail.gmail.com>
 <DFF0964C-990E-41C2-90E0-51F1C21223CD@mozilla.com>
 <A926C829-CB10-429D-9782-C96256271D0A@mozilla.com>
 <20160209140953.GH15751@merlinux.eu>
 <6857A31A-FD3E-434C-8F40-189FBAC5D88C@mozilla.com>
 <D36ADF22-B6B7-48DA-AA08-0AB7E33F44BA@mozilla.com>
 <20160211090955.GQ15751@merlinux.eu>
 <CA+RQFfeqTJ06dPCzXv-ZdKXXk4vRkWSvTS3fyt5y1J=oTt_=mg@mail.gmail.com>
 <1FF4AFBC-F983-4315-B9F0-0FE232C6097C@merlinux.eu>
 <CAPjwCjscXJ3=ji8MzunZd_Tc_z1JQx-BumqP_uoqn1z6gyv32Q@mail.gmail.com>
 <CA+RQFffOB2VfmDbMQKkyTe99EqyC3PaRsZmBZH84mkoYetbtQw@mail.gmail.com>
Message-ID: <CAPjwCjucAgU=Z=V8wQdcM53eaAkfyrydwHy-tJDCCJ9Vp+bcDA@mail.gmail.com>

I just sent out an indiegogo update with a link to Bruno's post. Thanks
Bruno :D

Brianna

On 13 February 2016 at 15:20, Bruno Oliveira <nicoddemus at gmail.com> wrote:

>
> On Sat, Feb 13, 2016 at 2:06 AM Brianna Laugher <brianna.laugher at gmail.com>
> wrote:
>
>> Your writing is great Bruno! If you wanted I would be happy to edit a
>> draft though.
>>
>
>> On 12 February 2016 at 09:02, Holger Krekel <holger at merlinux.eu> wrote:
>>
>>> Your written English is pretty good so you feel youbare rather missing
>>> practice in pronunciation? But when we did the hangout I wasn't aware of it
>>> :)
>>>
>>
> Thanks for the compliments! :)
>
> I will setup a blog post about the sprint tomorrow, just have to remember
> how to use Pelican. :)
>
> Cheers,
> Bruno.
>
>>


-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160216/33af7d17/attachment.html>

From brianna.laugher at gmail.com  Tue Feb 16 06:24:26 2016
From: brianna.laugher at gmail.com (Brianna Laugher)
Date: Tue, 16 Feb 2016 22:24:26 +1100
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <7E9CA161-D07E-4D8D-B645-3A8E25275BAB@pelme.se>
References: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>
 <CAPjwCjsH-ooSzQ4pTQKhq=14vAG9pasJmQurzbqWcGcX4cs8yQ@mail.gmail.com>
 <DFF0964C-990E-41C2-90E0-51F1C21223CD@mozilla.com>
 <A926C829-CB10-429D-9782-C96256271D0A@mozilla.com>
 <20160209140953.GH15751@merlinux.eu>
 <6857A31A-FD3E-434C-8F40-189FBAC5D88C@mozilla.com>
 <D36ADF22-B6B7-48DA-AA08-0AB7E33F44BA@mozilla.com>
 <20160211090955.GQ15751@merlinux.eu>
 <CA+RQFfeqTJ06dPCzXv-ZdKXXk4vRkWSvTS3fyt5y1J=oTt_=mg@mail.gmail.com>
 <1FF4AFBC-F983-4315-B9F0-0FE232C6097C@merlinux.eu>
 <CAPjwCjscXJ3=ji8MzunZd_Tc_z1JQx-BumqP_uoqn1z6gyv32Q@mail.gmail.com>
 <7E9CA161-D07E-4D8D-B645-3A8E25275BAB@pelme.se>
Message-ID: <CAPjwCjufkfznttRg_TakoDU5XLGsJAJh-C1U8axgO502b_4OUw@mail.gmail.com>

That's a great post, I look forward to that pytest blog too ;)

I suggest we wait a few days to post another IGG update, they recommend to
do updates at least every 5 days, but it's nice if the total donated gets a
bit bigger between each update :)

Brianna

On 16 February 2016 at 08:43, Andreas Pelme <andreas at pelme.se> wrote:

>
> > On 13 feb. 2016, at 05:06, Brianna Laugher <brianna.laugher at gmail.com>
> wrote:
> >
> > Andreas, how about you? You could speak about your company's support too
> :)
>
> I?ve put together a post at
>
> http://andreas.pelme.se/pytest-sprint.html
>
> I don?t really have a draft mode on my blog, but I?m quite sure it does
> not receive any traffic anyways. Feedback on the post is very welcome :)
>
> Cheers,
> Andreas
>
>


-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160216/8c9b8d82/attachment.html>

From raphael at hackebrot.de  Tue Feb 16 09:27:57 2016
From: raphael at hackebrot.de (Raphael Pierzina)
Date: Tue, 16 Feb 2016 14:27:57 +0000
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <CA+RQFfeqTJ06dPCzXv-ZdKXXk4vRkWSvTS3fyt5y1J=oTt_=mg@mail.gmail.com>
References: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>
 <CAPjwCjsH-ooSzQ4pTQKhq=14vAG9pasJmQurzbqWcGcX4cs8yQ@mail.gmail.com>
 <DFF0964C-990E-41C2-90E0-51F1C21223CD@mozilla.com>
 <A926C829-CB10-429D-9782-C96256271D0A@mozilla.com>
 <20160209140953.GH15751@merlinux.eu>
 <6857A31A-FD3E-434C-8F40-189FBAC5D88C@mozilla.com>
 <D36ADF22-B6B7-48DA-AA08-0AB7E33F44BA@mozilla.com>
 <20160211090955.GQ15751@merlinux.eu>
 <CA+RQFfeqTJ06dPCzXv-ZdKXXk4vRkWSvTS3fyt5y1J=oTt_=mg@mail.gmail.com>
Message-ID: <12D72D98-68DC-479A-B95C-76900D50A9E3@hackebrot.de>

Hi all,

I think you should go for it, Bruno! :-)

You have been really active in the past months which makes you a good candidate to speak about ongoing topics, I think.

I would like to talk with Brian on the Podcast about the sprint - however I am not nearly as involved in core-pytest as others.

We should definitely take the chance!

Raphael

> On 11 Feb 2016, at 21:01, Bruno Oliveira <nicoddemus at gmail.com> wrote:
> 
> Hi Holger,
> 
> TBH I'm a little shy of my english speaking skills, so I rather don't do the interview. :S
> 
> Someone else might be more suited!
> 
> 
> On Thu, Feb 11, 2016 at 7:10 AM holger krekel <holger at merlinux.eu <mailto:holger at merlinux.eu>> wrote:
> 
> Hey Bruno,
> 
> what about you?  You have been incredibly active and it'd be cool to see
> you interviewed :)  I think apart from the campaign it'd be interesting
> to talk about pytest-3.0 and xdist improvements that we are looking into ...
> 
> best,
> holger
> 
> 
> On Wed, Feb 10, 2016 at 20:14 +0000, Dave Hunt wrote:
> > We have an invitation to be discuss/promote the sprint on the Python Test Podcast if anyone wants to volunteer!
> > https://twitter.com/brianokken/status/697419561797160960 <https://twitter.com/brianokken/status/697419561797160960> <https://twitter.com/brianokken/status/697419561797160960 <https://twitter.com/brianokken/status/697419561797160960>>
> >
> > Cheers,
> > Dave
> >
> > > On 9 Feb 2016, at 17:16, Dave Hunt <dhunt at mozilla.com <mailto:dhunt at mozilla.com>> wrote:
> > >
> > > Published:
> > > http://blargon7.com/2016/02/python-testing-sprint-2016/ <http://blargon7.com/2016/02/python-testing-sprint-2016/> <http://blargon7.com/2016/02/python-testing-sprint-2016/ <http://blargon7.com/2016/02/python-testing-sprint-2016/>>
> > >
> > > Dave
> > >
> > >> On 9 Feb 2016, at 14:09, holger krekel <holger at merlinux.eu <mailto:holger at merlinux.eu> <mailto:holger at merlinux.eu <mailto:holger at merlinux.eu>>> wrote:
> > >>
> > >> On Tue, Feb 09, 2016 at 14:07 +0000, Dave Hunt wrote:
> > >>> I have a public preview of my blog post. Feedback welcome:
> > >>> http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07 <http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07> <http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07 <http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07>> <http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07 <http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07> <http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07 <http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07>>>
> > >>
> > >> reads good!
> > >>
> > >> holger
> > >>
> > >>> Dave
> > >>>
> > >>>> On 9 Feb 2016, at 10:40, Dave Hunt <dhunt at mozilla.com <mailto:dhunt at mozilla.com> <mailto:dhunt at mozilla.com <mailto:dhunt at mozilla.com>>> wrote:
> > >>>>
> > >>>> I think this is a great idea! I have had approval to join you all during the sprint, so I?d be happy to write a blog post about how I came to pytest and what I?d like to work on during the week.
> > >>>>
> > >>>> Cheers,
> > >>>> Dave
> > >>>>
> > >>>>> On 8 Feb 2016, at 20:05, Brianna Laugher <brianna.laugher at gmail.com <mailto:brianna.laugher at gmail.com> <mailto:brianna.laugher at gmail.com <mailto:brianna.laugher at gmail.com>> <mailto:brianna.laugher at gmail.com <mailto:brianna.laugher at gmail.com> <mailto:brianna.laugher at gmail.com <mailto:brianna.laugher at gmail.com>>>> wrote:
> > >>>>>
> > >>>>> Heh, I had the exact same idea last night :)
> > >>>>>
> > >>>>> I was thinking
> > >>>>> 1) how did you get involved with pytest?
> > >>>>> 2) What is your favourite feature/plugin of pytest that is relatively unknown?
> > >>>>> 3) What are you planning to work on during the sprint?
> > >>>>>
> > >>>>> Cheers
> > >>>>> Brianna
> > >>>>>
> > >>>>> On 09/02/2016 6:04 AM, "Holger Krekel" <holger at merlinux.eu <mailto:holger at merlinux.eu> <mailto:holger at merlinux.eu <mailto:holger at merlinux.eu>> <mailto:holger at merlinux.eu <mailto:holger at merlinux.eu> <mailto:holger at merlinux.eu <mailto:holger at merlinux.eu>>>> wrote:
> > >>>>> What about if each of us who wants to participate writes a small blog (lacking a blog a pytest-dev) post of where he/she comes from, past core or plugin work for example, and main areas of interest for the sprint?
> > >>>>>
> > >>>>> We could publish them via updates every few days. Any takers?
> > >>>>> --
> > >>>>> Sent using mobile touch keys, increased chances for errors and misunderstandings. Enjoy!
> > >>>>> _______________________________________________
> > >>>>> pytest-dev mailing list
> > >>>>> pytest-dev at python.org <mailto:pytest-dev at python.org> <mailto:pytest-dev at python.org <mailto:pytest-dev at python.org>> <mailto:pytest-dev at python.org <mailto:pytest-dev at python.org> <mailto:pytest-dev at python.org <mailto:pytest-dev at python.org>>>
> > >>>>> https://mail.python.org/mailman/listinfo/pytest-dev <https://mail.python.org/mailman/listinfo/pytest-dev> <https://mail.python.org/mailman/listinfo/pytest-dev <https://mail.python.org/mailman/listinfo/pytest-dev>> <https://mail.python.org/mailman/listinfo/pytest-dev <https://mail.python.org/mailman/listinfo/pytest-dev> <https://mail.python.org/mailman/listinfo/pytest-dev <https://mail.python.org/mailman/listinfo/pytest-dev>>>
> > >>>>>
> > >>>>> _______________________________________________
> > >>>>> pytest-dev mailing list
> > >>>>> pytest-dev at python.org <mailto:pytest-dev at python.org> <mailto:pytest-dev at python.org <mailto:pytest-dev at python.org>> <mailto:pytest-dev at python.org <mailto:pytest-dev at python.org> <mailto:pytest-dev at python.org <mailto:pytest-dev at python.org>>>
> > >>>>> https://mail.python.org/mailman/listinfo/pytest-dev <https://mail.python.org/mailman/listinfo/pytest-dev> <https://mail.python.org/mailman/listinfo/pytest-dev <https://mail.python.org/mailman/listinfo/pytest-dev>>
> > >>>>
> > >>>
> > >>
> > >> --
> > >> about me:    http://holgerkrekel.net/about-me/ <http://holgerkrekel.net/about-me/> <http://holgerkrekel.net/about-me/ <http://holgerkrekel.net/about-me/>>
> > >> contracting: http://merlinux.eu <http://merlinux.eu/> <http://merlinux.eu/ <http://merlinux.eu/>>
> > >
> >
> 
> --
> about me:    http://holgerkrekel.net/about-me/ <http://holgerkrekel.net/about-me/>
> contracting: http://merlinux.eu <http://merlinux.eu/>
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org <mailto:pytest-dev at python.org>
> https://mail.python.org/mailman/listinfo/pytest-dev <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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160216/836f78da/attachment-0001.html>

From nicoddemus at gmail.com  Tue Feb 16 09:38:38 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Tue, 16 Feb 2016 14:38:38 +0000
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <12D72D98-68DC-479A-B95C-76900D50A9E3@hackebrot.de>
References: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>
 <CAPjwCjsH-ooSzQ4pTQKhq=14vAG9pasJmQurzbqWcGcX4cs8yQ@mail.gmail.com>
 <DFF0964C-990E-41C2-90E0-51F1C21223CD@mozilla.com>
 <A926C829-CB10-429D-9782-C96256271D0A@mozilla.com>
 <20160209140953.GH15751@merlinux.eu>
 <6857A31A-FD3E-434C-8F40-189FBAC5D88C@mozilla.com>
 <D36ADF22-B6B7-48DA-AA08-0AB7E33F44BA@mozilla.com>
 <20160211090955.GQ15751@merlinux.eu>
 <CA+RQFfeqTJ06dPCzXv-ZdKXXk4vRkWSvTS3fyt5y1J=oTt_=mg@mail.gmail.com>
 <12D72D98-68DC-479A-B95C-76900D50A9E3@hackebrot.de>
Message-ID: <CA+RQFfeB47c=cd=QOjmPyi5mDTLt7oWTFpyGCeU+PF_ZN8EFbA@mail.gmail.com>

Hi Raphael,

Thanks, but as I said in another e-email, I rather someone else would do
the interview. :)

But I also agree it is a great opportunity. Brian for a long time has been
writing about Python testing in general and is a noted pytest fan.

Cheers

On Tue, Feb 16, 2016 at 12:28 PM Raphael Pierzina <raphael at hackebrot.de>
wrote:

> Hi all,
>
> I think you should go for it, Bruno! :-)
>
> You have been really active in the past months which makes you a good
> candidate to speak about ongoing topics, I think.
>
> I would like to talk with Brian on the Podcast about the sprint - however
> I am not nearly as involved in core-pytest as others.
>
> We should definitely take the chance!
>
> Raphael
>
> On 11 Feb 2016, at 21:01, Bruno Oliveira <nicoddemus at gmail.com> wrote:
>
> Hi Holger,
>
> TBH I'm a little shy of my english speaking skills, so I rather don't do
> the interview. :S
>
> Someone else might be more suited!
>
>
> On Thu, Feb 11, 2016 at 7:10 AM holger krekel <holger at merlinux.eu> wrote:
>
>>
>> Hey Bruno,
>>
>> what about you?  You have been incredibly active and it'd be cool to see
>> you interviewed :)  I think apart from the campaign it'd be interesting
>> to talk about pytest-3.0 and xdist improvements that we are looking into
>> ...
>>
>> best,
>> holger
>>
>>
>> On Wed, Feb 10, 2016 at 20:14 +0000, Dave Hunt wrote:
>> > We have an invitation to be discuss/promote the sprint on the Python
>> Test Podcast if anyone wants to volunteer!
>> > https://twitter.com/brianokken/status/697419561797160960 <
>> https://twitter.com/brianokken/status/697419561797160960>
>> >
>> > Cheers,
>> > Dave
>> >
>> > > On 9 Feb 2016, at 17:16, Dave Hunt <dhunt at mozilla.com> wrote:
>> > >
>> > > Published:
>> > > http://blargon7.com/2016/02/python-testing-sprint-2016/ <
>> http://blargon7.com/2016/02/python-testing-sprint-2016/>
>> > >
>> > > Dave
>> > >
>> > >> On 9 Feb 2016, at 14:09, holger krekel <holger at merlinux.eu <mailto:
>> holger at merlinux.eu>> wrote:
>> > >>
>> > >> On Tue, Feb 09, 2016 at 14:07 +0000, Dave Hunt wrote:
>> > >>> I have a public preview of my blog post. Feedback welcome:
>> > >>> http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07 <
>> http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07> <
>> http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07 <
>> http://blargon7.com/?p=204&preview=1&_ppp=65d7c71c07>>
>> > >>
>> > >> reads good!
>> > >>
>> > >> holger
>> > >>
>> > >>> Dave
>> > >>>
>> > >>>> On 9 Feb 2016, at 10:40, Dave Hunt <dhunt at mozilla.com <mailto:
>> dhunt at mozilla.com>> wrote:
>> > >>>>
>> > >>>> I think this is a great idea! I have had approval to join you all
>> during the sprint, so I?d be happy to write a blog post about how I came to
>> pytest and what I?d like to work on during the week.
>> > >>>>
>> > >>>> Cheers,
>> > >>>> Dave
>> > >>>>
>> > >>>>> On 8 Feb 2016, at 20:05, Brianna Laugher <
>> brianna.laugher at gmail.com <mailto:brianna.laugher at gmail.com> <mailto:
>> brianna.laugher at gmail.com <mailto:brianna.laugher at gmail.com>>> wrote:
>> > >>>>>
>> > >>>>> Heh, I had the exact same idea last night :)
>> > >>>>>
>> > >>>>> I was thinking
>> > >>>>> 1) how did you get involved with pytest?
>> > >>>>> 2) What is your favourite feature/plugin of pytest that is
>> relatively unknown?
>> > >>>>> 3) What are you planning to work on during the sprint?
>> > >>>>>
>> > >>>>> Cheers
>> > >>>>> Brianna
>> > >>>>>
>> > >>>>> On 09/02/2016 6:04 AM, "Holger Krekel" <holger at merlinux.eu
>> <mailto:holger at merlinux.eu> <mailto:holger at merlinux.eu <mailto:
>> holger at merlinux.eu>>> wrote:
>> > >>>>> What about if each of us who wants to participate writes a small
>> blog (lacking a blog a pytest-dev) post of where he/she comes from, past
>> core or plugin work for example, and main areas of interest for the sprint?
>> > >>>>>
>> > >>>>> We could publish them via updates every few days. Any takers?
>> > >>>>> --
>> > >>>>> Sent using mobile touch keys, increased chances for errors and
>> misunderstandings. Enjoy!
>> > >>>>> _______________________________________________
>> > >>>>> pytest-dev mailing list
>> > >>>>> pytest-dev at python.org <mailto:pytest-dev at python.org> <mailto:
>> pytest-dev at python.org <mailto:pytest-dev at python.org>>
>> > >>>>> https://mail.python.org/mailman/listinfo/pytest-dev <
>> https://mail.python.org/mailman/listinfo/pytest-dev> <
>> https://mail.python.org/mailman/listinfo/pytest-dev <
>> https://mail.python.org/mailman/listinfo/pytest-dev>>
>> > >>>>>
>> > >>>>> _______________________________________________
>> > >>>>> pytest-dev mailing list
>> > >>>>> pytest-dev at python.org <mailto:pytest-dev at python.org> <mailto:
>> pytest-dev at python.org <mailto:pytest-dev at python.org>>
>> > >>>>> https://mail.python.org/mailman/listinfo/pytest-dev <
>> https://mail.python.org/mailman/listinfo/pytest-dev>
>> > >>>>
>> > >>>
>> > >>
>> > >> --
>> > >> about me:    http://holgerkrekel.net/about-me/ <
>> http://holgerkrekel.net/about-me/>
>> > >> contracting: http://merlinux.eu <http://merlinux.eu/>
>> > >
>> >
>>
>> --
>> about me:    http://holgerkrekel.net/about-me/
>> contracting: http://merlinux.eu
>> _______________________________________________
>> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160216/0b309cc8/attachment.html>

From me at the-compiler.org  Tue Feb 16 15:02:59 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Tue, 16 Feb 2016 21:02:59 +0100
Subject: [pytest-dev] pytest-xvfb v0.1.0 released!
Message-ID: <20160216200259.GJ27155@tonks>

Hey!

I'm happy to annouce another pytest plugin I wrote to scratch my own
itch, pytest-xvfb: https://github.com/The-Compiler/pytest-xvfb

This means you can run GUI tests locally without any windows popping
up (on Linux).

I'm aware that there are other plugins to use Xvfb via pytest, but the
aim of pytest-xvfb is to be dead simple: Install it, install Xvfb, and
your tests will run via Xvfb (unless you pass --no-xvfb).

If Xvfb is not installed, the tests will continue to run normally.

I just uploaded v0.1.0 to PyPI, and updated pytest-qt[1] and
qutebrowser[2] to use it.

Thanks to hackebrot and everyone else involved for the cookiecutter
template (which made creating a new plugin much easier again \o/), and
to @cgoldberg for xvfbwrapper which was the inspiration for this
plugin.

Enjoy, and any feedback is appreciated!

Florian

[1] https://github.com/pytest-dev/pytest-qt/pull/124
[2] https://github.com/The-Compiler/qutebrowser/commit/5c617b861c2a517168c694519379982db666e971

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160216/38662c0b/attachment.sig>

From raphael at hackebrot.de  Tue Feb 16 19:05:54 2016
From: raphael at hackebrot.de (Raphael Pierzina)
Date: Wed, 17 Feb 2016 00:05:54 +0000
Subject: [pytest-dev] pytest-xvfb v0.1.0 released!
In-Reply-To: <20160216200259.GJ27155@tonks>
References: <20160216200259.GJ27155@tonks>
Message-ID: <11A2566C-7BFF-4326-8CAB-6A319EE56460@hackebrot.de>

Hi Florian!

Thank you for your feedback! Happy you like the template.

I think you need to update the *year* in the LICENSE file and a link to the actual PyPI package would be helpful! :-)

Best
Raphael

> On 16 Feb 2016, at 20:02, Florian Bruhin <me at the-compiler.org> wrote:
> 
> Hey!
> 
> I'm happy to annouce another pytest plugin I wrote to scratch my own
> itch, pytest-xvfb: https://github.com/The-Compiler/pytest-xvfb
> 
> This means you can run GUI tests locally without any windows popping
> up (on Linux).
> 
> I'm aware that there are other plugins to use Xvfb via pytest, but the
> aim of pytest-xvfb is to be dead simple: Install it, install Xvfb, and
> your tests will run via Xvfb (unless you pass --no-xvfb).
> 
> If Xvfb is not installed, the tests will continue to run normally.
> 
> I just uploaded v0.1.0 to PyPI, and updated pytest-qt[1] and
> qutebrowser[2] to use it.
> 
> Thanks to hackebrot and everyone else involved for the cookiecutter
> template (which made creating a new plugin much easier again \o/), and
> to @cgoldberg for xvfbwrapper which was the inspiration for this
> plugin.
> 
> Enjoy, and any feedback is appreciated!
> 
> Florian
> 
> [1] https://github.com/pytest-dev/pytest-qt/pull/124
> [2] https://github.com/The-Compiler/qutebrowser/commit/5c617b861c2a517168c694519379982db666e971
> 
> -- 
> http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
>   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
>         I love long mails! | http://email.is-not-s.ms/
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev


From me at the-compiler.org  Wed Feb 17 00:12:38 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Wed, 17 Feb 2016 06:12:38 +0100
Subject: [pytest-dev] pytest-xvfb v0.1.0 released!
In-Reply-To: <11A2566C-7BFF-4326-8CAB-6A319EE56460@hackebrot.de>
References: <20160216200259.GJ27155@tonks>
 <11A2566C-7BFF-4326-8CAB-6A319EE56460@hackebrot.de>
Message-ID: <20160217051238.GL27155@tonks>

* Raphael Pierzina <raphael at hackebrot.de> [2016-02-17 00:05:54 +0000]:
> Thank you for your feedback! Happy you like the template.

Thanks as well!

> I think you need to update the *year* in the LICENSE file and a link to the actual PyPI package would be helpful! :-)

Done - now I'm wondering why cookiecutter inserted 2015 there
though...

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160217/cbf20ad2/attachment.sig>

From oliver at bestwalter.de  Wed Feb 17 06:08:52 2016
From: oliver at bestwalter.de (Oliver Bestwalter)
Date: Wed, 17 Feb 2016 11:08:52 +0000
Subject: [pytest-dev] Participation in 2016 Sprint
Message-ID: <CAG5Cgto1MnUS1mJQjxBf04L_z-uLRedT4gq19JecRTC+HWRwHg@mail.gmail.com>

Hello,

I would like to participate in the sprint and I won't need any funding.

My name is Oliver Bestwalter and I live in Ravensburg near Lake Constance.
I fell in love with Python in 2006 and work at Avira since 2011. I am part
of a small team that is automating internal build, test and release
processes with Python. We are responsible for the complete life cycle of
our systems including testing, provisioning and deploying them on Linux,
Windows and Mac, so my job description according to the latest buzzwords
would be DevOps I guess.

I am using py.test in all my pet projects and professionally since 2011.
Last year I started using devpi and tox also. I have no experience working
on the code bases yet.

cheers
Oliver
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160217/022ae96c/attachment.html>

From raphael at hackebrot.de  Wed Feb 17 13:21:20 2016
From: raphael at hackebrot.de (Raphael Pierzina)
Date: Wed, 17 Feb 2016 18:21:20 +0000
Subject: [pytest-dev] python testing sprint June 2016 (pytest/tox) /
 funding needed
In-Reply-To: <20160205130818.GH15751@merlinux.eu>
References: <20160205130818.GH15751@merlinux.eu>
Message-ID: <DCF3D56A-8734-48A2-9F39-A71F7781D806@hackebrot.de>

Hi Holger,

I am currently working to get more funding for the sprint.

Can you please provide me with info on the venue? It is required in a form that I?d like to submit.

Will it be in your Merlinux office?

Cheers
Raphael

> On 05 Feb 2016, at 13:08, holger krekel <holger at merlinux.eu> wrote:
> 
> Hello all,
> 
> we are heading for a one-week python testing sprint focusing on
> improving the open source pytest and tox tools in June 20th-26th 2016 in
> Freiburg, Germany. We have around 10 core maintainers from all across
> the globe who want to participate.  We just started an indiegogo
> campaign to get the neccessary funding for travel/accomodation and hope
> you or your organisation help to make it happen and/or even participate
> yourself.
> 
> See here for more details on the sprint: 
> 
>    http://pytest.org/latest/announce/sprint2016.html
> 
> and here for donating to make it happen:
> 
>    http://igg.me/at/pytest-sprint/x/4034848
> 
> thanks!
> holger
> 
> -- 
> about me:    http://holgerkrekel.net/about-me/
> contracting: http://merlinux.eu
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev


From Nikolaus at rath.org  Wed Feb 17 16:06:49 2016
From: Nikolaus at rath.org (Nikolaus Rath)
Date: Wed, 17 Feb 2016 13:06:49 -0800
Subject: [pytest-dev] How to add delay before processing captured output
Message-ID: <877fi3kpw6.fsf@thinkpad.rath.org>

Hello,

I have a test that starts a background process, and then checks its
response to various queries. Now, I would like to test for particular
bug where some query causes the server to crash. However, there's an
interesting problem with this:


I when running with capturing disabled, I can see the final words of the
server on the screen. When running with capturing (fd capturing, to be
exact), these last messages are lost.

I eventually figured out that the problem is that the test fails before
the server crashes (because the server returns an invalid response
before crashing), and capfd then shows the captured output before the
server had a chance to print its last words.

If I explicitly ignore the test failure, I am able to see the full
captured output. In other words, if

def my_test():
    check_server_response()

becomes

def my_test():
    try:
       check_server_response()
    except:
       time.sleep(1)
       wait

then the server gets enough time to die before the test fails.


Now, I realize that adding a delay is rather hacky, but I do not see a
better way to implement this (after all, I have to take into account
that the server could also hang). However, I really do not want to
insert sleep calls into every single test.

Therefore, I tried to define a custom "wait a little" autouse fixture
that just does this:

@pytest.fixture(autouse=True)
def wait_for_server(request, capfd):
    def wait_a_moment():
        time.sleep(1)
    request.addfinalizer(wait_a_moment)


...but this did not actually have the desired effect. It seems the
fixture is only run *after* capfd has read the the output.


Is there a way to add a delay that is (1) only incurred when a test
fails and (2) executed right after the test fails (ie., before the capfd
finalizer runs)?


Thanks,
-Nikolaus


-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             ?Time flies like an arrow, fruit flies like a Banana.?

From Nikolaus at rath.org  Wed Feb 17 16:12:12 2016
From: Nikolaus at rath.org (Nikolaus Rath)
Date: Wed, 17 Feb 2016 13:12:12 -0800
Subject: [pytest-dev] How to add delay before processing captured output
In-Reply-To: <877fi3kpw6.fsf@thinkpad.rath.org> (Nikolaus Rath's message of
 "Wed, 17 Feb 2016 13:06:49 -0800")
References: <877fi3kpw6.fsf@thinkpad.rath.org>
Message-ID: <874md7kpn7.fsf@thinkpad.rath.org>

On Feb 17 2016, Nikolaus Rath <Nikolaus-BTH8mxji4b0 at public.gmane.org> wrote:
> If I explicitly ignore the test failure, I am able to see the full
> captured output. In other words, if
>
> def my_test():
>     check_server_response()
>
> becomes
>
> def my_test():
>     try:
>        check_server_response()
>     except:
>        time.sleep(1)
>        wait

Obviously that should have been "raise", not "wait".



Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             ?Time flies like an arrow, fruit flies like a Banana.?

From nicoddemus at gmail.com  Wed Feb 17 20:58:23 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 18 Feb 2016 01:58:23 +0000
Subject: [pytest-dev] How to add delay before processing captured output
In-Reply-To: <877fi3kpw6.fsf@thinkpad.rath.org>
References: <877fi3kpw6.fsf@thinkpad.rath.org>
Message-ID: <CA+RQFffqWyUryv=LqOaa1XYJfCoCcim9d8CdvbJKWhgzcSEHaQ@mail.gmail.com>

Hi Nokolaus,

On Wed, Feb 17, 2016 at 7:07 PM Nikolaus Rath <Nikolaus at rath.org> wrote:

> Is there a way to add a delay that is (1) only incurred when a test
> fails and (2) executed right after the test fails (ie., before the capfd
> finalizer runs)?
>

One way to execute something right after the test function is to implement
the pytest_pyfunc_call, which is used to call python test functions:

@pytest.mark.hookwrapper
def pytest_pyfunc_call(pyfuncitem):
    outcome = yield
    failed = outcome.excinfo is not None
    if failed:
        wait_a_moment()

You might even use marks to add this "wait time" only to marked functions,
instead of all tests.

I don't have time to look up and see if this will work with interaction
with the capture plugin, but it's worth a shot.

HTH,
Bruno.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160218/c8ba46b6/attachment.html>

From nicoddemus at gmail.com  Thu Feb 18 07:20:02 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 18 Feb 2016 12:20:02 +0000
Subject: [pytest-dev] GitHub Issues and Pull Requests templates
Message-ID: <CA+RQFffvvunjAXPywdUgpu-Crz=10WuD5v2iKvKDG2c1VkRosQ@mail.gmail.com>

Guys,

GitHub just announced support for Issues and PR templates[1]. I think this
is even better than updating our CONTRIBUTING[2] file, so I was thinking of
adding those for pytest.

For issues:

* include a good description
* include py.test, operating system versions
* pip list of the venv used
* minimal example if possible

For PR:

* where to target the PR: master vs feature branch
* make sure to include one or more tests
* add yourself to AUTHORS
* add a new CHANGELOG entry

What do you guys think? Anything else you would like to add?

[1] https://github.com/blog/2111-issue-and-pull-request-templates
[2] https://github.com/pytest-dev/pytest/issues/1282
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160218/7bf0db87/attachment.html>

From florian.schulze at gmx.net  Thu Feb 18 07:57:01 2016
From: florian.schulze at gmx.net (Florian Schulze)
Date: Thu, 18 Feb 2016 13:57:01 +0100
Subject: [pytest-dev] GitHub Issues and Pull Requests templates
In-Reply-To: <CA+RQFffvvunjAXPywdUgpu-Crz=10WuD5v2iKvKDG2c1VkRosQ@mail.gmail.com>
References: <CA+RQFffvvunjAXPywdUgpu-Crz=10WuD5v2iKvKDG2c1VkRosQ@mail.gmail.com>
Message-ID: <C0D5E872-E27C-46D9-A1C3-F5240287EA58@gmx.net>

On 18 Feb 2016, at 13:20, Bruno Oliveira wrote:

> For PR:
>
> * where to target the PR: master vs feature branch
> * make sure to include one or more tests
> * add yourself to AUTHORS
> * add a new CHANGELOG entry

CHANGELOG and AUTHORS entries easily cause merge conflicts. In a non 
public project we are currently experimenting with putting that info 
into the PR itself and the person merging the PR is responsible for 
updating it. With github this should even be possible through the web 
before merging, I just thought of that and haven't tried. So the author 
is still responsible for providing the info, but not directly in the 
files.

Regards,
Florian Schulze

From me at the-compiler.org  Thu Feb 18 08:05:31 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Thu, 18 Feb 2016 14:05:31 +0100
Subject: [pytest-dev] GitHub Issues and Pull Requests templates
In-Reply-To: <C0D5E872-E27C-46D9-A1C3-F5240287EA58@gmx.net>
References: <CA+RQFffvvunjAXPywdUgpu-Crz=10WuD5v2iKvKDG2c1VkRosQ@mail.gmail.com>
 <C0D5E872-E27C-46D9-A1C3-F5240287EA58@gmx.net>
Message-ID: <20160218130531.GI4904@tonks>

* Florian Schulze <florian.schulze at gmx.net> [2016-02-18 13:57:01 +0100]:
> On 18 Feb 2016, at 13:20, Bruno Oliveira wrote:
> 
> >For PR:
> >
> >* where to target the PR: master vs feature branch
> >* make sure to include one or more tests
> >* add yourself to AUTHORS
> >* add a new CHANGELOG entry
> 
> CHANGELOG and AUTHORS entries easily cause merge conflicts. In a non public
> project we are currently experimenting with putting that info into the PR
> itself and the person merging the PR is responsible for updating it. With
> github this should even be possible through the web before merging, I just
> thought of that and haven't tried. So the author is still responsible for
> providing the info, but not directly in the files.

FWIW, another solution would be to add some empty lines and tell
people to pick a random non-empty line:

https://about.gitlab.com/2015/02/10/gitlab-reduced-merge-conflicts-by-90-percent-with-changelog-placeholders/

(Unfortunately the updated solution with a .gitattributes file didn't
work on GitHub, last time we tried)

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160218/7d6ca101/attachment.sig>

From nicoddemus at gmail.com  Thu Feb 18 08:07:43 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 18 Feb 2016 13:07:43 +0000
Subject: [pytest-dev] GitHub Issues and Pull Requests templates
In-Reply-To: <20160218130531.GI4904@tonks>
References: <CA+RQFffvvunjAXPywdUgpu-Crz=10WuD5v2iKvKDG2c1VkRosQ@mail.gmail.com>
 <C0D5E872-E27C-46D9-A1C3-F5240287EA58@gmx.net> <20160218130531.GI4904@tonks>
Message-ID: <CA+RQFfcgX2rw+D+z5pwvrEz7S25SQo8jVeZO5rSKP0_kHud5DQ@mail.gmail.com>

On Thu, Feb 18, 2016 at 11:05 AM Florian Bruhin <me at the-compiler.org> wrote:

> FWIW, another solution would be to add some empty lines and tell
> people to pick a random non-empty line:
>
>
> https://about.gitlab.com/2015/02/10/gitlab-reduced-merge-conflicts-by-90-percent-with-changelog-placeholders/


+1 for this solution.

Cheers,
Bruno,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160218/1a158f84/attachment.html>

From Nikolaus at rath.org  Thu Feb 18 12:18:56 2016
From: Nikolaus at rath.org (Nikolaus Rath)
Date: Thu, 18 Feb 2016 09:18:56 -0800
Subject: [pytest-dev] How to add delay before processing captured output
In-Reply-To: <CA+RQFffqWyUryv=LqOaa1XYJfCoCcim9d8CdvbJKWhgzcSEHaQ@mail.gmail.com>
 (Bruno Oliveira's message of "Thu, 18 Feb 2016 01:58:23 +0000")
References: <877fi3kpw6.fsf@thinkpad.rath.org>
 <CA+RQFffqWyUryv=LqOaa1XYJfCoCcim9d8CdvbJKWhgzcSEHaQ@mail.gmail.com>
Message-ID: <87fuwq7x8f.fsf@thinkpad.rath.org>

On Feb 18 2016, Bruno Oliveira <nicoddemus-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org> wrote:
> Hi Nokolaus,
>
> On Wed, Feb 17, 2016 at 7:07 PM Nikolaus Rath <Nikolaus-BTH8mxji4b0 at public.gmane.org> wrote:
>
>> Is there a way to add a delay that is (1) only incurred when a test
>> fails and (2) executed right after the test fails (ie., before the capfd
>> finalizer runs)?
>>
>
> One way to execute something right after the test function is to implement
> the pytest_pyfunc_call, which is used to call python test functions:
>
> @pytest.mark.hookwrapper
> def pytest_pyfunc_call(pyfuncitem):
>     outcome = yield
>     failed = outcome.excinfo is not None
>     if failed:
>         wait_a_moment()
>
> You might even use marks to add this "wait time" only to marked functions,
> instead of all tests.
>
> I don't have time to look up and see if this will work with interaction
> with the capture plugin, but it's worth a shot.

Works perfectly, thanks!


Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             ?Time flies like an arrow, fruit flies like a Banana.?

From raphael at hackebrot.de  Thu Feb 18 13:40:56 2016
From: raphael at hackebrot.de (Raphael Pierzina)
Date: Thu, 18 Feb 2016 18:40:56 +0000
Subject: [pytest-dev] GitHub Issues and Pull Requests templates
In-Reply-To: <CA+RQFffvvunjAXPywdUgpu-Crz=10WuD5v2iKvKDG2c1VkRosQ@mail.gmail.com>
References: <CA+RQFffvvunjAXPywdUgpu-Crz=10WuD5v2iKvKDG2c1VkRosQ@mail.gmail.com>
Message-ID: <F8418EC7-E1AD-40BA-B06A-8F55B9C16873@hackebrot.de>

ohhh..guess I?ve never added myself to AUTHORS nor updated CHANGELOG.

That?s a +1 on PR templates :D

Raphael
> On 18 Feb 2016, at 12:20, Bruno Oliveira <nicoddemus at gmail.com> wrote:
> 
> Guys,
> 
> GitHub just announced support for Issues and PR templates[1]. I think this is even better than updating our CONTRIBUTING[2] file, so I was thinking of adding those for pytest.
> 
> For issues:
> 
> * include a good description
> * include py.test, operating system versions
> * pip list of the venv used
> * minimal example if possible
> 
> For PR:
> 
> * where to target the PR: master vs feature branch
> * make sure to include one or more tests
> * add yourself to AUTHORS
> * add a new CHANGELOG entry
> 
> What do you guys think? Anything else you would like to add?
> 
> [1] https://github.com/blog/2111-issue-and-pull-request-templates <https://github.com/blog/2111-issue-and-pull-request-templates>
> [2] https://github.com/pytest-dev/pytest/issues/1282 <https://github.com/pytest-dev/pytest/issues/1282>
> _______________________________________________
> 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: <http://mail.python.org/pipermail/pytest-dev/attachments/20160218/efbe316d/attachment.html>

From brianna.laugher at gmail.com  Sat Feb 20 06:41:50 2016
From: brianna.laugher at gmail.com (Brianna Laugher)
Date: Sat, 20 Feb 2016 22:41:50 +1100
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <CAPjwCjufkfznttRg_TakoDU5XLGsJAJh-C1U8axgO502b_4OUw@mail.gmail.com>
References: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>
 <CAPjwCjsH-ooSzQ4pTQKhq=14vAG9pasJmQurzbqWcGcX4cs8yQ@mail.gmail.com>
 <DFF0964C-990E-41C2-90E0-51F1C21223CD@mozilla.com>
 <A926C829-CB10-429D-9782-C96256271D0A@mozilla.com>
 <20160209140953.GH15751@merlinux.eu>
 <6857A31A-FD3E-434C-8F40-189FBAC5D88C@mozilla.com>
 <D36ADF22-B6B7-48DA-AA08-0AB7E33F44BA@mozilla.com>
 <20160211090955.GQ15751@merlinux.eu>
 <CA+RQFfeqTJ06dPCzXv-ZdKXXk4vRkWSvTS3fyt5y1J=oTt_=mg@mail.gmail.com>
 <1FF4AFBC-F983-4315-B9F0-0FE232C6097C@merlinux.eu>
 <CAPjwCjscXJ3=ji8MzunZd_Tc_z1JQx-BumqP_uoqn1z6gyv32Q@mail.gmail.com>
 <7E9CA161-D07E-4D8D-B645-3A8E25275BAB@pelme.se>
 <CAPjwCjufkfznttRg_TakoDU5XLGsJAJh-C1U8axgO502b_4OUw@mail.gmail.com>
Message-ID: <CAPjwCjt+KWEOi0_6_kgiBe+PP4sR_5yDHa5L0mPrF7yH-N13Jg@mail.gmail.com>

Just sent out an update with a link to your post Andreas, thanks!

Who's up next...Raphael? Floris? Florian? Holger? Are you all working on
posts? :P

cheers
Brianna


On 16 February 2016 at 22:24, Brianna Laugher <brianna.laugher at gmail.com>
wrote:

> That's a great post, I look forward to that pytest blog too ;)
>
> I suggest we wait a few days to post another IGG update, they recommend to
> do updates at least every 5 days, but it's nice if the total donated gets a
> bit bigger between each update :)
>
> Brianna
>
> On 16 February 2016 at 08:43, Andreas Pelme <andreas at pelme.se> wrote:
>
>>
>> > On 13 feb. 2016, at 05:06, Brianna Laugher <brianna.laugher at gmail.com>
>> wrote:
>> >
>> > Andreas, how about you? You could speak about your company's support
>> too :)
>>
>> I?ve put together a post at
>>
>> http://andreas.pelme.se/pytest-sprint.html
>>
>> I don?t really have a draft mode on my blog, but I?m quite sure it does
>> not receive any traffic anyways. Feedback on the post is very welcome :)
>>
>> Cheers,
>> Andreas
>>
>>
>
>
> --
> They've just been waiting in a mountain for the right moment:
> http://modernthings.org/
>



-- 
They've just been waiting in a mountain for the right moment:
http://modernthings.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160220/4d6e3bde/attachment.html>

From flub at devork.be  Sat Feb 20 09:30:08 2016
From: flub at devork.be (Floris Bruynooghe)
Date: Sat, 20 Feb 2016 14:30:08 +0000
Subject: [pytest-dev] Participation in 2016 Sprint
In-Reply-To: <CAG5Cgto1MnUS1mJQjxBf04L_z-uLRedT4gq19JecRTC+HWRwHg@mail.gmail.com>
References: <CAG5Cgto1MnUS1mJQjxBf04L_z-uLRedT4gq19JecRTC+HWRwHg@mail.gmail.com>
Message-ID: <CAAWk_Dx_x3PwLjOd+3u26VQevmkv+ETPerwvnEmJKzh5r-Swcw@mail.gmail.com>

Hi Oliver,

On 17 February 2016 at 11:08, Oliver Bestwalter <oliver at bestwalter.de> wrote:
> I would like to participate in the sprint and I won't need any funding.

Great that you want to join us!

> I am using py.test in all my pet projects and professionally since 2011.
> Last year I started using devpi and tox also. I have no experience working
> on the code bases yet.

No worries, it will be a great opportunity to get into the code and
help will be at hand.

We don't know an exact location yet or where we'll be staying, so keep
an eye out on the list for more details to start appearing.  I look
forward to meeting you in Freiburg!

Floris

From flub at devork.be  Sat Feb 20 09:45:25 2016
From: flub at devork.be (Floris Bruynooghe)
Date: Sat, 20 Feb 2016 14:45:25 +0000
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <CAPjwCjt+KWEOi0_6_kgiBe+PP4sR_5yDHa5L0mPrF7yH-N13Jg@mail.gmail.com>
References: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>
 <CAPjwCjsH-ooSzQ4pTQKhq=14vAG9pasJmQurzbqWcGcX4cs8yQ@mail.gmail.com>
 <DFF0964C-990E-41C2-90E0-51F1C21223CD@mozilla.com>
 <A926C829-CB10-429D-9782-C96256271D0A@mozilla.com>
 <20160209140953.GH15751@merlinux.eu>
 <6857A31A-FD3E-434C-8F40-189FBAC5D88C@mozilla.com>
 <D36ADF22-B6B7-48DA-AA08-0AB7E33F44BA@mozilla.com>
 <20160211090955.GQ15751@merlinux.eu>
 <CA+RQFfeqTJ06dPCzXv-ZdKXXk4vRkWSvTS3fyt5y1J=oTt_=mg@mail.gmail.com>
 <1FF4AFBC-F983-4315-B9F0-0FE232C6097C@merlinux.eu>
 <CAPjwCjscXJ3=ji8MzunZd_Tc_z1JQx-BumqP_uoqn1z6gyv32Q@mail.gmail.com>
 <7E9CA161-D07E-4D8D-B645-3A8E25275BAB@pelme.se>
 <CAPjwCjufkfznttRg_TakoDU5XLGsJAJh-C1U8axgO502b_4OUw@mail.gmail.com>
 <CAPjwCjt+KWEOi0_6_kgiBe+PP4sR_5yDHa5L0mPrF7yH-N13Jg@mail.gmail.com>
Message-ID: <CAAWk_Dz32W5dGjo=5r7RNaQyuWv85ar2G=3rYooDxkfVuhatiw@mail.gmail.com>

On 20 February 2016 at 11:41, Brianna Laugher <brianna.laugher at gmail.com> wrote:
> Just sent out an update with a link to your post Andreas, thanks!
>
> Who's up next...Raphael? Floris? Florian? Holger? Are you all working on
> posts? :P

Yep :-)
http://blog.devork.be/2016/02/pytest-sprint-in-freiburg.html

From oliver at bestwalter.de  Sat Feb 20 10:32:14 2016
From: oliver at bestwalter.de (Oliver Bestwalter)
Date: Sat, 20 Feb 2016 15:32:14 +0000
Subject: [pytest-dev] Participation in 2016 Sprint
In-Reply-To: <CAAWk_Dx_x3PwLjOd+3u26VQevmkv+ETPerwvnEmJKzh5r-Swcw@mail.gmail.com>
References: <CAG5Cgto1MnUS1mJQjxBf04L_z-uLRedT4gq19JecRTC+HWRwHg@mail.gmail.com>
 <CAAWk_Dx_x3PwLjOd+3u26VQevmkv+ETPerwvnEmJKzh5r-Swcw@mail.gmail.com>
Message-ID: <CAG5CgtqyaFR335OmcAg_uVsdwm6Bv--NOqgt1DkHjB87cFG6Mw@mail.gmail.com>

Hello Floris,

thanks for the warm welcome. I already started questioning my own sanity a
bit after making that gut decision that I want to participate, because to
spend a whole week on a sprint for a project I am not actively involved in
yet seems a bit ... weird. But the point is: I really appreciate the whole
pytest/tox/devpi toolchain and the ideas behind it, so I'll have go at
making myself useful while having some fun and learning from the jedi
masters of testing :)

cheers
Oliver

On Sat, 20 Feb 2016 at 15:30 Floris Bruynooghe <flub at devork.be> wrote:

> Hi Oliver,
>
> On 17 February 2016 at 11:08, Oliver Bestwalter <oliver at bestwalter.de>
> wrote:
> > I would like to participate in the sprint and I won't need any funding.
>
> Great that you want to join us!
>
> > I am using py.test in all my pet projects and professionally since 2011.
> > Last year I started using devpi and tox also. I have no experience
> working
> > on the code bases yet.
>
> No worries, it will be a great opportunity to get into the code and
> help will be at hand.
>
> We don't know an exact location yet or where we'll be staying, so keep
> an eye out on the list for more details to start appearing.  I look
> forward to meeting you in Freiburg!
>
> Floris
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160220/aef2d6da/attachment.html>

From me at the-compiler.org  Sat Feb 20 11:07:48 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Sat, 20 Feb 2016 17:07:48 +0100
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <CAPjwCjt+KWEOi0_6_kgiBe+PP4sR_5yDHa5L0mPrF7yH-N13Jg@mail.gmail.com>
References: <20160209140953.GH15751@merlinux.eu>
 <6857A31A-FD3E-434C-8F40-189FBAC5D88C@mozilla.com>
 <D36ADF22-B6B7-48DA-AA08-0AB7E33F44BA@mozilla.com>
 <20160211090955.GQ15751@merlinux.eu>
 <CA+RQFfeqTJ06dPCzXv-ZdKXXk4vRkWSvTS3fyt5y1J=oTt_=mg@mail.gmail.com>
 <1FF4AFBC-F983-4315-B9F0-0FE232C6097C@merlinux.eu>
 <CAPjwCjscXJ3=ji8MzunZd_Tc_z1JQx-BumqP_uoqn1z6gyv32Q@mail.gmail.com>
 <7E9CA161-D07E-4D8D-B645-3A8E25275BAB@pelme.se>
 <CAPjwCjufkfznttRg_TakoDU5XLGsJAJh-C1U8axgO502b_4OUw@mail.gmail.com>
 <CAPjwCjt+KWEOi0_6_kgiBe+PP4sR_5yDHa5L0mPrF7yH-N13Jg@mail.gmail.com>
Message-ID: <20160220160748.GN4904@tonks>

* Brianna Laugher <brianna.laugher at gmail.com> [2016-02-20 22:41:50 +1100]:
> Who's up next...Raphael? Floris? Florian? Holger? Are you all working on
> posts? :P

I was busy with a training I'll give next week - I'll look into
writing a blog post after that :)

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160220/5f46be9c/attachment-0001.sig>

From raphael at hackebrot.de  Sat Feb 20 11:10:11 2016
From: raphael at hackebrot.de (Raphael Pierzina)
Date: Sat, 20 Feb 2016 16:10:11 +0000
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <CAAWk_Dz32W5dGjo=5r7RNaQyuWv85ar2G=3rYooDxkfVuhatiw@mail.gmail.com>
References: <AD431ECA-1067-44BE-B68E-759C236200D6@merlinux.eu>
 <CAPjwCjsH-ooSzQ4pTQKhq=14vAG9pasJmQurzbqWcGcX4cs8yQ@mail.gmail.com>
 <DFF0964C-990E-41C2-90E0-51F1C21223CD@mozilla.com>
 <A926C829-CB10-429D-9782-C96256271D0A@mozilla.com>
 <20160209140953.GH15751@merlinux.eu>
 <6857A31A-FD3E-434C-8F40-189FBAC5D88C@mozilla.com>
 <D36ADF22-B6B7-48DA-AA08-0AB7E33F44BA@mozilla.com>
 <20160211090955.GQ15751@merlinux.eu>
 <CA+RQFfeqTJ06dPCzXv-ZdKXXk4vRkWSvTS3fyt5y1J=oTt_=mg@mail.gmail.com>
 <1FF4AFBC-F983-4315-B9F0-0FE232C6097C@merlinux.eu>
 <CAPjwCjscXJ3=ji8MzunZd_Tc_z1JQx-BumqP_uoqn1z6gyv32Q@mail.gmail.com>
 <7E9CA161-D07E-4D8D-B645-3A8E25275BAB@pelme.se>
 <CAPjwCjufkfznttRg_TakoDU5XLGsJAJh-C1U8axgO502b_4OUw@mail.gmail.com>
 <CAPjwCjt+KWEOi0_6_kgiBe+PP4sR_5yDHa5L0mPrF7yH-N13Jg@mail.gmail.com>
 <CAAWk_Dz32W5dGjo=5r7RNaQyuWv85ar2G=3rYooDxkfVuhatiw@mail.gmail.com>
Message-ID: <06136058-8C97-4E2D-9E22-5555A435A0B6@hackebrot.de>

Good job, Floris.

Currently working on the my mini pytest-blog. I?ll keep you posted.

Raphael

> On 20 Feb 2016, at 14:45, Floris Bruynooghe <flub at devork.be> wrote:
> 
> On 20 February 2016 at 11:41, Brianna Laugher <brianna.laugher at gmail.com> wrote:
>> Just sent out an update with a link to your post Andreas, thanks!
>> 
>> Who's up next...Raphael? Floris? Florian? Holger? Are you all working on
>> posts? :P
> 
> Yep :-)
> http://blog.devork.be/2016/02/pytest-sprint-in-freiburg.html
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev


From nicoddemus at gmail.com  Sat Feb 20 17:44:22 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Sat, 20 Feb 2016 22:44:22 +0000
Subject: [pytest-dev] Make a 2.9.0-rc.1 release?
Message-ID: <CA+RQFfc=YO897PM01PahT3BzCZFO6M3Mb10LH8DH_amcoiyeOQ@mail.gmail.com>

Hi,

I was thinking of making a 2.9.0-rc.1 release (published on my devpi.net
account) and send an email to the relevant mailing lists asking people to
give it a go on their test suites. The objective is to detect any major
breakages, and if nothing major is found, release 2.9.0 by the end of the
week.

What do you guys think? If nobody opposes the idea, I will prepare a
2.9.0-rc.1 release tomorrow or Monday the latest and send the e-mails.

Cheers,
Bruno.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160220/3e7fedbc/attachment.html>

From tom at viner.tv  Sat Feb 20 18:15:33 2016
From: tom at viner.tv (Tom Viner)
Date: Sat, 20 Feb 2016 23:15:33 +0000
Subject: [pytest-dev] Sprint participants writing a blog post?
Message-ID: <CANBSuyGKZj8EsRjSX_6JoVXQ5HDsMfYfN82fea2gxak5E8gJeQ@mail.gmail.com>

>
> Date: Sat, 20 Feb 2016 22:41:50 +1100
> From: Brianna Laugher <brianna.laugher at gmail.com>
>
> Who's up next...Raphael? Floris? Florian? Holger? Are you all working on
> posts? :P
>

Me! :-) Here's a draft post introducing myself and explaining why I've
signed up. Feedback welcome!

http://tomviner.co.uk/drafts/pytest-and-i-time-for-a-sprint.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160220/bdc78448/attachment.html>

From nicoddemus at gmail.com  Sat Feb 20 20:24:55 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Sun, 21 Feb 2016 01:24:55 +0000
Subject: [pytest-dev] Sprint participants writing a blog post?
In-Reply-To: <CANBSuyGKZj8EsRjSX_6JoVXQ5HDsMfYfN82fea2gxak5E8gJeQ@mail.gmail.com>
References: <CANBSuyGKZj8EsRjSX_6JoVXQ5HDsMfYfN82fea2gxak5E8gJeQ@mail.gmail.com>
Message-ID: <CA+RQFfcPt+29Fhf4xk_6BS6RdQYXQ3MSQyBp5gURT++9qca-nA@mail.gmail.com>

On Sat, Feb 20, 2016 at 9:16 PM Tom Viner <tom at viner.tv> wrote:

> Date: Sat, 20 Feb 2016 22:41:50 +1100
>> From: Brianna Laugher <brianna.laugher at gmail.com>
>
>
>>
>> Who's up next...Raphael? Floris? Florian? Holger? Are you all working on
>> posts? :P
>>
>
> Me! :-) Here's a draft post introducing myself and explaining why I've
> signed up. Feedback welcome!
>
> http://tomviner.co.uk/drafts/pytest-and-i-time-for-a-sprint.html
>

Nice post Tom! Good idea mentioning the adopt pytest month, nice touch! :)

Bruno
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160221/ff77b5dc/attachment.html>

From holger at merlinux.eu  Sun Feb 21 02:10:57 2016
From: holger at merlinux.eu (holger krekel)
Date: Sun, 21 Feb 2016 07:10:57 +0000
Subject: [pytest-dev] Make a 2.9.0-rc.1 release?
In-Reply-To: <CA+RQFfc=YO897PM01PahT3BzCZFO6M3Mb10LH8DH_amcoiyeOQ@mail.gmail.com>
References: <CA+RQFfc=YO897PM01PahT3BzCZFO6M3Mb10LH8DH_amcoiyeOQ@mail.gmail.com>
Message-ID: <20160221071057.GC9650@merlinux.eu>

Hi Bruno,

On Sat, Feb 20, 2016 at 22:44 +0000, Bruno Oliveira wrote:
> Hi,
> 
> I was thinking of making a 2.9.0-rc.1 release (published on my devpi.net
> account) and send an email to the relevant mailing lists asking people to
> give it a go on their test suites. The objective is to detect any major
> breakages, and if nothing major is found, release 2.9.0 by the end of the
> week.
> 
> What do you guys think? If nobody opposes the idea, I will prepare a
> 2.9.0-rc.1 release tomorrow or Monday the latest and send the e-mails.

My experiences with beta/rc releases so far was that very few people go for
it.  Doing a 2.9.0 and being prepared to fix regressions quickly might be
a path involving less efforts with a good result. YMMV.

holger

> Cheers,
> Bruno.

> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev


-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From nicoddemus at gmail.com  Sun Feb 21 09:26:48 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Sun, 21 Feb 2016 14:26:48 +0000
Subject: [pytest-dev] Make a 2.9.0-rc.1 release?
In-Reply-To: <20160221071057.GC9650@merlinux.eu>
References: <CA+RQFfc=YO897PM01PahT3BzCZFO6M3Mb10LH8DH_amcoiyeOQ@mail.gmail.com>
 <20160221071057.GC9650@merlinux.eu>
Message-ID: <CA+RQFfeAGb5zPi9ynQJY2eK8czDDpYPeGDBSpjxHQ84JG2pF0A@mail.gmail.com>

Hi Holger,

On Sun, Feb 21, 2016 at 4:10 AM holger krekel <holger at merlinux.eu> wrote:

> My experiences with beta/rc releases so far was that very few people go for
> it.  Doing a 2.9.0 and being prepared to fix regressions quickly might be
> a path involving less efforts with a good result. YMMV.
>

Since the cost of doing such a release is small I think it is worth it. I
agree that being prepared to fix regressions after the official release is
done is important though. :)

Cheers,
Bruno.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160221/4c615a70/attachment.html>

From raphael at hackebrot.de  Sun Feb 21 11:27:26 2016
From: raphael at hackebrot.de (Raphael Pierzina)
Date: Sun, 21 Feb 2016 16:27:26 +0000
Subject: [pytest-dev] Announcing new blog - pytest-tricks
Message-ID: <547E2694-200C-4D4C-9E64-11F3CED68D99@hackebrot.de>

Hi,

I built a blog for pytest related articles using Lektor[1].

http://hackebrot.github.io/pytest-tricks/ <http://hackebrot.github.io/pytest-tricks/>


My idea is to frequently push out snippets that are probably not worth writing a full blog post, similar to the TIL-project[2]. Please feel free to pick a card from the issue tracker and submit a PR.

https://github.com/hackebrot/pytest-tricks <https://github.com/hackebrot/pytest-tricks>


I placed a message referring to our dev sprint funding campaign to the footer of the site. Who knows maybe this encourages more people to donate :)

Let me know your thoughts! Any feedback is greatly appreciated.

Cheers
Raphael

[1]: https://www.getlektor.com/ <https://www.getlektor.com/>
[2]: https://github.com/jbranchaud/til <https://github.com/jbranchaud/til>




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160221/6ecd27f6/attachment-0001.html>

From tom at viner.tv  Sun Feb 21 16:30:09 2016
From: tom at viner.tv (Tom Viner)
Date: Sun, 21 Feb 2016 21:30:09 +0000
Subject: [pytest-dev] Enabling viewing of rewritten AST trees as Python
Message-ID: <CANBSuyE7_=bNxpT-BGtvCrcSpz5RdMe-PPrAXkyCfnosF7-hZw@mail.gmail.com>

To update on this topic, I've now published a pytest plugin to display the
rewritten AST as Python:
https://github.com/tomviner/pytest-ast-back-to-python

Not sure if it will ever come in handy, but it was interesting to create my
first pytest plugin anyway! Keep it in mind as an option, if we get any
bugs with assertion rewriting.

It works like this:

As an example take a trivial test like:

def test_simple():
    a = 1
    b = 2
    assert 1 + 2 == 3

View the rewritten AST as Python like this:

$ py.test --show-ast-as-python test_simple.py
======================================== test session starts
========================================
plugins: ast-back-to-python-0.1.0, cov-2.2.1
collected 1 items

test_simple.py .
======================================== Rewritten AST as Python
========================================
import builtins as @py_builtins
import _pytest.assertion.rewrite as @pytest_ar

def test_simple():
    a = 1
    b = 2
    @py_assert0 = 1
    @py_assert2 = 2
    @py_assert4 = @py_assert0 + @py_assert2
    @py_assert6 = 3
    @py_assert5 = @py_assert4 == @py_assert6
    if not @py_assert5:
        @py_format8 = @pytest_ar._call_reprcompare(('==',), (@py_assert5,),
('(%(py1)s + %(py3)s) == %(py7)s',), (@py_assert4, @py_assert6)) % {'py3':
@pytest_ar._saferepr(@py_assert2), 'py1':
@pytest_ar._saferepr(@py_assert0), 'py7': @pytest_ar._saferepr(@py_assert6)}
        @py_format10 = ('' + 'assert %(py9)s') % {'py9': @py_format8}
        raise AssertionError(@pytest_ar._format_explanation(@py_format10))
    @py_assert0 = @py_assert2 = @py_assert4 = @py_assert5 = @py_assert6 =
None

On 2 March 2015 at 09:06, Tom Viner <tom at viner.tv> wrote:

> One extra note:
>
> `py.test -s` is required to see rewritten AST output, even for failing
> tests, because the output comes while
> tests are being collected and rewritten, not during the execution of a
> test. So pytest's "show output upon
> fail" cannot help here.
>
> If anyone knows how to tie the output to particular tests, that would be
> great.
>
>
> On 1 March 2015 at 23:01, Tom Viner <tom at viner.tv> wrote:
>
>> Thanks for your ideas Floris, I've managed to get it working with
>> your pytest_configure suggestion.
>>
>> The only extra bit was having to disable reading the cached pyc files
>> that pytest writes, as these skip my monkeypatch.
>>
>> Take a look, it's simple to use:
>> https://gist.github.com/tomviner/c3537c2f2b2b8172f83e
>>
>> If there's any demand, I could easily make this a pip installable pytest
>> plugin.
>>
>> On 13 November 2014 at 23:34, Floris Bruynooghe <flub at devork.be> wrote:
>>
>>> Hi Tom,
>>>
>>> On 9 November 2014 19:18, Tom Viner <tom at viner.tv> wrote:
>>> > The four options I can think of to gain access to this variable:
>>> > - monkey patch rewrite.rewrite_asserts
>>> > - edit rewrite_asserts and paste in the logging code above:
>>> >     -- temporarily, by each developer, on each occasion required
>>> >     -- permanently, but only running when a certain debug flag is
>>> active
>>> > - expose the rewritten AST via a new hook
>>> >
>>> > monkey patch is my preferred option, because if I can make it work, a
>>> plugin
>>> > could be written. I just need some help to find an appropriate hook to
>>> do
>>> > the monkey patching before pytest gets going with the
>>> AssertionRewritingHook
>>> > and calls rewrite_asserts. Without knowledge of an early-running hook,
>>> I
>>> > could only get this working by patching rewrite_asserts then calling
>>> > pytest.main myself, see
>>> > https://gist.github.com/tomviner/13c95cdb1e159028fc0b
>>>
>>> Would this work by using monkeypatching, but using a method on
>>> _pytest.pytester.TmpTestDir which wraps around inline_run or
>>> inline_runsource?  That would seem like a fairly reasonable approach.
>>> It could simply skip with an appropriate message if the meta lib is
>>> importable and print the reversed python code to stdout for capsys to
>>> collect.
>>>
>>> If you would like to go the full plugin way I believe you just need to
>>> hook in before collection happens.  I imagine pytest_configure would
>>> be a reasonable hook for that, but have to admit I haven't tried it.
>>>
>>>
>>> Regards,
>>> Floris
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160221/7a9b38e1/attachment.html>

From tom at viner.tv  Sun Feb 21 16:57:00 2016
From: tom at viner.tv (Tom Viner)
Date: Sun, 21 Feb 2016 21:57:00 +0000
Subject: [pytest-dev] Sprint participants writing a blog post?
Message-ID: <CANBSuyGDyQTpHOeooiNCbtsUSZ2Qjwxk-VK2Q_bB0FL_4Y2pZA@mail.gmail.com>

>
> Date: Sun, 21 Feb 2016 01:24:55 +0000
> From: Bruno Oliveira <nicoddemus at gmail.com>
> Subject: Re: [pytest-dev] Sprint participants writing a blog post?
>
> On Sat, Feb 20, 2016 at 9:16 PM Tom Viner <tom at viner.tv> wrote:
>
> > Date: Sat, 20 Feb 2016 22:41:50 +1100
> >> From: Brianna Laugher <brianna.laugher at gmail.com>
> >
> >
> >>
> >> Who's up next...Raphael? Floris? Florian? Holger? Are you all working on
> >> posts? :P
> >>
> >
> > Me! :-) Here's a draft post introducing myself and explaining why I've
> > signed up. Feedback welcome!
> >
> > http://tomviner.co.uk/drafts/pytest-and-i-time-for-a-sprint.html
> >
>
> Nice post Tom! Good idea mentioning the adopt pytest month, nice touch! :)
>
> Bruno
>

Thanks Bruno. Published:
http://tomviner.co.uk/pytest-and-i-time-for-a-sprint.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160221/69977a0f/attachment.html>

From holger at merlinux.eu  Mon Feb 22 02:22:30 2016
From: holger at merlinux.eu (holger krekel)
Date: Mon, 22 Feb 2016 07:22:30 +0000
Subject: [pytest-dev] Make a 2.9.0-rc.1 release?
In-Reply-To: <CA+RQFfeAGb5zPi9ynQJY2eK8czDDpYPeGDBSpjxHQ84JG2pF0A@mail.gmail.com>
References: <CA+RQFfc=YO897PM01PahT3BzCZFO6M3Mb10LH8DH_amcoiyeOQ@mail.gmail.com>
 <20160221071057.GC9650@merlinux.eu>
 <CA+RQFfeAGb5zPi9ynQJY2eK8czDDpYPeGDBSpjxHQ84JG2pF0A@mail.gmail.com>
Message-ID: <20160222072230.GG9650@merlinux.eu>

Hey  Bruno,

On Sun, Feb 21, 2016 at 14:26 +0000, Bruno Oliveira wrote:
> Hi Holger,
> 
> On Sun, Feb 21, 2016 at 4:10 AM holger krekel <holger at merlinux.eu> wrote:
> 
> > My experiences with beta/rc releases so far was that very few people go for
> > it.  Doing a 2.9.0 and being prepared to fix regressions quickly might be
> > a path involving less efforts with a good result. YMMV.
> >
> 
> Since the cost of doing such a release is small I think it is worth it. I
> agree that being prepared to fix regressions after the official release is
> done is important though. :)

If you'd like to do it, sure, go for a RC1 :)

holger

> Cheers,
> Bruno.

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From nicoddemus at gmail.com  Mon Feb 22 18:11:46 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Mon, 22 Feb 2016 23:11:46 +0000
Subject: [pytest-dev] pytest 2.9.0-rc.1
Message-ID: <CA+RQFfcwQ=t5YRPqfcYGopvsuNTU4aGCrWEUdwzYsXBrVYBBtw@mail.gmail.com>

Hi all,

We released pytest 2.9.0-rc.1, a release candidate to try to identify any
regressions before the official 2.9.0 release. It would be really helpful
if people could install this version, execute their test suites and report
any regressions to pytest-dev at python.org or the issues page[1].

To install this release, please execute the following with a virtualenv
active:

pip install -i https://devpi.net/nicoddemus/dev pytest==2.9.0-rc.1

[1] https://github.com/pytest-dev/pytest/issues

Thanks,
The py.test team.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160222/969639c7/attachment.html>

From me at the-compiler.org  Tue Feb 23 02:57:35 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Tue, 23 Feb 2016 08:57:35 +0100
Subject: [pytest-dev] pytest 2.9.0-rc.1
In-Reply-To: <CA+RQFfcwQ=t5YRPqfcYGopvsuNTU4aGCrWEUdwzYsXBrVYBBtw@mail.gmail.com>
References: <CA+RQFfcwQ=t5YRPqfcYGopvsuNTU4aGCrWEUdwzYsXBrVYBBtw@mail.gmail.com>
Message-ID: <20160223075735.GD4904@tonks>

Hey,

* Bruno Oliveira <nicoddemus at gmail.com> [2016-02-22 23:11:46 +0000]:
> We released pytest 2.9.0-rc.1, a release candidate to try to identify any
> regressions before the official 2.9.0 release. It would be really helpful
> if people could install this version, execute their test suites and report
> any regressions to pytest-dev at python.org or the issues page[1].

Other than pytest-hypothesis breaking because it doesn't expect the
dash in the version number, I have 17 failing and 1 xpassing test in
the qutebrowser testsuite, with (it seems) different kinds of issues.

I'm not sure if I'll have time to investigate this week though, maybe
not before Sunday.

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160223/4d203f97/attachment.sig>

From nicoddemus at gmail.com  Tue Feb 23 05:54:09 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Tue, 23 Feb 2016 10:54:09 +0000
Subject: [pytest-dev] pytest 2.9.0-rc.1
In-Reply-To: <20160223075735.GD4904@tonks>
References: <CA+RQFfcwQ=t5YRPqfcYGopvsuNTU4aGCrWEUdwzYsXBrVYBBtw@mail.gmail.com>
 <20160223075735.GD4904@tonks>
Message-ID: <CA+RQFfc8AqjOtg=PLrR6cVG9ebR=_dyxh58OaLfZnr8oKu6tVg@mail.gmail.com>

Hey Florian,

Thanks for taking the time to try it out.

On Tue, Feb 23, 2016 at 4:57 AM Florian Bruhin <me at the-compiler.org> wrote:

> Other than pytest-hypothesis breaking because it doesn't expect the
> dash in the version number,


That's strange, as having that dash is correct for pre-releases according
to the semver spec[1].


> I have 17 failing and 1 xpassing test in
> the qutebrowser testsuite, with (it seems) different kinds of issues.
>

If you still have the output of those runs readily available, could you
send them to me off-list? Either way I will give qutebrowser test suite a
spin with the pre-release version later.

I'm not sure if I'll have time to investigate this week though, maybe
> not before Sunday.
>

No problem, thanks again!

[1] http://semver.org/#spec-item-9

Bruno
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160223/bd560a76/attachment.html>

From mail at florian-schulze.net  Tue Feb 23 07:58:13 2016
From: mail at florian-schulze.net (Florian Schulze)
Date: Tue, 23 Feb 2016 13:58:13 +0100
Subject: [pytest-dev] pytest 2.9.0-rc.1
In-Reply-To: <CA+RQFfc8AqjOtg=PLrR6cVG9ebR=_dyxh58OaLfZnr8oKu6tVg@mail.gmail.com>
References: <CA+RQFfcwQ=t5YRPqfcYGopvsuNTU4aGCrWEUdwzYsXBrVYBBtw@mail.gmail.com>
 <20160223075735.GD4904@tonks>
 <CA+RQFfc8AqjOtg=PLrR6cVG9ebR=_dyxh58OaLfZnr8oKu6tVg@mail.gmail.com>
Message-ID: <F66CD5E6-5511-4037-8BDC-79FF78B6FD5D@florian-schulze.net>

On 23 Feb 2016, at 11:54, Bruno Oliveira wrote:

> Hey Florian,
>
> Thanks for taking the time to try it out.
>
> On Tue, Feb 23, 2016 at 4:57 AM Florian Bruhin <me at the-compiler.org> wrote:
>
>> Other than pytest-hypothesis breaking because it doesn't expect the
>> dash in the version number,
>
>
> That's strange, as having that dash is correct for pre-releases according
> to the semver spec[1].

Relevant is PEP404. The version should be 2.9.0.rc1 if I'm not mistaken.

Regards,
Florian Schulze

From mail at florian-schulze.net  Tue Feb 23 07:59:31 2016
From: mail at florian-schulze.net (Florian Schulze)
Date: Tue, 23 Feb 2016 13:59:31 +0100
Subject: [pytest-dev] pytest 2.9.0-rc.1
In-Reply-To: <F66CD5E6-5511-4037-8BDC-79FF78B6FD5D@florian-schulze.net>
References: <CA+RQFfcwQ=t5YRPqfcYGopvsuNTU4aGCrWEUdwzYsXBrVYBBtw@mail.gmail.com>
 <20160223075735.GD4904@tonks>
 <CA+RQFfc8AqjOtg=PLrR6cVG9ebR=_dyxh58OaLfZnr8oKu6tVg@mail.gmail.com>
 <F66CD5E6-5511-4037-8BDC-79FF78B6FD5D@florian-schulze.net>
Message-ID: <470D9BA4-A5EC-480C-AC80-86520BD3185D@florian-schulze.net>

On 23 Feb 2016, at 13:58, Florian Schulze wrote:

> On 23 Feb 2016, at 11:54, Bruno Oliveira wrote:
>
>> Hey Florian,
>>
>> Thanks for taking the time to try it out.
>>
>> On Tue, Feb 23, 2016 at 4:57 AM Florian Bruhin <me at the-compiler.org> 
>> wrote:
>>
>>> Other than pytest-hypothesis breaking because it doesn't expect the
>>> dash in the version number,
>>
>>
>> That's strange, as having that dash is correct for pre-releases 
>> according
>> to the semver spec[1].
>
> Relevant is PEP404. The version should be 2.9.0.rc1 if I'm not 
> mistaken.

Should have been PEP440: https://www.python.org/dev/peps/pep-0440/

Regards,
Florian Schulze

From nicoddemus at gmail.com  Tue Feb 23 08:05:32 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Tue, 23 Feb 2016 13:05:32 +0000
Subject: [pytest-dev] pytest 2.9.0-rc.1
In-Reply-To: <470D9BA4-A5EC-480C-AC80-86520BD3185D@florian-schulze.net>
References: <CA+RQFfcwQ=t5YRPqfcYGopvsuNTU4aGCrWEUdwzYsXBrVYBBtw@mail.gmail.com>
 <20160223075735.GD4904@tonks>
 <CA+RQFfc8AqjOtg=PLrR6cVG9ebR=_dyxh58OaLfZnr8oKu6tVg@mail.gmail.com>
 <F66CD5E6-5511-4037-8BDC-79FF78B6FD5D@florian-schulze.net>
 <470D9BA4-A5EC-480C-AC80-86520BD3185D@florian-schulze.net>
Message-ID: <CA+RQFfeSk_Aa46EUCm6AoUD72tzh5yTqa+ovu-miqEQUdi4h6g@mail.gmail.com>

On Tue, Feb 23, 2016 at 9:59 AM Florian Schulze <mail at florian-schulze.net>
wrote:

> On 23 Feb 2016, at 13:58, Florian Schulze wrote:
>
> > Relevant is PEP404. The version should be 2.9.0.rc1 if I'm not
> > mistaken.
>
> Should have been PEP440: https://www.python.org/dev/peps/pep-0440/


Thanks for the link. Will follow that standard so it is more compatible
with that PEP then. :)

Best,
Bruno.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160223/a96f112e/attachment-0001.html>

From alexamici at gmail.com  Tue Feb 23 09:03:28 2016
From: alexamici at gmail.com (Alessandro Amici)
Date: Tue, 23 Feb 2016 14:03:28 +0000
Subject: [pytest-dev] How to sandbox test execution with pytest
In-Reply-To: <CACnxfA_M0UV7wN_bGj-pVxncuR5OtjCKWV55PD30qFnxi7zKPQ@mail.gmail.com>
References: <CACnxfA_vT9wyKxgsJ7UfzpvE0ndcfAVmNgbywnV6dXjA_qOPtA@mail.gmail.com>
 <CANkHFr_HksRaVZpn-BTM-4rerGLwsiDt0+cCm4+7O-gb288y8A@mail.gmail.com>
 <20160211094422.GT15751@merlinux.eu>
 <CACnxfA_i4J3=xW3AFpEHHBMd+sUYbg3uK65v2fNsJjg9jq-eMw@mail.gmail.com>
 <CACnxfA_M0UV7wN_bGj-pVxncuR5OtjCKWV55PD30qFnxi7zKPQ@mail.gmail.com>
Message-ID: <CACnxfA9LKXYT75WDA5FbuJc+512gTa1bH7RuoSX-heshqUz+uA@mail.gmail.com>

Hi,

I still didn't find any ready-made tool to run pytest inside a docker
container so I ended up setting up my own solution.

I gave the gory details in the answer to my own question on StackOverflow:

http://stackoverflow.com/questions/35322452

but it all boils down to add a carefully crafted (read quite kludgy)
Dockerfile to the to folder of a project and run the container with a magic
set of options.

I hope you find it useful,
Alessandro



On Fri, 12 Feb 2016 at 09:06 Alessandro Amici <alexamici at gmail.com> wrote:

> Hi,
>
> while researching the use of pytest-xdist for my CI-like use case and I
> realised that having a "disposable" environment is as important as having
> a isolated one, so that every test or every session runs from the same
> initial state and it is not influenced by what older sessions might have
> left on folders writable by the *testuser* (/home/testuser, /tmp, /var/tmp,
> etc).
>
> This made me go back searching the web again for a way to use pytest with
> docker and I'm currently evaluating the following projects:
>
> https://github.com/search?q=pytest+docker
>
> Does anybody have experience with pytest/docker integration or with any of
> these projects?
>
> I'll report back what I find.
>
> Thanks,
> Alessandro
>
> On Thu, 11 Feb 2016 at 11:07 Alessandro Amici <alexamici at gmail.com> wrote:
>
>> Ionel and Holger,
>>
>> I had considered the --box option, but it only implements process-level
>> isolation which is not enough for my use case as I want to protect also
>> from unrestricted filesystem read/write access. Sorry, I should have
>> mentioned it in the question.
>>
>> Holger's suggestion instead looks almost good enough as user-level
>> isolation is strong and highly customizable. The only problem is that you
>> need administration access to the machine to create and configure a new
>> user. I'll look into it as I've never used the --tx option.
>>
>> Thanks,
>> Alessandro
>>
>>
>> On Thu, 11 Feb 2016 at 10:44 holger krekel <holger at merlinux.eu> wrote:
>>
>>> On Thu, Feb 11, 2016 at 11:39 +0200, Ionel Cristian M?rie? wrote:
>>> > There's the `--boxed` option (from
>>> https://pypi.python.org/pypi/pytest-xdist)
>>> > but you can easily do your own "insulator" by using fork syscall.
>>>
>>> Also one can use plain "xdist" which provides process-level isolation.
>>> It shouldn't be too hard to also use another unix user via e.g.:
>>>
>>>     py.test --tx ssh=OTHERUSER at localhost --dist=each
>>>
>>> but you need to have setup rsyncing, see
>>> https://pypi.python.org/pypi/pytest-xdist
>>> for some more info.  The current "remote" test running is a bit limited
>>> and we plan to improve xdist distribution during the upcoming pytest
>>> sprint,
>>> see
>>> https://www.indiegogo.com/projects/python-testing-sprint-mid-2016/x/4034848#/
>>> creating an issue for "user-level separation of running tests" or
>>> something
>>> similar and adding a little donation is one way to help it :)
>>>
>>> best,
>>> holger
>>>
>>>
>>> >
>>> > Thanks,
>>> > -- Ionel Cristian M?rie?, http://blog.ionelmc.ro
>>> >
>>> > On Thu, Feb 11, 2016 at 10:33 AM, Alessandro Amici <
>>> alexamici at gmail.com>
>>> > wrote:
>>> >
>>> > > Hi,
>>> > >
>>> > > I asked the following question on StackOverflow first
>>> > > http://stackoverflow.com/questions/35322452, but someone quickly
>>> (and
>>> > > wrongly in my opinion) marked that as duplicate of the general
>>> "sandboxing
>>> > > in python", so I can't get answers there anymore :(
>>> > >
>>> > > Here is the question:
>>> > >
>>> > > I'm interested in executing potentially untrusted tests with pytest
>>> in
>>> > > some kind of sandbox, similarly to what continuous integration
>>> services do.
>>> > >
>>> > > I understand that to properly sandbox a python process you need
>>> OS-level
>>> > > isolation, like running the tests in a disposable chroot/container,
>>> but in
>>> > > my use case I don't need to protect against intentionally malicious
>>> code,
>>> > > only from dangerous behaviour of pairing "randomly" functions with
>>> > > arguments. So lesser strict sandboxing may still be acceptable. But I
>>> > > didn't find any plugin that enables any form of sandboxing.
>>> > >
>>> > > What is the best way to sandbox tests execution in pytest?
>>> > >
>>> > > **Update**: This question is not about [python sandboxing in
>>> general](
>>> > >
>>> http://stackoverflow.com/questions/3068139/how-can-i-sandbox-python-in-pure-python
>>> )
>>> > > as the tests' code is run by pytest and I can't change the way it is
>>> > > executed to use `exec` or `ast` or whatever. Also using pypy-sandbox
>>> is not
>>> > > an option unfortunately as it is "a prototype only" as per the [PyPy
>>> > > feature page](http://pypy.org/features.html).
>>> > >
>>> > > End of question.
>>> > >
>>> > > For context I'm writing a pytest plugin that lets you search
>>> installed
>>> > > modules for functions that pass the given feature-specification tests
>>> > > (still alpha):
>>> > >
>>> > > https://github.com/alexamici/pytest-wish
>>> > >
>>> > > If you find the question useful and not answered already on
>>> stackoverflow,
>>> > > the best course of action would be to reopen it and answer there,
>>> but I'll
>>> > > take also an answer here :)
>>> > >
>>> > > Alessandro
>>> > >
>>> > >
>>> > > _______________________________________________
>>> > > 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
>>>
>>>
>>> --
>>> about me:    http://holgerkrekel.net/about-me/
>>> contracting: http://merlinux.eu
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160223/8f3010cd/attachment.html>

From fp at gocept.com  Wed Feb 24 02:04:35 2016
From: fp at gocept.com (Florian Pilz)
Date: Wed, 24 Feb 2016 08:04:35 +0100
Subject: [pytest-dev] Continue after rerunning failing test combined with
 exitfirst
Message-ID: <E1A1E7D7-762C-49D2-A036-A4FFD56366AA@gocept.com>

Hi, a new issue was opened for `pytest-rerunfailures`, since it does not work nicely with the `?exitfirst` flag (see https://github.com/pytest-dev/pytest-rerunfailures/issues/30 <https://github.com/pytest-dev/pytest-rerunfailures/issues/30>).

I have looked into the reports and tracked the state of `Session.testsfailed`, but since an outcome ?failure" is overwritten with the outcome ?rerun? no failures are recorded and `Session.testsfailed` remain 0 es expected. However, the test suite still stops after the test finally passes after the required amount of reruns.

So my question is, which other mechanisms does pytest have to determine whether the test suite should be stopped? I?m pretty sure that exitfirst / maxfail = 1 is not the reason.

To give you more context, I?m running the following tests with `py.test ?reruns 3 -x`:

def test_before():
    pass

def test_flaky():
    import py
    path = py.path.local(__file__).dirpath().ensure('test.res')
    count = path.read() or 1
    if int(count) <= 3:
        path.write(int(count) + 1)
        raise Exception('Failure: {}'.format(count))

def test_after():
    pass
?????????
Florian Pilz ? fp at gocept.com ? Software Developer
gocept gmbh & co. kg ? Forsterstra?e 29 ? 06112 Halle (Saale) ? Germany
http://gocept.com <http://gocept.com/> ? Tel +49 345 122 9889 7
Python, Pyramid, Plone, Zope ? consulting, development, hosting, operations

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160224/47330c2e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160224/47330c2e/attachment.sig>

From holger at merlinux.eu  Thu Feb 25 01:00:45 2016
From: holger at merlinux.eu (holger krekel)
Date: Thu, 25 Feb 2016 06:00:45 +0000
Subject: [pytest-dev] sprint growing / funding at 60% now
Message-ID: <20160225060045.GG9650@merlinux.eu>

Hey all,

just some quick news: Splunk (company from west coast, US) just send $1000 which
brings us to about 60% funded status, 22 days left.  They'll also send
Danielle and Antony from their QA department who i got to know
personally a few weeks ago when i gave a master-class training in San
Francisco.

I amended the list of sprint participants in the repo and also added
some preliminary company affilitations.  Did i miss anyone except Ronny
(who is 99% going to come ASFAIK but can currently be not much online)?

    Anatoly Bubenkoff, Netherlands
    Andreas Pelme, Personalkollen, Sweden
    Anthony Wang, Splunk, US
    Brianna Laugher, Australia
    Bruno Oliveira, Brazil
    Danielle Jenkins, Splunk, US
    Dave Hunt, UK
    Florian Bruhin, Switzerland
    Floris Bruynooghe, UK
    Holger Krekel, merlinux, Germany
    Oliver Bestwalter, Avira, Germany
    Omar Kohl, Germany
    Raphael Pierzina, US/UK
    Tom Viner, UK

I also have a "likely attend" status from Stephan Obermann who is working
for Dolby and at advanced-level with pytest, tox, devpi stuff since a few years.

Please let me know if i missed anyone and add company affiliations if you like.

Seems like i'll need to look for a bigger place than i initially thought :)
More organisational details are coming in March.

cheers,

holger

-- 
about me:    http://holgerkrekel.net/about-me/
contracting: http://merlinux.eu

From alexamici at gmail.com  Thu Feb 25 04:19:55 2016
From: alexamici at gmail.com (Alessandro Amici)
Date: Thu, 25 Feb 2016 09:19:55 +0000
Subject: [pytest-dev] ANN: pytest-nodev v0.9.3 - Test-driven code search
Message-ID: <CACnxfA_+wg7Zjznt1X7eiQHNKLgHqEDTeGrbPf-9xotc5msgPQ@mail.gmail.com>

I am pleased to announce the release of the new beta release of
pytest-nodev (was pytest-wish) a test-driven code search plugin for pytest:

https://pytest-nodev.readthedocs.org

Changes:
- renamed the package to pytest-nodev from pytest-wish (sorry!)
- refuse to run potentially dangerous `--wish-from-all` by default and...
- ... document how to run inside a container to safely enable all the
features
- simpler command line usage
- more documentation and references to the academic research on the
test-driven code search subject

Development effort is directed to fixing bugs and writing better
documentation before the 1.0 release. Help is welcomed and appreciated:

https://github.com/nodev-io/pytest-nodev

User questions are best directed to
http://stackoverflow.com/search?q=pytest-nodev and general questions can be
sent to pytest-dev at python.org.

Thanks,
Alessandro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160225/8bd4c39c/attachment.html>

From nicoddemus at gmail.com  Thu Feb 25 18:35:26 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 25 Feb 2016 23:35:26 +0000
Subject: [pytest-dev] pytest 2.9.0-rc.1
In-Reply-To: <20160223075735.GD4904@tonks>
References: <CA+RQFfcwQ=t5YRPqfcYGopvsuNTU4aGCrWEUdwzYsXBrVYBBtw@mail.gmail.com>
 <20160223075735.GD4904@tonks>
Message-ID: <CA+RQFfdW1fJBgxyx0c6Bs8ocuPP5odx_=CKOBNKTV5k4LVhksg@mail.gmail.com>

On Tue, Feb 23, 2016 at 4:57 AM Florian Bruhin <me at the-compiler.org> wrote:

> Hey,
>
> * Bruno Oliveira <nicoddemus at gmail.com> [2016-02-22 23:11:46 +0000]:
> > We released pytest 2.9.0-rc.1, a release candidate to try to identify any
> > regressions before the official 2.9.0 release. It would be really helpful
> > if people could install this version, execute their test suites and
> report
> > any regressions to pytest-dev at python.org or the issues page[1].
>
> Other than pytest-hypothesis breaking because it doesn't expect the
> dash in the version number, I have 17 failing and 1 xpassing test in
> the qutebrowser testsuite, with (it seems) different kinds of issues.
>

FWIW, all tests failed due to the same problem, as reported in [1]. A PR is
already in place [2] and should be merged soon.

[1] https://github.com/pytest-dev/pytest/issues/1412
[2] https://github.com/pytest-dev/pytest/pull/1413

Cheers,
Bruno.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160225/db28ee0d/attachment.html>

From me at the-compiler.org  Fri Feb 26 13:09:36 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Fri, 26 Feb 2016 19:09:36 +0100
Subject: [pytest-dev] pytest 2.9.0-rc.1
In-Reply-To: <CA+RQFfdW1fJBgxyx0c6Bs8ocuPP5odx_=CKOBNKTV5k4LVhksg@mail.gmail.com>
References: <CA+RQFfcwQ=t5YRPqfcYGopvsuNTU4aGCrWEUdwzYsXBrVYBBtw@mail.gmail.com>
 <20160223075735.GD4904@tonks>
 <CA+RQFfdW1fJBgxyx0c6Bs8ocuPP5odx_=CKOBNKTV5k4LVhksg@mail.gmail.com>
Message-ID: <20160226180936.GO4904@tonks>

* Bruno Oliveira <nicoddemus at gmail.com> [2016-02-25 23:35:26 +0000]:
> On Tue, Feb 23, 2016 at 4:57 AM Florian Bruhin <me at the-compiler.org> wrote:
> 
> > Hey,
> >
> > * Bruno Oliveira <nicoddemus at gmail.com> [2016-02-22 23:11:46 +0000]:
> > > We released pytest 2.9.0-rc.1, a release candidate to try to identify any
> > > regressions before the official 2.9.0 release. It would be really helpful
> > > if people could install this version, execute their test suites and
> > report
> > > any regressions to pytest-dev at python.org or the issues page[1].
> >
> > Other than pytest-hypothesis breaking because it doesn't expect the
> > dash in the version number, I have 17 failing and 1 xpassing test in
> > the qutebrowser testsuite, with (it seems) different kinds of issues.
> >
> 
> FWIW, all tests failed due to the same problem, as reported in [1]. A PR is
> already in place [2] and should be merged soon.
> 
> [1] https://github.com/pytest-dev/pytest/issues/1412
> [2] https://github.com/pytest-dev/pytest/pull/1413

I just merged that PR - my testsuite now runs fine again :)
I also moved all remaining 2.9 issues to 2.10.

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160226/1fb3f4a1/attachment.sig>

From nicoddemus at gmail.com  Fri Feb 26 13:13:00 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Fri, 26 Feb 2016 18:13:00 +0000
Subject: [pytest-dev] pytest 2.9.0-rc.1
In-Reply-To: <20160226180936.GO4904@tonks>
References: <CA+RQFfcwQ=t5YRPqfcYGopvsuNTU4aGCrWEUdwzYsXBrVYBBtw@mail.gmail.com>
 <20160223075735.GD4904@tonks>
 <CA+RQFfdW1fJBgxyx0c6Bs8ocuPP5odx_=CKOBNKTV5k4LVhksg@mail.gmail.com>
 <20160226180936.GO4904@tonks>
Message-ID: <CA+RQFfcJQMH-_v3VNbt=3oO=5mbn0rW1a=wtpNFtn12AokNevQ@mail.gmail.com>

On Fri, Feb 26, 2016 at 3:09 PM Florian Bruhin <me at the-compiler.org> wrote:

> * Bruno Oliveira <nicoddemus at gmail.com> [2016-02-25 23:35:26 +0000]:
> > On Tue, Feb 23, 2016 at 4:57 AM Florian Bruhin <me at the-compiler.org>
> wrote:
> >
> > > Hey,
> > >
> > > * Bruno Oliveira <nicoddemus at gmail.com> [2016-02-22 23:11:46 +0000]:
> > > > We released pytest 2.9.0-rc.1, a release candidate to try to
> identify any
> > > > regressions before the official 2.9.0 release. It would be really
> helpful
> > > > if people could install this version, execute their test suites and
> > > report
> > > > any regressions to pytest-dev at python.org or the issues page[1].
> > >
> > > Other than pytest-hypothesis breaking because it doesn't expect the
> > > dash in the version number, I have 17 failing and 1 xpassing test in
> > > the qutebrowser testsuite, with (it seems) different kinds of issues.
> > >
> >
> > FWIW, all tests failed due to the same problem, as reported in [1]. A PR
> is
> > already in place [2] and should be merged soon.
> >
> > [1] https://github.com/pytest-dev/pytest/issues/1412
> > [2] https://github.com/pytest-dev/pytest/pull/1413
>
> I just merged that PR - my testsuite now runs fine again :)
> I also moved all remaining 2.9 issues to 2.10.
>

Thanks!

>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160226/9f4ced69/attachment.html>

From me at the-compiler.org  Fri Feb 26 17:59:29 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Fri, 26 Feb 2016 23:59:29 +0100
Subject: [pytest-dev] pytest-platform-markers v0.1.0 released!
Message-ID: <20160226225929.GV4904@tonks>

Hey,

Bruno motivated[1] me to split some code I had in qutebrowser's
testsuite to a separate plugin - so pytest-platform-markers[2] was
born!

The plugin provides various markers such as @pytest.mark.linux or
@pytest.mark.windows which makes it easier to skip tests on platforms
they don't run on.

Enjoy!

Florian

[1] https://github.com/hackebrot/pytest-tricks/issues/3#issuecomment-188730108
[2] https://github.com/The-Compiler/pytest-platform-markers/

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160226/2a6cd830/attachment.sig>

From bryan.berry at gmail.com  Sun Feb 28 14:21:29 2016
From: bryan.berry at gmail.com (Bryan Berry)
Date: Mon, 29 Feb 2016 02:21:29 +0700
Subject: [pytest-dev] question about pytest_addoption
Message-ID: <CANsX4xQ=bwo613ptZg+09iwPC=383SYL-S_i2s7t+TUhayOdRQ@mail.gmail.com>

dear pytest folks,

I am creating an automation framework based on pytest for my employer that i
hope to someday soon open-source. This framework is tentatively titled
'Ghost-elephant' after my child's imaginary friend. At a 5,000 foot view my
ghost-elephant manages virtual machines and a bag of configuration
variables needed
to execute the tests.

Ghost-elephant adds some custom command-line options but I also want to also
allow libraries, say added by separate fixture libraries, to add
command-line
flags. For example, Ghost-elephant adds a flag --skip-cleanup that my
custom software
fixtures use to determine if the fixture's cleanup step should be skipped.

A specific fixture library, say foo_fixture that handles the installation
of some particularly hairy proprietary software, may want to add additional
custom options. Perhaps, we need to pass this fixture a special flag
to enable ipv6 support.

Here is how I have currently attempted to support this feature and it isn't
working
at all. Could anyone point me towards a working solution?

I really want to minimize the code that a user needs to add to their
contest.py to take advantage of this.

# foo_fixture.py

def pytest_addoption_foo(parser):
    parser.addoption('--ipv6', action='store_true', default=False)


@pytest.fixture
def foo_fixture(request):
    ipv6 = request.config.getoption('--ipv6')
    # lots of complicated stuff


# conftest.py

def pytest_addoptions():
    option_adders = []
    gs = globals()
    for g in gs.keys():
        if isinstance(gs[g], function) and
g.startswith('pytest_addoption_'):
            option_adders.append(gs[g])
    def pytest_addoption(parser):
        for o in option_adders:
            o.__call__(parser)

pytest_addoptions()
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160229/42c996a7/attachment.html>

From tbekolay at gmail.com  Sun Feb 28 19:54:04 2016
From: tbekolay at gmail.com (Trevor Bekolay)
Date: Sun, 28 Feb 2016 19:54:04 -0500
Subject: [pytest-dev] Announcing pytest-cram
Message-ID: <CAL-NvjU27POMPOfPRKPPkV6ZSEmWYdfSstOMTXyT4_k+AS3Xzg@mail.gmail.com>

Hi everyone,

Over the weekend I wrote a pytest plugin that will run tests developed for
the cram tool (see https://bitheap.org/cram/) with pytest. I pushed the
first release to PyPI today, and was hoping that anyone with experience
with cram could test out pytest-cram on their tests.

On PyPI: https://pypi.python.org/pypi/pytest-cram
On Github: https://github.com/tbekolay/pytest-cram

It's only the first release and no users yet, so I'm not asking to be added
to the pytest-dev organization yet, though hopefully that will be possible.
For now, I'm hoping that people find it useful. Please let me know if you
run into any bugs by filing issues on Github.

Thanks!
Trevor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160228/c72045b1/attachment.html>