From bryan.berry at gmail.com  Mon Feb  6 23:16:06 2017
From: bryan.berry at gmail.com (Bryan Berry)
Date: Tue, 7 Feb 2017 11:16:06 +0700
Subject: [pytest-dev] request for feedback,
 pytest-suites - a plugin to execute a subset of tests
Message-ID: <CANsX4xRcxk7XxNGnRbWmup=_7q6dLBpu-MOAuN5fKm7syBfOSA@mail.gmail.com>

Hey folks!

I have made a little plugin that makes it easier to executes subsets of
your tests. I would very much appreciate your feedback on it.

https://github.com/bryanwb/pytest-suites

This plugin determines which tests belong in a suite by applying UNIX-style
glob
to the test function name. A suite consists of a name, pattern (glob) or
patterns, and
additional metadata.

First, add pytest-suites to your conftest.py

   # conftest.py

   pytest_plugins = ['suites']

Next you will likely want to define a suite or two. Also do this in
``conftest.py``



   # conftest.py

   from pytest_suites import add_suite

   add_suite(name="smoke", pattern="*basic*")
   add_suite(name="advanced", pattern="*")
   add_suite(name="extended", pattern="*", tags={'mode': 'extended'})


Meanwhile, add some tests:

  # my_test.py

  def test_basic_feature1():
      assert True

  def test_basic_feature2():
      assert True

  def test_advanced_feature1():
      assert True

  def test_advanced_feature1():
      assert True


Use the command-line option ``--suite SUITE`` to specify the suite

Executing ``pytest my_test.py --suite smoke`` will only execute the tests
`test_basic_feature1` and `test_basic_feature2`.

pytest-suites provides a mechanism for running tests to learn what suite is
currently being executed and access the suite's tags dictionary. This can be
useful when you want to occasionally test less or greater functionality
within a
given test. For example, you may frequently want `test_my_feature` to check
the
common case but right before a release you may the same test to be more
exhaustive.

  def test_advanced_feature1(suite):
      mode = suite.tags.get('mode', 'basic')
      if mode == 'extended':
          # test exhaustively
          assert do_expensive_operation()
      else:
          # test the common case
          assert True


That's pretty much it! there is a little more info on the github page. I
plan to publish this to pypi shortly.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20170207/17bb9664/attachment.html>

From aninhacostaribeiro at gmail.com  Tue Feb  7 18:01:21 2017
From: aninhacostaribeiro at gmail.com (Ana Ribeiro)
Date: Tue, 7 Feb 2017 20:01:21 -0300
Subject: [pytest-dev] Google Summer of Code
In-Reply-To: <CAG5CgtoeSXpP55O=+YaJSyNN48X_nSN+Y_9CUZx2rv1ffyY8VA@mail.gmail.com>
References: <CAO-2QM7xGuo78edg=1yWCwFYnkG=CpGigqMdAj-nQh9pBzwPyA@mail.gmail.com>
 <CA+RQFfduikX0trYb6udie1bY0nhuGJ9xrTM57s-wyjd5GwYO+Q@mail.gmail.com>
 <BD28797C-04FB-4908-9EC7-7108B2E822D0@mozilla.com>
 <CAO-2QM60vtba2x9VOdgO5DvbsTOtKto7QSERTLdirMTicJVndw@mail.gmail.com>
 <CA+RQFfejKis42OKnj8YaeFr4d_HOcTT1PuF_WhOREso8K9KaOg@mail.gmail.com>
 <CAG5Cgtqj8Svx77QK9eA7pPSFnfbpA1fKUCa_YbmOqGRvowz69g@mail.gmail.com>
 <CAO-2QM5kYzEgMe=5cEBVAegfxc-=HEyF37xQDSa5QSbT_Y3Hyg@mail.gmail.com>
 <20170125084719.dnwea7zpetto4s5y@merlinux.eu>
 <CA+RQFfdFU9GHaPG-d55OJzKBXwv9gm19=qhSEn1WyzCdjto=2Q@mail.gmail.com>
 <20170125110405.ohlbms2rahdxwwsy@tonks>
 <CAO-2QM72gmukFM8pkijnj=1vxW-5au=bjLiQ27-onzcGba0j6Q@mail.gmail.com>
 <CAG5CgtoeSXpP55O=+YaJSyNN48X_nSN+Y_9CUZx2rv1ffyY8VA@mail.gmail.com>
Message-ID: <CAO-2QM43UojCb3Vr-KJ1s2dKv-gRoxnvPc7Cs6cRy+eLv9Omzg@mail.gmail.com>

Hello,

I asked them how we could apply as a Python suborg. We have to create an
idea page until March 7 following this template (
https://wiki.python.org/moin/SummerOfCode/OrgIdeasPageTemplate) and send it
to Python.  gsoc-admins(at)python.org. So if anyone has an idea for a
summer project for any Pytest project, even plugins or other smaller
projects, I invite you to write to this list.

Best regards,
Ana

2017-01-25 12:00 GMT-03:00 Oliver Bestwalter <oliver at bestwalter.de>:

> Hello,
>
> o.k. sounds all good to me then.
>
> I have a topic in mind already that could nicely be tackled which is what
> we started to draft already as part of the sprint:
> https://github.com/tox-dev/tox/blob/master/doc/drafts/
> extend-envs-and-packagebuilds.md - if we find a dedicated individual who
> wants to get their feet wet with this topic, I actually start to get quite
> enthusiastic about the whole idea :)
>
> One caveat though: I am quite a catastrophe when it comes to classical
> admin things like filling out forms and stuff - so if this would be part of
> my work as a mentor, I will have to ask for a mentor myself to learn to
> better tackle these things ;)
>
> Cheers
> Oliver
>
> On Wed, 25 Jan 2017 at 12:31 Ana Ribeiro <aninhacostaribeiro at gmail.com>
> wrote:
>
>> Hello,
>>
>> Sorry, when I read the email too quickly and I thought of the browser
>> (Tor) instead of Tox (shame)... For sure, I have used Tox on my internship.
>>
>> About bad experiences, they may happen, but good experiences may happen
>> as well... In Mozilla Outreachy program, they had a good application
>> process in my opinion, we had to solve a small issue together our mentor,
>> so we could see if this partnership would work well. In GSoC we can decide
>> how we are going to take the application process, so I think it is a good
>> way.
>>
>> About how to apply as a suborg of python, I may ask them on IRC and come
>> here with more information.
>>
>> Best regards,
>> Ana
>>
>> 2017-01-25 8:04 GMT-03:00 Florian Bruhin <me at the-compiler.org>:
>>
>> * Bruno Oliveira <nicoddemus at gmail.com> [2017-01-25 10:27:09 +0000]:
>> > On Wed, Jan 25, 2017 at 6:47 AM holger krekel <holger at merlinux.eu>
>> wrote:
>> >
>> > > I'll leave the question of if/how to apply as org/suborg to others
>> > > as i am not bound to mentor myself (see my other post).
>> > >
>> >
>> > Which post do you mean Holger? I didn't receive any other reply from
>> you to
>> > this thread. Perhaps you sent it only to Ana by accident?
>>
>> I did, and it's in the archive too:
>> https://mail.python.org/pipermail/pytest-dev/2017-January/003985.html
>>
>> 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
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20170207/3b11961b/attachment.html>

From nicoddemus at gmail.com  Tue Feb  7 21:08:44 2017
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Wed, 08 Feb 2017 02:08:44 +0000
Subject: [pytest-dev] Google Summer of Code
In-Reply-To: <CAO-2QM43UojCb3Vr-KJ1s2dKv-gRoxnvPc7Cs6cRy+eLv9Omzg@mail.gmail.com>
References: <CAO-2QM7xGuo78edg=1yWCwFYnkG=CpGigqMdAj-nQh9pBzwPyA@mail.gmail.com>
 <CA+RQFfduikX0trYb6udie1bY0nhuGJ9xrTM57s-wyjd5GwYO+Q@mail.gmail.com>
 <BD28797C-04FB-4908-9EC7-7108B2E822D0@mozilla.com>
 <CAO-2QM60vtba2x9VOdgO5DvbsTOtKto7QSERTLdirMTicJVndw@mail.gmail.com>
 <CA+RQFfejKis42OKnj8YaeFr4d_HOcTT1PuF_WhOREso8K9KaOg@mail.gmail.com>
 <CAG5Cgtqj8Svx77QK9eA7pPSFnfbpA1fKUCa_YbmOqGRvowz69g@mail.gmail.com>
 <CAO-2QM5kYzEgMe=5cEBVAegfxc-=HEyF37xQDSa5QSbT_Y3Hyg@mail.gmail.com>
 <20170125084719.dnwea7zpetto4s5y@merlinux.eu>
 <CA+RQFfdFU9GHaPG-d55OJzKBXwv9gm19=qhSEn1WyzCdjto=2Q@mail.gmail.com>
 <20170125110405.ohlbms2rahdxwwsy@tonks>
 <CAO-2QM72gmukFM8pkijnj=1vxW-5au=bjLiQ27-onzcGba0j6Q@mail.gmail.com>
 <CAG5CgtoeSXpP55O=+YaJSyNN48X_nSN+Y_9CUZx2rv1ffyY8VA@mail.gmail.com>
 <CAO-2QM43UojCb3Vr-KJ1s2dKv-gRoxnvPc7Cs6cRy+eLv9Omzg@mail.gmail.com>
Message-ID: <CA+RQFff50EjvBiQ+LzTo7enVh7YpOBCm0wi1WrLeyB1j6AKB-Q@mail.gmail.com>

Hi Ana,

Thanks for continuing to pursue this!

On Tue, Feb 7, 2017 at 9:01 PM Ana Ribeiro <aninhacostaribeiro at gmail.com>
wrote:

> Hello,
>
> I asked them how we could apply as a Python suborg. We have to create an
> idea page until March 7 following this template (
> https://wiki.python.org/moin/SummerOfCode/OrgIdeasPageTemplate) and send
> it to Python.  gsoc-admins(at)python.org.
>


> So if anyone has an idea for a summer project for any Pytest project, even
> plugins or other smaller projects, I invite you to write to this list.
>

One topic that comes to mind is the long awaited feature to allow
controlling how tests are distributed among workers:
https://github.com/pytest-dev/pytest-xdist/issues/18: it has the benefits
of having a well defined scope and documentation on how it should work.

Cheers,
Bruno.


> Best regards,
> Ana
>
> 2017-01-25 12:00 GMT-03:00 Oliver Bestwalter <oliver at bestwalter.de>:
>
> Hello,
>
> o.k. sounds all good to me then.
>
> I have a topic in mind already that could nicely be tackled which is what
> we started to draft already as part of the sprint:
> https://github.com/tox-dev/tox/blob/master/doc/drafts/extend-envs-and-packagebuilds.md
> - if we find a dedicated individual who wants to get their feet wet with
> this topic, I actually start to get quite enthusiastic about the whole idea
> :)
>
> One caveat though: I am quite a catastrophe when it comes to classical
> admin things like filling out forms and stuff - so if this would be part of
> my work as a mentor, I will have to ask for a mentor myself to learn to
> better tackle these things ;)
>
> Cheers
> Oliver
>
> On Wed, 25 Jan 2017 at 12:31 Ana Ribeiro <aninhacostaribeiro at gmail.com>
> wrote:
>
> Hello,
>
> Sorry, when I read the email too quickly and I thought of the browser
> (Tor) instead of Tox (shame)... For sure, I have used Tox on my internship.
>
> About bad experiences, they may happen, but good experiences may happen as
> well... In Mozilla Outreachy program, they had a good application process
> in my opinion, we had to solve a small issue together our mentor, so we
> could see if this partnership would work well. In GSoC we can decide how we
> are going to take the application process, so I think it is a good way.
>
> About how to apply as a suborg of python, I may ask them on IRC and come
> here with more information.
>
> Best regards,
> Ana
>
> 2017-01-25 8:04 GMT-03:00 Florian Bruhin <me at the-compiler.org>:
>
> * Bruno Oliveira <nicoddemus at gmail.com> [2017-01-25 10:27:09 +0000]:
> > On Wed, Jan 25, 2017 at 6:47 AM holger krekel <holger at merlinux.eu>
> wrote:
> >
> > > I'll leave the question of if/how to apply as org/suborg to others
> > > as i am not bound to mentor myself (see my other post).
> > >
> >
> > Which post do you mean Holger? I didn't receive any other reply from you
> to
> > this thread. Perhaps you sent it only to Ana by accident?
>
> I did, and it's in the archive too:
> https://mail.python.org/pipermail/pytest-dev/2017-January/003985.html
>
> 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
>
>
> _______________________________________________
> 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/20170208/185d14e2/attachment-0001.html>

From aninhacostaribeiro at gmail.com  Tue Feb  7 22:46:41 2017
From: aninhacostaribeiro at gmail.com (Ana Ribeiro)
Date: Wed, 8 Feb 2017 00:46:41 -0300
Subject: [pytest-dev] Google Summer of Code
In-Reply-To: <CA+RQFff50EjvBiQ+LzTo7enVh7YpOBCm0wi1WrLeyB1j6AKB-Q@mail.gmail.com>
References: <CAO-2QM7xGuo78edg=1yWCwFYnkG=CpGigqMdAj-nQh9pBzwPyA@mail.gmail.com>
 <CA+RQFfduikX0trYb6udie1bY0nhuGJ9xrTM57s-wyjd5GwYO+Q@mail.gmail.com>
 <BD28797C-04FB-4908-9EC7-7108B2E822D0@mozilla.com>
 <CAO-2QM60vtba2x9VOdgO5DvbsTOtKto7QSERTLdirMTicJVndw@mail.gmail.com>
 <CA+RQFfejKis42OKnj8YaeFr4d_HOcTT1PuF_WhOREso8K9KaOg@mail.gmail.com>
 <CAG5Cgtqj8Svx77QK9eA7pPSFnfbpA1fKUCa_YbmOqGRvowz69g@mail.gmail.com>
 <CAO-2QM5kYzEgMe=5cEBVAegfxc-=HEyF37xQDSa5QSbT_Y3Hyg@mail.gmail.com>
 <20170125084719.dnwea7zpetto4s5y@merlinux.eu>
 <CA+RQFfdFU9GHaPG-d55OJzKBXwv9gm19=qhSEn1WyzCdjto=2Q@mail.gmail.com>
 <20170125110405.ohlbms2rahdxwwsy@tonks>
 <CAO-2QM72gmukFM8pkijnj=1vxW-5au=bjLiQ27-onzcGba0j6Q@mail.gmail.com>
 <CAG5CgtoeSXpP55O=+YaJSyNN48X_nSN+Y_9CUZx2rv1ffyY8VA@mail.gmail.com>
 <CAO-2QM43UojCb3Vr-KJ1s2dKv-gRoxnvPc7Cs6cRy+eLv9Omzg@mail.gmail.com>
 <CA+RQFff50EjvBiQ+LzTo7enVh7YpOBCm0wi1WrLeyB1j6AKB-Q@mail.gmail.com>
Message-ID: <CAO-2QM6LRW-SsAiNz12c6To5+4PqvFkvk+Yz1EEUNHsz=7JhCQ@mail.gmail.com>

Hello,

I created a first version of an idea's list page in our wiki:
https://wiki.python.org/moin/SummerOfCode/ApplicationTemplate2016, I put
there some of the observations listed in this topic. Please review and
comment.

Best regards,
Ana

2017-02-07 23:08 GMT-03:00 Bruno Oliveira <nicoddemus at gmail.com>:

>
> Hi Ana,
>
> Thanks for continuing to pursue this!
>
> On Tue, Feb 7, 2017 at 9:01 PM Ana Ribeiro <aninhacostaribeiro at gmail.com>
> wrote:
>
>> Hello,
>>
>> I asked them how we could apply as a Python suborg. We have to create an
>> idea page until March 7 following this template (
>> https://wiki.python.org/moin/SummerOfCode/OrgIdeasPageTemplate) and send
>> it to Python.  gsoc-admins(at)python.org.
>>
>
>
>> So if anyone has an idea for a summer project for any Pytest project,
>> even plugins or other smaller projects, I invite you to write to this list.
>>
>
> One topic that comes to mind is the long awaited feature to allow
> controlling how tests are distributed among workers:
> https://github.com/pytest-dev/pytest-xdist/issues/18: it has the benefits
> of having a well defined scope and documentation on how it should work.
>
> Cheers,
> Bruno.
>
>
>> Best regards,
>> Ana
>>
>> 2017-01-25 12:00 GMT-03:00 Oliver Bestwalter <oliver at bestwalter.de>:
>>
>> Hello,
>>
>> o.k. sounds all good to me then.
>>
>> I have a topic in mind already that could nicely be tackled which is what
>> we started to draft already as part of the sprint:
>> https://github.com/tox-dev/tox/blob/master/doc/drafts/
>> extend-envs-and-packagebuilds.md - if we find a dedicated individual who
>> wants to get their feet wet with this topic, I actually start to get quite
>> enthusiastic about the whole idea :)
>>
>> One caveat though: I am quite a catastrophe when it comes to classical
>> admin things like filling out forms and stuff - so if this would be part of
>> my work as a mentor, I will have to ask for a mentor myself to learn to
>> better tackle these things ;)
>>
>> Cheers
>> Oliver
>>
>> On Wed, 25 Jan 2017 at 12:31 Ana Ribeiro <aninhacostaribeiro at gmail.com>
>> wrote:
>>
>> Hello,
>>
>> Sorry, when I read the email too quickly and I thought of the browser
>> (Tor) instead of Tox (shame)... For sure, I have used Tox on my internship.
>>
>> About bad experiences, they may happen, but good experiences may happen
>> as well... In Mozilla Outreachy program, they had a good application
>> process in my opinion, we had to solve a small issue together our mentor,
>> so we could see if this partnership would work well. In GSoC we can decide
>> how we are going to take the application process, so I think it is a good
>> way.
>>
>> About how to apply as a suborg of python, I may ask them on IRC and come
>> here with more information.
>>
>> Best regards,
>> Ana
>>
>> 2017-01-25 8:04 GMT-03:00 Florian Bruhin <me at the-compiler.org>:
>>
>> * Bruno Oliveira <nicoddemus at gmail.com> [2017-01-25 10:27:09 +0000]:
>> > On Wed, Jan 25, 2017 at 6:47 AM holger krekel <holger at merlinux.eu>
>> wrote:
>> >
>> > > I'll leave the question of if/how to apply as org/suborg to others
>> > > as i am not bound to mentor myself (see my other post).
>> > >
>> >
>> > Which post do you mean Holger? I didn't receive any other reply from
>> you to
>> > this thread. Perhaps you sent it only to Ana by accident?
>>
>> I did, and it's in the archive too:
>> https://mail.python.org/pipermail/pytest-dev/2017-January/003985.html
>>
>> 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
>>
>>
>> _______________________________________________
>> 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/20170208/70a617d4/attachment-0001.html>

From aninhacostaribeiro at gmail.com  Tue Feb  7 22:47:14 2017
From: aninhacostaribeiro at gmail.com (Ana Ribeiro)
Date: Wed, 8 Feb 2017 00:47:14 -0300
Subject: [pytest-dev] Google Summer of Code
In-Reply-To: <CAO-2QM6LRW-SsAiNz12c6To5+4PqvFkvk+Yz1EEUNHsz=7JhCQ@mail.gmail.com>
References: <CAO-2QM7xGuo78edg=1yWCwFYnkG=CpGigqMdAj-nQh9pBzwPyA@mail.gmail.com>
 <CA+RQFfduikX0trYb6udie1bY0nhuGJ9xrTM57s-wyjd5GwYO+Q@mail.gmail.com>
 <BD28797C-04FB-4908-9EC7-7108B2E822D0@mozilla.com>
 <CAO-2QM60vtba2x9VOdgO5DvbsTOtKto7QSERTLdirMTicJVndw@mail.gmail.com>
 <CA+RQFfejKis42OKnj8YaeFr4d_HOcTT1PuF_WhOREso8K9KaOg@mail.gmail.com>
 <CAG5Cgtqj8Svx77QK9eA7pPSFnfbpA1fKUCa_YbmOqGRvowz69g@mail.gmail.com>
 <CAO-2QM5kYzEgMe=5cEBVAegfxc-=HEyF37xQDSa5QSbT_Y3Hyg@mail.gmail.com>
 <20170125084719.dnwea7zpetto4s5y@merlinux.eu>
 <CA+RQFfdFU9GHaPG-d55OJzKBXwv9gm19=qhSEn1WyzCdjto=2Q@mail.gmail.com>
 <20170125110405.ohlbms2rahdxwwsy@tonks>
 <CAO-2QM72gmukFM8pkijnj=1vxW-5au=bjLiQ27-onzcGba0j6Q@mail.gmail.com>
 <CAG5CgtoeSXpP55O=+YaJSyNN48X_nSN+Y_9CUZx2rv1ffyY8VA@mail.gmail.com>
 <CAO-2QM43UojCb3Vr-KJ1s2dKv-gRoxnvPc7Cs6cRy+eLv9Omzg@mail.gmail.com>
 <CA+RQFff50EjvBiQ+LzTo7enVh7YpOBCm0wi1WrLeyB1j6AKB-Q@mail.gmail.com>
 <CAO-2QM6LRW-SsAiNz12c6To5+4PqvFkvk+Yz1EEUNHsz=7JhCQ@mail.gmail.com>
Message-ID: <CAO-2QM5PCwHY5-fJp72xsQJoScXxPP31_a0LpogRgFg4ecTscg@mail.gmail.com>

Sorry, wrong link. This one is the correct one:
https://github.com/pytest-dev/pytest/wiki/GSoC-2017

2017-02-08 0:46 GMT-03:00 Ana Ribeiro <aninhacostaribeiro at gmail.com>:

> Hello,
>
> I created a first version of an idea's list page in our wiki:
> https://wiki.python.org/moin/SummerOfCode/ApplicationTemplate2016, I put
> there some of the observations listed in this topic. Please review and
> comment.
>
> Best regards,
> Ana
>
> 2017-02-07 23:08 GMT-03:00 Bruno Oliveira <nicoddemus at gmail.com>:
>
>>
>> Hi Ana,
>>
>> Thanks for continuing to pursue this!
>>
>> On Tue, Feb 7, 2017 at 9:01 PM Ana Ribeiro <aninhacostaribeiro at gmail.com>
>> wrote:
>>
>>> Hello,
>>>
>>> I asked them how we could apply as a Python suborg. We have to create an
>>> idea page until March 7 following this template (
>>> https://wiki.python.org/moin/SummerOfCode/OrgIdeasPageTemplate) and
>>> send it to Python.  gsoc-admins(at)python.org.
>>>
>>
>>
>>> So if anyone has an idea for a summer project for any Pytest project,
>>> even plugins or other smaller projects, I invite you to write to this list.
>>>
>>
>> One topic that comes to mind is the long awaited feature to allow
>> controlling how tests are distributed among workers:
>> https://github.com/pytest-dev/pytest-xdist/issues/18: it has the
>> benefits of having a well defined scope and documentation on how it should
>> work.
>>
>> Cheers,
>> Bruno.
>>
>>
>>> Best regards,
>>> Ana
>>>
>>> 2017-01-25 12:00 GMT-03:00 Oliver Bestwalter <oliver at bestwalter.de>:
>>>
>>> Hello,
>>>
>>> o.k. sounds all good to me then.
>>>
>>> I have a topic in mind already that could nicely be tackled which is
>>> what we started to draft already as part of the sprint:
>>> https://github.com/tox-dev/tox/blob/master/doc/drafts/extend
>>> -envs-and-packagebuilds.md - if we find a dedicated individual who
>>> wants to get their feet wet with this topic, I actually start to get quite
>>> enthusiastic about the whole idea :)
>>>
>>> One caveat though: I am quite a catastrophe when it comes to classical
>>> admin things like filling out forms and stuff - so if this would be part of
>>> my work as a mentor, I will have to ask for a mentor myself to learn to
>>> better tackle these things ;)
>>>
>>> Cheers
>>> Oliver
>>>
>>> On Wed, 25 Jan 2017 at 12:31 Ana Ribeiro <aninhacostaribeiro at gmail.com>
>>> wrote:
>>>
>>> Hello,
>>>
>>> Sorry, when I read the email too quickly and I thought of the browser
>>> (Tor) instead of Tox (shame)... For sure, I have used Tox on my internship.
>>>
>>> About bad experiences, they may happen, but good experiences may happen
>>> as well... In Mozilla Outreachy program, they had a good application
>>> process in my opinion, we had to solve a small issue together our mentor,
>>> so we could see if this partnership would work well. In GSoC we can decide
>>> how we are going to take the application process, so I think it is a good
>>> way.
>>>
>>> About how to apply as a suborg of python, I may ask them on IRC and come
>>> here with more information.
>>>
>>> Best regards,
>>> Ana
>>>
>>> 2017-01-25 8:04 GMT-03:00 Florian Bruhin <me at the-compiler.org>:
>>>
>>> * Bruno Oliveira <nicoddemus at gmail.com> [2017-01-25 10:27:09 +0000]:
>>> > On Wed, Jan 25, 2017 at 6:47 AM holger krekel <holger at merlinux.eu>
>>> wrote:
>>> >
>>> > > I'll leave the question of if/how to apply as org/suborg to others
>>> > > as i am not bound to mentor myself (see my other post).
>>> > >
>>> >
>>> > Which post do you mean Holger? I didn't receive any other reply from
>>> you to
>>> > this thread. Perhaps you sent it only to Ana by accident?
>>>
>>> I did, and it's in the archive too:
>>> https://mail.python.org/pipermail/pytest-dev/2017-January/003985.html
>>>
>>> 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
>>>
>>>
>>> _______________________________________________
>>> 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/20170208/158a9168/attachment-0001.html>

From nicoddemus at gmail.com  Wed Feb  8 09:48:49 2017
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Wed, 08 Feb 2017 14:48:49 +0000
Subject: [pytest-dev] Google Summer of Code
In-Reply-To: <CAO-2QM5PCwHY5-fJp72xsQJoScXxPP31_a0LpogRgFg4ecTscg@mail.gmail.com>
References: <CAO-2QM7xGuo78edg=1yWCwFYnkG=CpGigqMdAj-nQh9pBzwPyA@mail.gmail.com>
 <CA+RQFfduikX0trYb6udie1bY0nhuGJ9xrTM57s-wyjd5GwYO+Q@mail.gmail.com>
 <BD28797C-04FB-4908-9EC7-7108B2E822D0@mozilla.com>
 <CAO-2QM60vtba2x9VOdgO5DvbsTOtKto7QSERTLdirMTicJVndw@mail.gmail.com>
 <CA+RQFfejKis42OKnj8YaeFr4d_HOcTT1PuF_WhOREso8K9KaOg@mail.gmail.com>
 <CAG5Cgtqj8Svx77QK9eA7pPSFnfbpA1fKUCa_YbmOqGRvowz69g@mail.gmail.com>
 <CAO-2QM5kYzEgMe=5cEBVAegfxc-=HEyF37xQDSa5QSbT_Y3Hyg@mail.gmail.com>
 <20170125084719.dnwea7zpetto4s5y@merlinux.eu>
 <CA+RQFfdFU9GHaPG-d55OJzKBXwv9gm19=qhSEn1WyzCdjto=2Q@mail.gmail.com>
 <20170125110405.ohlbms2rahdxwwsy@tonks>
 <CAO-2QM72gmukFM8pkijnj=1vxW-5au=bjLiQ27-onzcGba0j6Q@mail.gmail.com>
 <CAG5CgtoeSXpP55O=+YaJSyNN48X_nSN+Y_9CUZx2rv1ffyY8VA@mail.gmail.com>
 <CAO-2QM43UojCb3Vr-KJ1s2dKv-gRoxnvPc7Cs6cRy+eLv9Omzg@mail.gmail.com>
 <CA+RQFff50EjvBiQ+LzTo7enVh7YpOBCm0wi1WrLeyB1j6AKB-Q@mail.gmail.com>
 <CAO-2QM6LRW-SsAiNz12c6To5+4PqvFkvk+Yz1EEUNHsz=7JhCQ@mail.gmail.com>
 <CAO-2QM5PCwHY5-fJp72xsQJoScXxPP31_a0LpogRgFg4ecTscg@mail.gmail.com>
Message-ID: <CA+RQFfcshbP69tbWOTXdK8oKaN4QXsDVCT08B8k=qVjq4Jh0NQ@mail.gmail.com>

On Wed, Feb 8, 2017 at 1:47 AM Ana Ribeiro <aninhacostaribeiro at gmail.com>
wrote:

> Sorry, wrong link. This one is the correct one:
> https://github.com/pytest-dev/pytest/wiki/GSoC-2017
>

Thanks Ana. I updated the item 1 with difficulty level and added myself as
possible mentor, but others please feel free to add themselves as well.

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

From oliver at bestwalter.de  Fri Feb 10 08:52:06 2017
From: oliver at bestwalter.de (Oliver Bestwalter)
Date: Fri, 10 Feb 2017 13:52:06 +0000
Subject: [pytest-dev] Google Summer of Code
In-Reply-To: <CA+RQFfcshbP69tbWOTXdK8oKaN4QXsDVCT08B8k=qVjq4Jh0NQ@mail.gmail.com>
References: <CAO-2QM7xGuo78edg=1yWCwFYnkG=CpGigqMdAj-nQh9pBzwPyA@mail.gmail.com>
 <CA+RQFfduikX0trYb6udie1bY0nhuGJ9xrTM57s-wyjd5GwYO+Q@mail.gmail.com>
 <BD28797C-04FB-4908-9EC7-7108B2E822D0@mozilla.com>
 <CAO-2QM60vtba2x9VOdgO5DvbsTOtKto7QSERTLdirMTicJVndw@mail.gmail.com>
 <CA+RQFfejKis42OKnj8YaeFr4d_HOcTT1PuF_WhOREso8K9KaOg@mail.gmail.com>
 <CAG5Cgtqj8Svx77QK9eA7pPSFnfbpA1fKUCa_YbmOqGRvowz69g@mail.gmail.com>
 <CAO-2QM5kYzEgMe=5cEBVAegfxc-=HEyF37xQDSa5QSbT_Y3Hyg@mail.gmail.com>
 <20170125084719.dnwea7zpetto4s5y@merlinux.eu>
 <CA+RQFfdFU9GHaPG-d55OJzKBXwv9gm19=qhSEn1WyzCdjto=2Q@mail.gmail.com>
 <20170125110405.ohlbms2rahdxwwsy@tonks>
 <CAO-2QM72gmukFM8pkijnj=1vxW-5au=bjLiQ27-onzcGba0j6Q@mail.gmail.com>
 <CAG5CgtoeSXpP55O=+YaJSyNN48X_nSN+Y_9CUZx2rv1ffyY8VA@mail.gmail.com>
 <CAO-2QM43UojCb3Vr-KJ1s2dKv-gRoxnvPc7Cs6cRy+eLv9Omzg@mail.gmail.com>
 <CA+RQFff50EjvBiQ+LzTo7enVh7YpOBCm0wi1WrLeyB1j6AKB-Q@mail.gmail.com>
 <CAO-2QM6LRW-SsAiNz12c6To5+4PqvFkvk+Yz1EEUNHsz=7JhCQ@mail.gmail.com>
 <CAO-2QM5PCwHY5-fJp72xsQJoScXxPP31_a0LpogRgFg4ecTscg@mail.gmail.com>
 <CA+RQFfcshbP69tbWOTXdK8oKaN4QXsDVCT08B8k=qVjq4Jh0NQ@mail.gmail.com>
Message-ID: <CAG5Cgtr0S03bRBCAP84vvDJ0UkM-WerPvWS7q4g97_QisLubVw@mail.gmail.com>

Hi all,

I had a closer look at the timeline and what is involved and I think I
would overreach myself if I would volunteer as a mentor this year already.
I am basically a newbie to tox myself, so I better buckle down a bit first.
I guess I will feel up to the task next year then.

If students want to work explicitly on tox and someone wants to mentor I
would suggest:

Generalize package builds and virtualenv creation:
https://github.com/tox-dev/tox/issues/338

as an interesting topic to tackle.

Cheers
Oliver

On Wed, 8 Feb 2017 at 15:49 Bruno Oliveira <nicoddemus at gmail.com> wrote:

> On Wed, Feb 8, 2017 at 1:47 AM Ana Ribeiro <aninhacostaribeiro at gmail.com>
> wrote:
>
> Sorry, wrong link. This one is the correct one:
> https://github.com/pytest-dev/pytest/wiki/GSoC-2017
>
>
> Thanks Ana. I updated the item 1 with difficulty level and added myself as
> possible mentor, but others please feel free to add themselves as well.
>
> Cheers,
> Bruno.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20170210/f437d877/attachment.html>

From nicoddemus at gmail.com  Fri Feb 10 09:45:24 2017
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Fri, 10 Feb 2017 14:45:24 +0000
Subject: [pytest-dev] Google Summer of Code
In-Reply-To: <CAG5Cgtr0S03bRBCAP84vvDJ0UkM-WerPvWS7q4g97_QisLubVw@mail.gmail.com>
References: <CAO-2QM7xGuo78edg=1yWCwFYnkG=CpGigqMdAj-nQh9pBzwPyA@mail.gmail.com>
 <CA+RQFfduikX0trYb6udie1bY0nhuGJ9xrTM57s-wyjd5GwYO+Q@mail.gmail.com>
 <BD28797C-04FB-4908-9EC7-7108B2E822D0@mozilla.com>
 <CAO-2QM60vtba2x9VOdgO5DvbsTOtKto7QSERTLdirMTicJVndw@mail.gmail.com>
 <CA+RQFfejKis42OKnj8YaeFr4d_HOcTT1PuF_WhOREso8K9KaOg@mail.gmail.com>
 <CAG5Cgtqj8Svx77QK9eA7pPSFnfbpA1fKUCa_YbmOqGRvowz69g@mail.gmail.com>
 <CAO-2QM5kYzEgMe=5cEBVAegfxc-=HEyF37xQDSa5QSbT_Y3Hyg@mail.gmail.com>
 <20170125084719.dnwea7zpetto4s5y@merlinux.eu>
 <CA+RQFfdFU9GHaPG-d55OJzKBXwv9gm19=qhSEn1WyzCdjto=2Q@mail.gmail.com>
 <20170125110405.ohlbms2rahdxwwsy@tonks>
 <CAO-2QM72gmukFM8pkijnj=1vxW-5au=bjLiQ27-onzcGba0j6Q@mail.gmail.com>
 <CAG5CgtoeSXpP55O=+YaJSyNN48X_nSN+Y_9CUZx2rv1ffyY8VA@mail.gmail.com>
 <CAO-2QM43UojCb3Vr-KJ1s2dKv-gRoxnvPc7Cs6cRy+eLv9Omzg@mail.gmail.com>
 <CA+RQFff50EjvBiQ+LzTo7enVh7YpOBCm0wi1WrLeyB1j6AKB-Q@mail.gmail.com>
 <CAO-2QM6LRW-SsAiNz12c6To5+4PqvFkvk+Yz1EEUNHsz=7JhCQ@mail.gmail.com>
 <CAO-2QM5PCwHY5-fJp72xsQJoScXxPP31_a0LpogRgFg4ecTscg@mail.gmail.com>
 <CA+RQFfcshbP69tbWOTXdK8oKaN4QXsDVCT08B8k=qVjq4Jh0NQ@mail.gmail.com>
 <CAG5Cgtr0S03bRBCAP84vvDJ0UkM-WerPvWS7q4g97_QisLubVw@mail.gmail.com>
Message-ID: <CA+RQFfe_4a7xFcESkbDOe68mgCnF2xbtFo4yYTMx-_hxjq=nHg@mail.gmail.com>

Hi Walter, :)

On Fri, Feb 10, 2017 at 11:52 AM Oliver Bestwalter <oliver at bestwalter.de>
wrote:

> If students want to work explicitly on tox and someone wants to mentor I
> would suggest:
>
> Generalize package builds and virtualenv creation:
> https://github.com/tox-dev/tox/issues/338
>
> as an interesting topic to tackle.
>

Agreed. Would you mind adding that topic to the WiKi?
https://github.com/pytest-dev/pytest/wiki/GSoC-2017 You can leave "possible
mentors" blank for now.

Cheers,
Bruno.

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

From rpfannsc at redhat.com  Fri Feb 10 10:37:16 2017
From: rpfannsc at redhat.com (Ronny Pfannschmidt)
Date: Fri, 10 Feb 2017 16:37:16 +0100
Subject: [pytest-dev] Google Summer of Code
In-Reply-To: <CA+RQFfe_4a7xFcESkbDOe68mgCnF2xbtFo4yYTMx-_hxjq=nHg@mail.gmail.com>
References: <CAO-2QM7xGuo78edg=1yWCwFYnkG=CpGigqMdAj-nQh9pBzwPyA@mail.gmail.com>
 <CA+RQFfduikX0trYb6udie1bY0nhuGJ9xrTM57s-wyjd5GwYO+Q@mail.gmail.com>
 <BD28797C-04FB-4908-9EC7-7108B2E822D0@mozilla.com>
 <CAO-2QM60vtba2x9VOdgO5DvbsTOtKto7QSERTLdirMTicJVndw@mail.gmail.com>
 <CA+RQFfejKis42OKnj8YaeFr4d_HOcTT1PuF_WhOREso8K9KaOg@mail.gmail.com>
 <CAG5Cgtqj8Svx77QK9eA7pPSFnfbpA1fKUCa_YbmOqGRvowz69g@mail.gmail.com>
 <CAO-2QM5kYzEgMe=5cEBVAegfxc-=HEyF37xQDSa5QSbT_Y3Hyg@mail.gmail.com>
 <20170125084719.dnwea7zpetto4s5y@merlinux.eu>
 <CA+RQFfdFU9GHaPG-d55OJzKBXwv9gm19=qhSEn1WyzCdjto=2Q@mail.gmail.com>
 <20170125110405.ohlbms2rahdxwwsy@tonks>
 <CAO-2QM72gmukFM8pkijnj=1vxW-5au=bjLiQ27-onzcGba0j6Q@mail.gmail.com>
 <CAG5CgtoeSXpP55O=+YaJSyNN48X_nSN+Y_9CUZx2rv1ffyY8VA@mail.gmail.com>
 <CAO-2QM43UojCb3Vr-KJ1s2dKv-gRoxnvPc7Cs6cRy+eLv9Omzg@mail.gmail.com>
 <CA+RQFff50EjvBiQ+LzTo7enVh7YpOBCm0wi1WrLeyB1j6AKB-Q@mail.gmail.com>
 <CAO-2QM6LRW-SsAiNz12c6To5+4PqvFkvk+Yz1EEUNHsz=7JhCQ@mail.gmail.com>
 <CAO-2QM5PCwHY5-fJp72xsQJoScXxPP31_a0LpogRgFg4ecTscg@mail.gmail.com>
 <CA+RQFfcshbP69tbWOTXdK8oKaN4QXsDVCT08B8k=qVjq4Jh0NQ@mail.gmail.com>
 <CAG5Cgtr0S03bRBCAP84vvDJ0UkM-WerPvWS7q4g97_QisLubVw@mail.gmail.com>
 <CA+RQFfe_4a7xFcESkbDOe68mgCnF2xbtFo4yYTMx-_hxjq=nHg@mail.gmail.com>
Message-ID: <CAA10jzMU39ZdUbKMSLvhdZQv1owHr4tmaSNjZh8bUbjxnbTQFQ@mail.gmail.com>

please note that tackling "fixtures in distribution" with the current state
of xdist we will very likely push much further into the direction of an
"unmanageable mess"

-- Ronny

2017-02-10 15:45 GMT+01:00 Bruno Oliveira <nicoddemus at gmail.com>:

> Hi Walter, :)
>
> On Fri, Feb 10, 2017 at 11:52 AM Oliver Bestwalter <oliver at bestwalter.de>
> wrote:
>
>> If students want to work explicitly on tox and someone wants to mentor I
>> would suggest:
>>
>> Generalize package builds and virtualenv creation:
>> https://github.com/tox-dev/tox/issues/338
>>
>> as an interesting topic to tackle.
>>
>
> Agreed. Would you mind adding that topic to the WiKi?
> https://github.com/pytest-dev/pytest/wiki/GSoC-2017 You can leave
> "possible mentors" blank for now.
>
> Cheers,
> Bruno.
>
>>
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
>


-- 

Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael
O'Neill, Eric Shander
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20170210/e7162e8e/attachment.html>

From oliver at bestwalter.de  Fri Feb 10 10:20:53 2017
From: oliver at bestwalter.de (Oliver Bestwalter)
Date: Fri, 10 Feb 2017 15:20:53 +0000
Subject: [pytest-dev] Google Summer of Code
In-Reply-To: <CA+RQFfe_4a7xFcESkbDOe68mgCnF2xbtFo4yYTMx-_hxjq=nHg@mail.gmail.com>
References: <CAO-2QM7xGuo78edg=1yWCwFYnkG=CpGigqMdAj-nQh9pBzwPyA@mail.gmail.com>
 <CA+RQFfduikX0trYb6udie1bY0nhuGJ9xrTM57s-wyjd5GwYO+Q@mail.gmail.com>
 <BD28797C-04FB-4908-9EC7-7108B2E822D0@mozilla.com>
 <CAO-2QM60vtba2x9VOdgO5DvbsTOtKto7QSERTLdirMTicJVndw@mail.gmail.com>
 <CA+RQFfejKis42OKnj8YaeFr4d_HOcTT1PuF_WhOREso8K9KaOg@mail.gmail.com>
 <CAG5Cgtqj8Svx77QK9eA7pPSFnfbpA1fKUCa_YbmOqGRvowz69g@mail.gmail.com>
 <CAO-2QM5kYzEgMe=5cEBVAegfxc-=HEyF37xQDSa5QSbT_Y3Hyg@mail.gmail.com>
 <20170125084719.dnwea7zpetto4s5y@merlinux.eu>
 <CA+RQFfdFU9GHaPG-d55OJzKBXwv9gm19=qhSEn1WyzCdjto=2Q@mail.gmail.com>
 <20170125110405.ohlbms2rahdxwwsy@tonks>
 <CAO-2QM72gmukFM8pkijnj=1vxW-5au=bjLiQ27-onzcGba0j6Q@mail.gmail.com>
 <CAG5CgtoeSXpP55O=+YaJSyNN48X_nSN+Y_9CUZx2rv1ffyY8VA@mail.gmail.com>
 <CAO-2QM43UojCb3Vr-KJ1s2dKv-gRoxnvPc7Cs6cRy+eLv9Omzg@mail.gmail.com>
 <CA+RQFff50EjvBiQ+LzTo7enVh7YpOBCm0wi1WrLeyB1j6AKB-Q@mail.gmail.com>
 <CAO-2QM6LRW-SsAiNz12c6To5+4PqvFkvk+Yz1EEUNHsz=7JhCQ@mail.gmail.com>
 <CAO-2QM5PCwHY5-fJp72xsQJoScXxPP31_a0LpogRgFg4ecTscg@mail.gmail.com>
 <CA+RQFfcshbP69tbWOTXdK8oKaN4QXsDVCT08B8k=qVjq4Jh0NQ@mail.gmail.com>
 <CAG5Cgtr0S03bRBCAP84vvDJ0UkM-WerPvWS7q4g97_QisLubVw@mail.gmail.com>
 <CA+RQFfe_4a7xFcESkbDOe68mgCnF2xbtFo4yYTMx-_hxjq=nHg@mail.gmail.com>
Message-ID: <CAG5CgtqM5gbuAr3Mbz2M-NjwrqsyocOPPQwvZFDGu_881kTfOQ@mail.gmail.com>

Hey Oliviera!

done :D

On Fri, 10 Feb 2017 at 15:45 Bruno Oliveira <nicoddemus at gmail.com> wrote:

> Hi Walter, :)
>
> On Fri, Feb 10, 2017 at 11:52 AM Oliver Bestwalter <oliver at bestwalter.de>
> wrote:
>
> If students want to work explicitly on tox and someone wants to mentor I
> would suggest:
>
> Generalize package builds and virtualenv creation:
> https://github.com/tox-dev/tox/issues/338
>
> as an interesting topic to tackle.
>
>
> Agreed. Would you mind adding that topic to the WiKi?
> https://github.com/pytest-dev/pytest/wiki/GSoC-2017 You can leave
> "possible mentors" blank for now.
>
> Cheers,
> Bruno.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20170210/00abfe4c/attachment-0001.html>

From oliver at bestwalter.de  Fri Feb 10 10:23:36 2017
From: oliver at bestwalter.de (Oliver Bestwalter)
Date: Fri, 10 Feb 2017 15:23:36 +0000
Subject: [pytest-dev] Google Summer of Code
In-Reply-To: <CAG5CgtqM5gbuAr3Mbz2M-NjwrqsyocOPPQwvZFDGu_881kTfOQ@mail.gmail.com>
References: <CAO-2QM7xGuo78edg=1yWCwFYnkG=CpGigqMdAj-nQh9pBzwPyA@mail.gmail.com>
 <CA+RQFfduikX0trYb6udie1bY0nhuGJ9xrTM57s-wyjd5GwYO+Q@mail.gmail.com>
 <BD28797C-04FB-4908-9EC7-7108B2E822D0@mozilla.com>
 <CAO-2QM60vtba2x9VOdgO5DvbsTOtKto7QSERTLdirMTicJVndw@mail.gmail.com>
 <CA+RQFfejKis42OKnj8YaeFr4d_HOcTT1PuF_WhOREso8K9KaOg@mail.gmail.com>
 <CAG5Cgtqj8Svx77QK9eA7pPSFnfbpA1fKUCa_YbmOqGRvowz69g@mail.gmail.com>
 <CAO-2QM5kYzEgMe=5cEBVAegfxc-=HEyF37xQDSa5QSbT_Y3Hyg@mail.gmail.com>
 <20170125084719.dnwea7zpetto4s5y@merlinux.eu>
 <CA+RQFfdFU9GHaPG-d55OJzKBXwv9gm19=qhSEn1WyzCdjto=2Q@mail.gmail.com>
 <20170125110405.ohlbms2rahdxwwsy@tonks>
 <CAO-2QM72gmukFM8pkijnj=1vxW-5au=bjLiQ27-onzcGba0j6Q@mail.gmail.com>
 <CAG5CgtoeSXpP55O=+YaJSyNN48X_nSN+Y_9CUZx2rv1ffyY8VA@mail.gmail.com>
 <CAO-2QM43UojCb3Vr-KJ1s2dKv-gRoxnvPc7Cs6cRy+eLv9Omzg@mail.gmail.com>
 <CA+RQFff50EjvBiQ+LzTo7enVh7YpOBCm0wi1WrLeyB1j6AKB-Q@mail.gmail.com>
 <CAO-2QM6LRW-SsAiNz12c6To5+4PqvFkvk+Yz1EEUNHsz=7JhCQ@mail.gmail.com>
 <CAO-2QM5PCwHY5-fJp72xsQJoScXxPP31_a0LpogRgFg4ecTscg@mail.gmail.com>
 <CA+RQFfcshbP69tbWOTXdK8oKaN4QXsDVCT08B8k=qVjq4Jh0NQ@mail.gmail.com>
 <CAG5Cgtr0S03bRBCAP84vvDJ0UkM-WerPvWS7q4g97_QisLubVw@mail.gmail.com>
 <CA+RQFfe_4a7xFcESkbDOe68mgCnF2xbtFo4yYTMx-_hxjq=nHg@mail.gmail.com>
 <CAG5CgtqM5gbuAr3Mbz2M-NjwrqsyocOPPQwvZFDGu_881kTfOQ@mail.gmail.com>
Message-ID: <CAG5Cgtq3oxRmaRwmoTFwLV5jfLBOj-6=xtk11i5xTjC=D1a6AA@mail.gmail.com>

On Fri, 10 Feb 2017 at 16:21 Oliver Bestwalter <oliver at bestwalter.de> wrote:

Hey Oliviera!


[Note the subtle reordering of the letters to mark the way I pronounce this
in my head] - I'll see myself out now.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20170210/f84e8bea/attachment.html>

From flub at devork.be  Mon Feb 20 14:01:43 2017
From: flub at devork.be (Floris Bruynooghe)
Date: Mon, 20 Feb 2017 16:01:43 -0300
Subject: [pytest-dev] Reviving pytest-commit
Message-ID: <87h93ou1ns.fsf@powell.devork.be>

Hi all,

Those of you subscribed to pytest-commit may have noticed I tried to
revive it as it had been dead since the github migration.  On an
unrelated issue I noticed I actually used this a fair bit when it was
working.

Sadly github will only send us commit messages instead of full diffs by
default.  To get it to email full diffs we'd have to run a service
somewhere which github can poke as webhook or something, which seems a
bit a pain to setup and maintain.  If anyone is aware of an easier way
do speak up, otherwise I might not bother for now, unless lots of people
would want it.

Regards,
Floris

From me at the-compiler.org  Mon Feb 20 15:40:36 2017
From: me at the-compiler.org (Florian Bruhin)
Date: Mon, 20 Feb 2017 21:40:36 +0100
Subject: [pytest-dev] Reviving pytest-commit
In-Reply-To: <87h93ou1ns.fsf@powell.devork.be>
References: <87h93ou1ns.fsf@powell.devork.be>
Message-ID: <20170220204036.nmflmpgubwnmijy7@tonks>

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

FWIW there's this: https://github.com/mavam/gitdub

But it's Ruby, and Ruby stuff can be difficult to set up in my
experience.

FWIW, I wouldn't use it.

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: 833 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20170220/8d95f28c/attachment.sig>

From thomas at thomas-lotze.de  Mon Feb 20 16:41:54 2017
From: thomas at thomas-lotze.de (Thomas Lotze)
Date: Mon, 20 Feb 2017 22:41:54 +0100
Subject: [pytest-dev] Mozilla Open Source Support
Message-ID: <20170220224154.6fa55b58@alpha>

Hi,

I just noticed that the next deadline for applications for Mozilla Open
Source Support awards will be due soon, at the end of the month. Also,
pytest (as well as tox) is listed among the projects Mozilla considers
Foundational technology which it supports through a dedicated awards track.

https://wiki.mozilla.org/MOSS

https://wiki.mozilla.org/MOSS/Foundational_Technology/Projects_We_Use

I wonder whether the pytest project should apply for an award. This question
has been brought up on this mailing list before, at least last summer by
Florian Bruhin. The discussion back then didn't lead to a conclusion,
more-or-less open questions being what well-defined project objective to
propose, who could work on it, and, not the least important, what Holger
thought of it as the money would likely be handled by his company. Florian
Schulze was the only one who said he was available full-time at the time.

Now, I'm aware that I've not been known as a pytest contributor so far, but
I've been using pytest, I want to help improve it in turn, and I'm interested
in and available for working on open-source Python projects on the basis of
funding such as the MOSS awards. This is why I'd like to re-raise the
question of applying for such an award, and ask you who else might be
interested in joining the work and what would be the best objectives to have
funded.

"Reducing the number of bugs" would be useful but possibly too much of general
maintenance to be eligible for an award. There are a number of enhancement
proposals in the tracker, some of which will be more urgent or helpful to the
project than others, or might lend themselves better to being implemented by
one or two persons rather than, e.g., during a sprint.

If there is any interest in applying for a MOSS award, I'd be happy to work on
an application during the next few days. But if there is a feeling that
pytest shouldn't apply for an award, or not this time, I'd be equally
interested in discussing that and possibly preparing for next time. I'd
particularly like to ask the opinions of Holger, and of Dave Hunt, who is
listed as the project's contact within Mozilla on the above-mentioned list.

Thank you! Cheers,
Thomas

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20170220/eadb924a/attachment.sig>

From dhunt at mozilla.com  Tue Feb 21 03:51:37 2017
From: dhunt at mozilla.com (Dave Hunt)
Date: Tue, 21 Feb 2017 08:51:37 +0000
Subject: [pytest-dev] Mozilla Open Source Support
In-Reply-To: <20170220224154.6fa55b58@alpha>
References: <20170220224154.6fa55b58@alpha>
Message-ID: <D8D05C4E-586A-4055-BAF0-5AD2DDCD2A3D@mozilla.com>

I believe Raphael has applied for a MOSS award to work on the documentation. I?m happy to support this, or likely any other application.

Cheers,
Dave

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


From raphael at hackebrot.de  Sun Feb 26 17:03:16 2017
From: raphael at hackebrot.de (Raphael Pierzina)
Date: Sun, 26 Feb 2017 22:03:16 +0000
Subject: [pytest-dev] Mozilla Open Source Support
In-Reply-To: <D8D05C4E-586A-4055-BAF0-5AD2DDCD2A3D@mozilla.com>
References: <20170220224154.6fa55b58@alpha>
 <D8D05C4E-586A-4055-BAF0-5AD2DDCD2A3D@mozilla.com>
Message-ID: <DFD7E118-E92A-4E69-87A2-046C7B6FD7B9@hackebrot.de>

Hey there!

Dave is right about me being interested in applying for the MOSS grant. I have done some work for it last year and chatted to a few pytest contributors offlist for feedback.

I would like to pick up the work on the documentation [1] that Brianna, Andreas and myself started during the developer sprint in June, 2016. However I have come to realize that having a full-time job, I unfortunately don't have the time to revisit all of the docs, make sure the contents are up-to-date, move them around if need be and making sure any resulting pull requests get reviewed and merged in time.  

In December, I applied for a month-long Open Source Fellowship with Changelog and Hacker Paradise [2] to work on this. Unfortunately I was notified last week, that they had received a huge number of applications and that I was not selected for the fellowship this time.

Notwithstanding the above, I was hoping to use the MOSS grant to allow me and anyone who is interested to work on this effort full-time for a month or longer, depending on the amount we want to request.

I had not applied for the last round and I am not planning on doing so for this round either. The reason being, that the MOSS wiki clearly states that they "have a reasonably strong preference for funding legal organizations rather than individuals representing projects" (see [3] Project Criteria). I have looked into registering a non-profit in the UK or a Verein in Germany, but neither seems to be trivial being a German citizen living and working in the UK and members all over the globe. Also: "Recipients are responsible to determine the tax implications of receiving an award, based on their respective countries' tax laws and compliance requirements.".

I am aware that Holger took care of finances and these kinds of things in the past using his company, which allowed us to run a very successful fundraiser and more. However going forward, I believe setting up some sort of legal entity for pytest and related projects would be the right thing to do. It would allow us to share responsibilities and explore other ways of raising money for the project in the future (crowd-funding, stickers + t-shirts, donations etc.).

As to applying for the MOSS grant in general, I think it's crucial to have a good plan for what we would like to work on and also who exactly would like to be involved. The objectives need to be achievable and specific and people would need to be happy to commit to them. I personally think, it's important that such a project will be a success, otherwise we might cause damage to pytest's reputation and it might be harder to receive similar grants in the future. I also don't want this to be unfair to the Mozilla Champion. Afterall they have to vouch for us.

I think it's great that you, Thomas, use pytest and want to improve it! I suggest that you have a look at unresolved issues on the tracker and help fix some of them or give feedback on open pull requests. This will probably increase the chances of being awarded with the MOSS award, should you apply, and even if it doesn't work out as hoped it will be great to have you as a contributor!

Best,
Raphael

[1]: https://github.com/pytest-dev/pytest/wiki/Docs-refactor
[2]: http://www.hackerparadise.org/blog/2016/11/17/open-source-fellowship/
[3]: https://wiki.mozilla.org/MOSS/Foundational_Technology

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


From thomas at thomas-lotze.de  Mon Feb 27 04:43:19 2017
From: thomas at thomas-lotze.de (Thomas Lotze)
Date: Mon, 27 Feb 2017 10:43:19 +0100
Subject: [pytest-dev] Mozilla Open Source Support
In-Reply-To: <DFD7E118-E92A-4E69-87A2-046C7B6FD7B9@hackebrot.de>
References: <20170220224154.6fa55b58@alpha>
 <D8D05C4E-586A-4055-BAF0-5AD2DDCD2A3D@mozilla.com>
 <DFD7E118-E92A-4E69-87A2-046C7B6FD7B9@hackebrot.de>
Message-ID: <20170227104319.366b5896@krusty.ws.whq.gocept.com>

Hi Raphael,

thank you for your reply. Given the number of diverse concerns you confirm
or raise (previous plannings for funding the work on docs, the handling of
finances, the project's reputation etc), it first of all becomes pretty
clear that I'm not going to rush anything now before the impending deadline
of this round of MOSS awards.

Even though I was thinking of development work, I wouldn't object to
helping with the documentation. So my suggestion is to use the time until
the next round to clarify the financial stuff (I wouldn't think it's
necessary to set up a dedicated legal entity for this, but let's discuss
that with people who have done more of these things before), and then pick
up on the existing plans for documentation work and see who's willing to
join and what it would make sense to include in the proposal. (I could
imagine that some development stuff can be added which e.g. contributes to
the user experience, while still keeping the objective of the proposal
well-defined.)

I'll get back to the list about this in the next days. Thank you again for
putting the subject of the awards in a better perspective!

Cheers,
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20170227/ac268316/attachment.sig>