From xiao.xj at gmail.com  Thu Nov  3 22:33:38 2016
From: xiao.xj at gmail.com (Ted)
Date: Fri, 4 Nov 2016 10:33:38 +0800
Subject: [pytest-dev] T-Shirt has arrived!
In-Reply-To: <CAK7X-XCQxyPXgkLhv2QY7zDmSOiXaKDeKyy8fGc7BNbEWvFK0w@mail.gmail.com>
References: <e3c4dfb0-c6a3-2472-9fa5-81a7c47cf581@gmail.com>
 <CA+RQFfcs+xivYxaDk+ZXLRkmuv=24=BBggYFHiA=vfhhvOOafw@mail.gmail.com>
 <CAKSVWF+wMODs0R5C8+us_byLn1oCho7exMRK15JbSNcmrz8VeQ@mail.gmail.com>
 <8E0E8155-E45B-4954-9A78-89F8A41C6B68@mozilla.com>
 <CAA10jzOHHCRoFdscFV5uQ+=BfFoEcZuDSRqSDMEaZU9fYr01Ag@mail.gmail.com>
 <CAO-2QM6dZAPRwcAFALJH8o4Si_koUOB_zyRbzCHfHH3Eui0MjA@mail.gmail.com>
 <CAG5Cgtq+NFScQGV-kUQYh2EtyS-xggrTHB3GYpi6gavDmiqFzg@mail.gmail.com>
 <CAK7X-XCQxyPXgkLhv2QY7zDmSOiXaKDeKyy8fGc7BNbEWvFK0w@mail.gmail.com>
Message-ID: <CAJGDcJD3k-ea+8BxSU+QN4G6LjsS1_9LKEbBv_Fk82qE8Uk=-Q@mail.gmail.com>

It is exciting the package arrived in Shanghai, Thanks a lot!


Best Regard
Ted

On Fri, Oct 28, 2016 at 8:54 PM, Vasily Kuznetsov <kvas.it at gmail.com> wrote:

> I got mine too and it's awesome! Thanks Florian for doing all the grunt
> work of getting this printed.
>
> On Thu, Oct 27, 2016 at 9:28 PM Oliver Bestwalter <oliver at bestwalter.de>
> wrote:
>
>> Hi all,
>>
>> mine arrived today. Thanks a lot!
>>
>> Cheers
>> Oliver
>>
>> On Thu, 27 Oct 2016 at 14:22 Ana Ribeiro <aninhacostaribeiro at gmail.com>
>> wrote:
>>
>> Seems it gets longer to get in Brazil :'( Still waiting for mine too.
>>
>> 2016-10-27 7:09 GMT-03:00 Ronny Pfannschmidt <rpfannsc at redhat.com>:
>>
>> mine arrived as well :)
>>
>> 2016-10-26 21:45 GMT+02:00 Dave Hunt <dhunt at mozilla.com>:
>>
>> Awesome shirt, thanks everyone!
>>
>> [image: image1.JPG]
>>
>> Dave Hunt
>>
>> On 24 Oct 2016, at 19:29, Stefan Farmbauer <farmi at web.de> wrote:
>>
>> Mine arrived too. Thanks a lot. It's really cool
>>
>> Bruno Oliveira <nicoddemus at gmail.com> schrieb am Mo., 24. Okt. 2016
>> 19:18:
>>
>> Pics or didn't happen! :)
>>
>> Still waiting for mine. ^^
>>
>> On Mon, Oct 24, 2016 at 3:04 PM Omar Kohl <omarkohl at gmail.com> wrote:
>>
>> Hey,
>>
>> the 2016 Sprint T-Shirt arrived today! Thanks a lot, very cool :-)
>>
>> Omar
>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>>
>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>>
>>
>>
>> --
>>
>> 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
>>
>>
>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>>
>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20161104/c7a94f8b/attachment.html>

From me at the-compiler.org  Fri Nov  4 01:19:14 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Fri, 4 Nov 2016 06:19:14 +0100
Subject: [pytest-dev] T-Shirt has arrived!
In-Reply-To: <CAJGDcJD3k-ea+8BxSU+QN4G6LjsS1_9LKEbBv_Fk82qE8Uk=-Q@mail.gmail.com>
References: <e3c4dfb0-c6a3-2472-9fa5-81a7c47cf581@gmail.com>
 <CA+RQFfcs+xivYxaDk+ZXLRkmuv=24=BBggYFHiA=vfhhvOOafw@mail.gmail.com>
 <CAKSVWF+wMODs0R5C8+us_byLn1oCho7exMRK15JbSNcmrz8VeQ@mail.gmail.com>
 <8E0E8155-E45B-4954-9A78-89F8A41C6B68@mozilla.com>
 <CAA10jzOHHCRoFdscFV5uQ+=BfFoEcZuDSRqSDMEaZU9fYr01Ag@mail.gmail.com>
 <CAO-2QM6dZAPRwcAFALJH8o4Si_koUOB_zyRbzCHfHH3Eui0MjA@mail.gmail.com>
 <CAG5Cgtq+NFScQGV-kUQYh2EtyS-xggrTHB3GYpi6gavDmiqFzg@mail.gmail.com>
 <CAK7X-XCQxyPXgkLhv2QY7zDmSOiXaKDeKyy8fGc7BNbEWvFK0w@mail.gmail.com>
 <CAJGDcJD3k-ea+8BxSU+QN4G6LjsS1_9LKEbBv_Fk82qE8Uk=-Q@mail.gmail.com>
Message-ID: <20161104051914.cufrizs6fpvlbtfo@tonks>

Hey Ted,

* Ted <xiao.xj at gmail.com> [2016-11-04 10:33:38 +0800]:
> It is exciting the package arrived in Shanghai, Thanks a lot!

Glad to hear that! And it didn't even take the 1-6 months which
packages in the opposite direction usually take for me ;)

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: 801 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20161104/2c36d28e/attachment-0001.sig>

From holger at merlinux.eu  Fri Nov  4 05:53:16 2016
From: holger at merlinux.eu (holger krekel)
Date: Fri, 4 Nov 2016 10:53:16 +0100
Subject: [pytest-dev] new tox-dev mailing list on python
Message-ID: <20161104095316.GY21830@merlinux.eu>

Hey all,

thanks to Mark Sapiro we now have a dedicated mailing list (tox-dev at python.org) and it's even using Mailman3 :) Please subscribe here:

    https://mail.python.org/mm3/mailman3/lists/tox-dev.python.org

We also recently moved tox development to github:

    https://github.com/tox-dev/tox

I am more than happy to give people commit/push/merge rights, especially those who contributed already.

I take the opportunity to thank Oliver Bestwalter for stepping up to sort through issueslately.  Some of the activity around tox also was possible thanks to the 2016 python testing sprint which was crowdfunded.  So thanks to those who contributed at the sprint and for the sprint.  Next up is getting a nice logo for tox[1].  So don't hesitate to join tox-dev ML to influence what logo tox is going to have :)

best,
holger

[1] I suggest we use a bit of the remaining crowd-funds to give some money to whoever comes up with a nice logo design.

From tom at viner.tv  Fri Nov  4 06:21:08 2016
From: tom at viner.tv (Tom Viner)
Date: Fri, 4 Nov 2016 10:21:08 +0000
Subject: [pytest-dev] T-Shirt has arrived!
Message-ID: <CANBSuyEEWgUwzED5B9a0b+mXdzpSdtb8eT0fbO00PwjeOYOX5g@mail.gmail.com>

Yes mine arrived too. Thanks Florian!

Am I wearing it right btw? I tried the other way first, but the ticket
label thing was at the front.

[image: Inline images 1]
https://imgur.com/a/i3ud6
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20161104/ee508bba/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 702069 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20161104/ee508bba/attachment-0001.png>

From me at the-compiler.org  Fri Nov  4 06:31:25 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Fri, 4 Nov 2016 11:31:25 +0100
Subject: [pytest-dev] T-Shirt has arrived!
In-Reply-To: <CANBSuyEEWgUwzED5B9a0b+mXdzpSdtb8eT0fbO00PwjeOYOX5g@mail.gmail.com>
References: <CANBSuyEEWgUwzED5B9a0b+mXdzpSdtb8eT0fbO00PwjeOYOX5g@mail.gmail.com>
Message-ID: <20161104103125.emmwbmupbwaleye3@tonks>

Hey Tom,

* Tom Viner <tom at viner.tv> [2016-11-04 10:21:08 +0000]:
> Am I wearing it right btw? I tried the other way first, but the ticket
> label thing was at the front.

Yep, the print is supposed to be on the back :)

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: 801 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20161104/a4843023/attachment.sig>

From kvas.it at gmail.com  Fri Nov  4 07:20:06 2016
From: kvas.it at gmail.com (Vasily Kuznetsov)
Date: Fri, 04 Nov 2016 11:20:06 +0000
Subject: [pytest-dev] T-Shirt has arrived!
In-Reply-To: <20161104103125.emmwbmupbwaleye3@tonks>
References: <CANBSuyEEWgUwzED5B9a0b+mXdzpSdtb8eT0fbO00PwjeOYOX5g@mail.gmail.com>
 <20161104103125.emmwbmupbwaleye3@tonks>
Message-ID: <CAK7X-XCt1dU2arvybxqm3eXHyhvWwZ3vH6C+TV-Q5ODNOTvpxA@mail.gmail.com>

Yes, indeed the print is supposed to be on the back. It was Brianna's
suggestion to make it so. The thing is, when a girl is wearing a t-shirt
with some elaborate writing on the front, it gets awkward when people try
to read it. I totally sympathise with that. Printing the test results on
the back, on the other hand, allows anyone to discreetly assure themselves
that your garment is working correctly ;)

Cheers,
Vasily

P.S. The disadvantage of the print on the back, though, is that I can't see
your faces in the pictures... perhaps we should have another sprint to take
care of this.

On Fri, Nov 4, 2016 at 11:31 AM Florian Bruhin <me at the-compiler.org> wrote:

> Hey Tom,
>
> * Tom Viner <tom at viner.tv> [2016-11-04 10:21:08 +0000]:
> > Am I wearing it right btw? I tried the other way first, but the ticket
> > label thing was at the front.
>
> Yep, the print is supposed to be on the back :)
>
> 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/20161104/ff8c9740/attachment.html>

From bjlockie at lockie.ca  Fri Nov  4 09:02:30 2016
From: bjlockie at lockie.ca (James)
Date: Fri, 4 Nov 2016 09:02:30 -0400
Subject: [pytest-dev] showing reason for skipped and verbose
Message-ID: <02fe80f3-52e6-6f95-a059-ad2079f23595@lockie.ca>

$ py.test -v testscript.py
============================= test session starts 
==============================
platform linux2 -- Python 2.7.12, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 
-- /usr/bin/python
cachedir: .cache
rootdir: /home/rjl/pytest, inifile:
collected 8 items

testscript.py::TestAclass::test_1 PASSED
testscript.py::TestAclass::test_2 PASSED
testscript.py::TestAclass::test_3 PASSED
testscript.py::TestAclass::test_4 PASSED
testscript.py::TestBclass::test_21 SKIPPED
testscript.py::TestBclass::test_22 SKIPPED
testscript.py::TestBclass::test_23 SKIPPED
testscript.py::TestBclass::test_24 SKIPPED

===================== 4 passed, 4 skipped in 0.03 seconds 
======================

$ py.test -rv testscript.py
============================= test session starts 
==============================
platform linux2 -- Python 2.7.12, pytest-2.8.7, py-1.4.31, pluggy-0.3.1
rootdir: /home/rjl/pytest, inifile:
collected 8 items

testscript.py ....ssss

===================== 4 passed, 4 skipped in 0.01 seconds 
======================

$ py.test -rs testscript.py
============================= test session starts 
==============================
platform linux2 -- Python 2.7.12, pytest-2.8.7, py-1.4.31, pluggy-0.3.1
rootdir: /home/rjl/pytest, inifile:
collected 8 items

testscript.py ....ssss
=========================== short test summary info 
============================
SKIP [4] /home/rjl/pytest/conftest.py:8: test needs -A option to run

===================== 4 passed, 4 skipped in 0.01 seconds 
======================


I want the output from the first one showing 'PASSED' or 'SKIPPED' but I 
also want to see the reason a specific test was skipped.
Something like:
testscript.py::TestAclass::test_1 PASSED
testscript.py::TestAclass::test_2 PASSED
testscript.py::TestAclass::test_3 PASSED
testscript.py::TestAclass::test_4 PASSED
testscript.py::TestBclass::test_21 SKIPPED (needs -A option to run)
testscript.py::TestBclass::test_22 SKIPPED (needs -A option to run)
testscript.py::TestBclass::test_23 SKIPPED (needs -A option to run)
testscript.py::TestBclass::test_24 SKIPPED (needs -A option to run)


From nicoddemus at gmail.com  Fri Nov  4 09:10:32 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Fri, 04 Nov 2016 13:10:32 +0000
Subject: [pytest-dev] showing reason for skipped and verbose
In-Reply-To: <02fe80f3-52e6-6f95-a059-ad2079f23595@lockie.ca>
References: <02fe80f3-52e6-6f95-a059-ad2079f23595@lockie.ca>
Message-ID: <CA+RQFffNDZSdNDqkQYS2gYV0at5SzH7xffUU8jK6tmPzD5ZbrA@mail.gmail.com>

Hi James,

I guess this makes sense. Could please report an issue in the bug tracker:
https://github.com/pytest-dev/pytest/issues?

Thanks,
Bruno.

On Fri, Nov 4, 2016 at 11:04 AM James <bjlockie at lockie.ca> wrote:

> $ py.test -v testscript.py
> ============================= test session starts
> ==============================
> platform linux2 -- Python 2.7.12, pytest-2.8.7, py-1.4.31, pluggy-0.3.1
> -- /usr/bin/python
> cachedir: .cache
> rootdir: /home/rjl/pytest, inifile:
> collected 8 items
>
> testscript.py::TestAclass::test_1 PASSED
> testscript.py::TestAclass::test_2 PASSED
> testscript.py::TestAclass::test_3 PASSED
> testscript.py::TestAclass::test_4 PASSED
> testscript.py::TestBclass::test_21 SKIPPED
> testscript.py::TestBclass::test_22 SKIPPED
> testscript.py::TestBclass::test_23 SKIPPED
> testscript.py::TestBclass::test_24 SKIPPED
>
> ===================== 4 passed, 4 skipped in 0.03 seconds
> ======================
>
> $ py.test -rv testscript.py
> ============================= test session starts
> ==============================
> platform linux2 -- Python 2.7.12, pytest-2.8.7, py-1.4.31, pluggy-0.3.1
> rootdir: /home/rjl/pytest, inifile:
> collected 8 items
>
> testscript.py ....ssss
>
> ===================== 4 passed, 4 skipped in 0.01 seconds
> ======================
>
> $ py.test -rs testscript.py
> ============================= test session starts
> ==============================
> platform linux2 -- Python 2.7.12, pytest-2.8.7, py-1.4.31, pluggy-0.3.1
> rootdir: /home/rjl/pytest, inifile:
> collected 8 items
>
> testscript.py ....ssss
> =========================== short test summary info
> ============================
> SKIP [4] /home/rjl/pytest/conftest.py:8: test needs -A option to run
>
> ===================== 4 passed, 4 skipped in 0.01 seconds
> ======================
>
>
> I want the output from the first one showing 'PASSED' or 'SKIPPED' but I
> also want to see the reason a specific test was skipped.
> Something like:
> testscript.py::TestAclass::test_1 PASSED
> testscript.py::TestAclass::test_2 PASSED
> testscript.py::TestAclass::test_3 PASSED
> testscript.py::TestAclass::test_4 PASSED
> testscript.py::TestBclass::test_21 SKIPPED (needs -A option to run)
> testscript.py::TestBclass::test_22 SKIPPED (needs -A option to run)
> testscript.py::TestBclass::test_23 SKIPPED (needs -A option to run)
> testscript.py::TestBclass::test_24 SKIPPED (needs -A option to run)
>
> _______________________________________________
> 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/20161104/28824f56/attachment-0001.html>

From tom at viner.tv  Fri Nov  4 19:40:35 2016
From: tom at viner.tv (Tom Viner)
Date: Fri, 4 Nov 2016 23:40:35 +0000
Subject: [pytest-dev] T-Shirt has arrived!
Message-ID: <CANBSuyFiqOnaDEOu_sNhjnfuG9A0Tx3W6Dxu_YKO_rE2ZDaozQ@mail.gmail.com>

Aha, thanks for explaining!

And what a splendid idea Vasily.

On 4 November 2016 at 13:10, <pytest-dev-request at python.org> wrote:

> Yes, indeed the print is supposed to be on the back. It was Brianna's
> suggestion to make it so. The thing is, when a girl is wearing a t-shirt
> with some elaborate writing on the front, it gets awkward when people try
> to read it. I totally sympathise with that. Printing the test results on
> the back, on the other hand, allows anyone to discreetly assure themselves
> that your garment is working correctly ;)
>
> Cheers,
> Vasily
>
> P.S. The disadvantage of the print on the back, though, is that I can't
> see
> your faces in the pictures... perhaps we should have another sprint to take
> care of this.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20161104/9a3f8e84/attachment.html>

From nicoddemus at gmail.com  Fri Nov 11 15:15:16 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Fri, 11 Nov 2016 20:15:16 +0000
Subject: [pytest-dev] pytest 3.0.4 released
Message-ID: <CA+RQFfej65XjNksGgwvsh7AXdCJkEHyeGN8yoNiijr1mA9CRFA@mail.gmail.com>

Hi all,

pytest 3.0.4 has just been released to PyPI.

This release fixes some regressions and bugs reported in the last version,
being a drop-in replacement. To upgrade::

  pip install --upgrade pytest

The changelog is available at http://doc.pytest.org/en/latest/changelog.html
.

Thanks to all who contributed to this release, among them:

* Bruno Oliveira
* Dan Wandschneider
* Florian Bruhin
* Georgy Dyuldin
* Grigorii Eremeev
* Jason R. Coombs
* Manuel Jacob
* Mathieu Clabaut
* Michael Seifert
* Nikolaus Rath
* Ronny Pfannschmidt
* Tom V

Happy testing,
The pytest Development Team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20161111/ab4edaf3/attachment.html>

From flub at devork.be  Sat Nov 12 15:22:30 2016
From: flub at devork.be (Floris Bruynooghe)
Date: Sat, 12 Nov 2016 12:22:30 -0800
Subject: [pytest-dev] t-shirts and stickers now out, thanks Florian!
In-Reply-To: <e33829f4-3804-981f-b9be-9e43ce538e35@ronnypfannschmidt.de>
References: <20161025110411.GH4522@merlinux.eu>
 <e33829f4-3804-981f-b9be-9e43ce538e35@ronnypfannschmidt.de>
Message-ID: <CAAWk_Dxt+DHgGSq5UbY3Yu2MWwOtkwyK8rwPJAMXKUEx0C6dDQ@mail.gmail.com>

Hi All,

On 25 October 2016 at 06:15, Ronny Pfannschmidt
<opensource at ronnypfannschmidt.de> wrote:
> a) preparing and planning much better connectivity for the next sprint,
>     the venue was fabulous but i think the bad internet connection
>     was a tax on productivity while hacking, ensuring good connectivity
>     independent of the venue would enable us to keep using beautiful low
> cost venues
>     while not making the use of the services we grew accustomed to while
> developing
>     harder than necessary

This seems like a nice idea.  I guess it falls under sprint funds
though, we probably should just not mind spending some money on
connectivity.

> b) sovereign build/ci infrastructure for both pytest* and tox*
>     (*i* feel that travis&co are very limiting and actively
>      prevent doing certain kinds of automation in a simple painless way,)
>     however this is a larger topic i might not be able to address this
> year to begin with

I feel like fully sovereign build/ci infrastructure is more likely to
be limited by the time and effort needed to create and maintain it
then by money.  But if paying travis or someone else would make a
significant difference to our experience with build/ci then I'd be in
favour of that.

Floris

From flub at devork.be  Sun Nov 13 21:52:47 2016
From: flub at devork.be (Floris Bruynooghe)
Date: Sun, 13 Nov 2016 18:52:47 -0800
Subject: [pytest-dev] Commit access to pytest
Message-ID: <CAAWk_Dz1Vs2RtvrOWFGXxzWWnCp45pa2b1j9t771DoaqW1zHMw@mail.gmail.com>

Hi all,

A while ago Ronny proposed to adopt the ZeroMQ C4.1 process.  While
the discussion there never got very far (and I forgot to pick it up at
the sprint) I'd like to propose a rather less radical workflow while
attempting to make it easier for people to get on board.

Basically I'd propose to give commit access to anyone who created a PR
and followed it through to it being successfully merged (with
changelog etc etc all done by the new contributor).

The main reason to propose this is because right now we don't really
have a clear policy on when someone joins the committers.  And it is
much more inclusive to write down clear rules for this.  Gaining
commit access is generally empowering and motivating and a good way to
include new members in the development.

What do other people think?

Floris

From opensource at ronnypfannschmidt.de  Mon Nov 14 02:35:38 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Mon, 14 Nov 2016 08:35:38 +0100
Subject: [pytest-dev] Commit access to pytest
In-Reply-To: <CAAWk_Dz1Vs2RtvrOWFGXxzWWnCp45pa2b1j9t771DoaqW1zHMw@mail.gmail.com>
References: <CAAWk_Dz1Vs2RtvrOWFGXxzWWnCp45pa2b1j9t771DoaqW1zHMw@mail.gmail.com>
Message-ID: <21e78b9f-513b-56f3-c990-b3f5b1c7cb7a@ronnypfannschmidt.de>

Hi All,

i believe that when we do something like this, we should lean in the
direction of C 4.1
and focus on enabling more people to merge good pull requests of others
(we already started to follow a informal process where we no longer
self-merge until approval)

With the review Approval system that came to github i feel that c4.1 it
not up to date for gh
(i.e. self merge after approval looks like a valid move now)

I like the idea of slowly iterating towards  a more open and inclusive
process.
Readily offering commit bits to people that Demonstrate
they can honor the Contribution Process is a beautiful first step.

-- Ronny

Am 14.11.2016 um 03:52 schrieb Floris Bruynooghe:
> Hi all,
>
> A while ago Ronny proposed to adopt the ZeroMQ C4.1 process.  While
> the discussion there never got very far (and I forgot to pick it up at
> the sprint) I'd like to propose a rather less radical workflow while
> attempting to make it easier for people to get on board.
>
> Basically I'd propose to give commit access to anyone who created a PR
> and followed it through to it being successfully merged (with
> changelog etc etc all done by the new contributor).
>
> The main reason to propose this is because right now we don't really
> have a clear policy on when someone joins the committers.  And it is
> much more inclusive to write down clear rules for this.  Gaining
> commit access is generally empowering and motivating and a good way to
> include new members in the development.
>
> What do other people think?
>
> Floris
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev


From slafs.e at gmail.com  Mon Nov 14 04:49:02 2016
From: slafs.e at gmail.com (=?UTF-8?Q?S=C5=82awek_Ehlert?=)
Date: Mon, 14 Nov 2016 09:49:02 +0000
Subject: [pytest-dev] ANN: pytest-bpdb is now part of pytest-dev org on
 GitHub
Message-ID: <CAOTs6ty4fu6o16GwTdvs_GdY8-pANxo5tyObp_X4RKUM1verUw@mail.gmail.com>

Just wanted to say hi and mention that pytest-bpdb plugin is now a part of
pytest-dev organization on GitHub.

https://github.com/pytest-dev/pytest-bpdb

Kind regards

S?awek Ehlert
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20161114/751c11dc/attachment.html>

From nicoddemus at gmail.com  Mon Nov 14 09:59:30 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Mon, 14 Nov 2016 14:59:30 +0000
Subject: [pytest-dev] Commit access to pytest
In-Reply-To: <21e78b9f-513b-56f3-c990-b3f5b1c7cb7a@ronnypfannschmidt.de>
References: <CAAWk_Dz1Vs2RtvrOWFGXxzWWnCp45pa2b1j9t771DoaqW1zHMw@mail.gmail.com>
 <21e78b9f-513b-56f3-c990-b3f5b1c7cb7a@ronnypfannschmidt.de>
Message-ID: <CA+RQFfcbge-jAMqhimqV=3XDQ4kw8Gf7DjwJgxbFGPkN8xCxvA@mail.gmail.com>

Hi everyone,

I like the idea as well. As Floris mentioned, giving people commit access
is certainly a good way of motivating new contributors.

Anyone up for writing up those guidelines so we can review them and decide
if we want to move in that direction or not?

Cheers

On Mon, Nov 14, 2016 at 5:42 AM Ronny Pfannschmidt <
opensource at ronnypfannschmidt.de> wrote:

> Hi All,
>
> i believe that when we do something like this, we should lean in the
> direction of C 4.1
> and focus on enabling more people to merge good pull requests of others
> (we already started to follow a informal process where we no longer
> self-merge until approval)
>
> With the review Approval system that came to github i feel that c4.1 it
> not up to date for gh
> (i.e. self merge after approval looks like a valid move now)
>
> I like the idea of slowly iterating towards  a more open and inclusive
> process.
> Readily offering commit bits to people that Demonstrate
> they can honor the Contribution Process is a beautiful first step.
>
> -- Ronny
>
> Am 14.11.2016 um 03:52 schrieb Floris Bruynooghe:
> > Hi all,
> >
> > A while ago Ronny proposed to adopt the ZeroMQ C4.1 process.  While
> > the discussion there never got very far (and I forgot to pick it up at
> > the sprint) I'd like to propose a rather less radical workflow while
> > attempting to make it easier for people to get on board.
> >
> > Basically I'd propose to give commit access to anyone who created a PR
> > and followed it through to it being successfully merged (with
> > changelog etc etc all done by the new contributor).
> >
> > The main reason to propose this is because right now we don't really
> > have a clear policy on when someone joins the committers.  And it is
> > much more inclusive to write down clear rules for this.  Gaining
> > commit access is generally empowering and motivating and a good way to
> > include new members in the development.
> >
> > What do other people think?
> >
> > Floris
> > _______________________________________________
> > 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/20161114/293dfcdb/attachment.html>

From alexander.belopolsky at gmail.com  Mon Nov 14 18:34:15 2016
From: alexander.belopolsky at gmail.com (Alexander Belopolsky)
Date: Mon, 14 Nov 2016 18:34:15 -0500
Subject: [pytest-dev] Session state
Message-ID: <CAP7h-xYvDQCDZxci718nnd_QAyca_W53ZpCnS0bSG11gLYm+uQ@mail.gmail.com>

Dear Pytest-Dev,

I am trying to implement a pytest plugin to check for reference leaks
similarly to how it is done in CPython with python -mtest -R : command.

The problem is that pytest_runtest_protocol seems to update some internal
state and calling it even on an empty test function increases the total
reference count.  Clearly, I need to clean up the internal state in my
plugin, but I cannot figure out where this state is kept.

Looking at the  pytest_runtest_protocol implementation in runner.py, I see
the following code:

def pytest_runtest_protocol(item, nextitem):
    ...
    runtestprotocol(item, nextitem=nextitem)
    return True

where runtestprotocol() is a function returning a list to reports, but this
list is apparently discarded by the runner.  Can someone explain how
reports are passed from the runner hooks to the terminal hooks?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20161114/1924a2dd/attachment.html>

From flub at devork.be  Tue Nov 15 15:18:27 2016
From: flub at devork.be (Floris Bruynooghe)
Date: Tue, 15 Nov 2016 20:18:27 +0000
Subject: [pytest-dev] Commit access to pytest
In-Reply-To: <CA+RQFfcbge-jAMqhimqV=3XDQ4kw8Gf7DjwJgxbFGPkN8xCxvA@mail.gmail.com>
References: <CAAWk_Dz1Vs2RtvrOWFGXxzWWnCp45pa2b1j9t771DoaqW1zHMw@mail.gmail.com>
 <21e78b9f-513b-56f3-c990-b3f5b1c7cb7a@ronnypfannschmidt.de>
 <CA+RQFfcbge-jAMqhimqV=3XDQ4kw8Gf7DjwJgxbFGPkN8xCxvA@mail.gmail.com>
Message-ID: <CAAWk_Dxaa0A+1abmKVqYQSGBz2AQ_jdy1wT6zt4DOH3E1SfR2A@mail.gmail.com>

Cool, I'll create a PR against CONTRIBUTING.txt, but I'll re-read C4.1
again first to incorporate Ronny's comments better.

Floris

On 14 November 2016 at 14:59, Bruno Oliveira <nicoddemus at gmail.com> wrote:
> Hi everyone,
>
> I like the idea as well. As Floris mentioned, giving people commit access is
> certainly a good way of motivating new contributors.
>
> Anyone up for writing up those guidelines so we can review them and decide
> if we want to move in that direction or not?
>
> Cheers
>
> On Mon, Nov 14, 2016 at 5:42 AM Ronny Pfannschmidt
> <opensource at ronnypfannschmidt.de> wrote:
>>
>> Hi All,
>>
>> i believe that when we do something like this, we should lean in the
>> direction of C 4.1
>> and focus on enabling more people to merge good pull requests of others
>> (we already started to follow a informal process where we no longer
>> self-merge until approval)
>>
>> With the review Approval system that came to github i feel that c4.1 it
>> not up to date for gh
>> (i.e. self merge after approval looks like a valid move now)
>>
>> I like the idea of slowly iterating towards  a more open and inclusive
>> process.
>> Readily offering commit bits to people that Demonstrate
>> they can honor the Contribution Process is a beautiful first step.
>>
>> -- Ronny
>>
>> Am 14.11.2016 um 03:52 schrieb Floris Bruynooghe:
>> > Hi all,
>> >
>> > A while ago Ronny proposed to adopt the ZeroMQ C4.1 process.  While
>> > the discussion there never got very far (and I forgot to pick it up at
>> > the sprint) I'd like to propose a rather less radical workflow while
>> > attempting to make it easier for people to get on board.
>> >
>> > Basically I'd propose to give commit access to anyone who created a PR
>> > and followed it through to it being successfully merged (with
>> > changelog etc etc all done by the new contributor).
>> >
>> > The main reason to propose this is because right now we don't really
>> > have a clear policy on when someone joins the committers.  And it is
>> > much more inclusive to write down clear rules for this.  Gaining
>> > commit access is generally empowering and motivating and a good way to
>> > include new members in the development.
>> >
>> > What do other people think?
>> >
>> > Floris
>> > _______________________________________________
>> > 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 oliver at bestwalter.de  Tue Nov 15 18:19:33 2016
From: oliver at bestwalter.de (Oliver Bestwalter)
Date: Tue, 15 Nov 2016 23:19:33 +0000
Subject: [pytest-dev] Commit access to pytest
In-Reply-To: <CAAWk_Dxaa0A+1abmKVqYQSGBz2AQ_jdy1wT6zt4DOH3E1SfR2A@mail.gmail.com>
References: <CAAWk_Dz1Vs2RtvrOWFGXxzWWnCp45pa2b1j9t771DoaqW1zHMw@mail.gmail.com>
 <21e78b9f-513b-56f3-c990-b3f5b1c7cb7a@ronnypfannschmidt.de>
 <CA+RQFfcbge-jAMqhimqV=3XDQ4kw8Gf7DjwJgxbFGPkN8xCxvA@mail.gmail.com>
 <CAAWk_Dxaa0A+1abmKVqYQSGBz2AQ_jdy1wT6zt4DOH3E1SfR2A@mail.gmail.com>
Message-ID: <CAG5CgtqUATS8t7Rv7gh+LBnfccTPJsNAmbvSftvKmX5h-5qqUw@mail.gmail.com>

Hi,

will this be a "sorta kinda C4" then or do we want to implement the whole
thing as described in https://rfc.zeromq.org/spec:42/C4/ ?

I ask because what you describe Floris is an interesting idea but I do not
see the parallel to C4 as that process clearly has maintainers who merge
PRs of others, which I think of as a Good Thing. I mean this part of the
protocol:

- A "Contributor" is a person who wishes to provide a patch, being a set of
commits that solve some clearly identified problem.
- A "Maintainer" is a person who merges patches to the project. Maintainers
are not developers; their job is to enforce process.
- Contributors SHALL NOT have commit access to the repository unless they
are also Maintainers.
- Maintainers SHALL have commit access to the repository.
I also like the whole Problem -> Solution idea as basis for  development of
the project (section 2.3).

Giving everybody commit rights who successfully merged a PR is a different
idea that could be experimented with, but I would not call it C4.

Cheers
Oliver

On Tue, 15 Nov 2016 at 21:18 Floris Bruynooghe <flub at devork.be> wrote:

> Cool, I'll create a PR against CONTRIBUTING.txt, but I'll re-read C4.1
> again first to incorporate Ronny's comments better.
>
> Floris
>
> On 14 November 2016 at 14:59, Bruno Oliveira <nicoddemus at gmail.com> wrote:
> > Hi everyone,
> >
> > I like the idea as well. As Floris mentioned, giving people commit
> access is
> > certainly a good way of motivating new contributors.
> >
> > Anyone up for writing up those guidelines so we can review them and
> decide
> > if we want to move in that direction or not?
> >
> > Cheers
> >
> > On Mon, Nov 14, 2016 at 5:42 AM Ronny Pfannschmidt
> > <opensource at ronnypfannschmidt.de> wrote:
> >>
> >> Hi All,
> >>
> >> i believe that when we do something like this, we should lean in the
> >> direction of C 4.1
> >> and focus on enabling more people to merge good pull requests of others
> >> (we already started to follow a informal process where we no longer
> >> self-merge until approval)
> >>
> >> With the review Approval system that came to github i feel that c4.1 it
> >> not up to date for gh
> >> (i.e. self merge after approval looks like a valid move now)
> >>
> >> I like the idea of slowly iterating towards  a more open and inclusive
> >> process.
> >> Readily offering commit bits to people that Demonstrate
> >> they can honor the Contribution Process is a beautiful first step.
> >>
> >> -- Ronny
> >>
> >> Am 14.11.2016 um 03:52 schrieb Floris Bruynooghe:
> >> > Hi all,
> >> >
> >> > A while ago Ronny proposed to adopt the ZeroMQ C4.1 process.  While
> >> > the discussion there never got very far (and I forgot to pick it up at
> >> > the sprint) I'd like to propose a rather less radical workflow while
> >> > attempting to make it easier for people to get on board.
> >> >
> >> > Basically I'd propose to give commit access to anyone who created a PR
> >> > and followed it through to it being successfully merged (with
> >> > changelog etc etc all done by the new contributor).
> >> >
> >> > The main reason to propose this is because right now we don't really
> >> > have a clear policy on when someone joins the committers.  And it is
> >> > much more inclusive to write down clear rules for this.  Gaining
> >> > commit access is generally empowering and motivating and a good way to
> >> > include new members in the development.
> >> >
> >> > What do other people think?
> >> >
> >> > Floris
> >> > _______________________________________________
> >> > 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/20161115/28376586/attachment.html>

From flub at devork.be  Wed Nov 16 14:42:13 2016
From: flub at devork.be (Floris Bruynooghe)
Date: Wed, 16 Nov 2016 19:42:13 +0000
Subject: [pytest-dev] Commit access to pytest
In-Reply-To: <CAG5CgtqUATS8t7Rv7gh+LBnfccTPJsNAmbvSftvKmX5h-5qqUw@mail.gmail.com>
References: <CAAWk_Dz1Vs2RtvrOWFGXxzWWnCp45pa2b1j9t771DoaqW1zHMw@mail.gmail.com>
 <21e78b9f-513b-56f3-c990-b3f5b1c7cb7a@ronnypfannschmidt.de>
 <CA+RQFfcbge-jAMqhimqV=3XDQ4kw8Gf7DjwJgxbFGPkN8xCxvA@mail.gmail.com>
 <CAAWk_Dxaa0A+1abmKVqYQSGBz2AQ_jdy1wT6zt4DOH3E1SfR2A@mail.gmail.com>
 <CAG5CgtqUATS8t7Rv7gh+LBnfccTPJsNAmbvSftvKmX5h-5qqUw@mail.gmail.com>
Message-ID: <CAAWk_DwOtMNq+jcRZX8JMHSHBCz8xiMB7zjhJZEeZT-QCYwLmg@mail.gmail.com>

On 15 November 2016 at 23:19, Oliver Bestwalter <oliver at bestwalter.de> wrote:
> Hi,
>
> will this be a "sorta kinda C4" then or do we want to implement the whole
> thing as described in https://rfc.zeromq.org/spec:42/C4/ ?

Probably not, upon re-reading this I'm not actually a massive fan of
the document in it's entirety despite it having many good intentions,
e.g. 2.3.1 (must use real names) ranks pretty high on my scale for a
bad idea.  But I'm not going to dissect the whole thing here.

> I ask because what you describe Floris is an interesting idea but I do not
> see the parallel to C4 as that process clearly has maintainers who merge PRs
> of others, which I think of as a Good Thing. I mean this part of the
> protocol:
>
> A "Contributor" is a person who wishes to provide a patch, being a set of
> commits that solve some clearly identified problem.
> A "Maintainer" is a person who merges patches to the project. Maintainers
> are not developers; their job is to enforce process.
> Contributors SHALL NOT have commit access to the repository unless they are
> also Maintainers.
> Maintainers SHALL have commit access to the repository.

So upon re-reading of C4.1 I'm just interested in formalising how one
gets to be a Maintainer.  C4.1 itself leaves this pretty vague while
I'd like to give Contributors a clear expectation.

> I also like the whole Problem -> Solution idea as basis for  development of
> the project (section 2.3).

Sure, C4.1 has many good ideas quite a few which we already follow more or less.

> Giving everybody commit rights who successfully merged a PR is a different
> idea that could be experimented with, but I would not call it C4.

You're right, there is virtually no overlap between my proposal and
C4.1.  It had been a very long time since I read C4.1 so honestly I
didn't really remember what exactly it contained.


Floris

From oliver at bestwalter.de  Wed Nov 16 17:06:34 2016
From: oliver at bestwalter.de (Oliver Bestwalter)
Date: Wed, 16 Nov 2016 22:06:34 +0000
Subject: [pytest-dev] Commit access to pytest
In-Reply-To: <CAAWk_DwOtMNq+jcRZX8JMHSHBCz8xiMB7zjhJZEeZT-QCYwLmg@mail.gmail.com>
References: <CAAWk_Dz1Vs2RtvrOWFGXxzWWnCp45pa2b1j9t771DoaqW1zHMw@mail.gmail.com>
 <21e78b9f-513b-56f3-c990-b3f5b1c7cb7a@ronnypfannschmidt.de>
 <CA+RQFfcbge-jAMqhimqV=3XDQ4kw8Gf7DjwJgxbFGPkN8xCxvA@mail.gmail.com>
 <CAAWk_Dxaa0A+1abmKVqYQSGBz2AQ_jdy1wT6zt4DOH3E1SfR2A@mail.gmail.com>
 <CAG5CgtqUATS8t7Rv7gh+LBnfccTPJsNAmbvSftvKmX5h-5qqUw@mail.gmail.com>
 <CAAWk_DwOtMNq+jcRZX8JMHSHBCz8xiMB7zjhJZEeZT-QCYwLmg@mail.gmail.com>
Message-ID: <CAG5CgtptGLhz6aDsG+hZMUy27QrmhFffQ6rCOVSq4D9SPxLAJQ@mail.gmail.com>

Hi Floris,

thanks for the clarification.

Cheers
Oliver

On Wed, 16 Nov 2016 at 20:42 Floris Bruynooghe <flub at devork.be> wrote:

> On 15 November 2016 at 23:19, Oliver Bestwalter <oliver at bestwalter.de>
> wrote:
> > Hi,
> >
> > will this be a "sorta kinda C4" then or do we want to implement the whole
> > thing as described in https://rfc.zeromq.org/spec:42/C4/ ?
>
> Probably not, upon re-reading this I'm not actually a massive fan of
> the document in it's entirety despite it having many good intentions,
> e.g. 2.3.1 (must use real names) ranks pretty high on my scale for a
> bad idea.  But I'm not going to dissect the whole thing here.
>
> > I ask because what you describe Floris is an interesting idea but I do
> not
> > see the parallel to C4 as that process clearly has maintainers who merge
> PRs
> > of others, which I think of as a Good Thing. I mean this part of the
> > protocol:
> >
> > A "Contributor" is a person who wishes to provide a patch, being a set of
> > commits that solve some clearly identified problem.
> > A "Maintainer" is a person who merges patches to the project. Maintainers
> > are not developers; their job is to enforce process.
> > Contributors SHALL NOT have commit access to the repository unless they
> are
> > also Maintainers.
> > Maintainers SHALL have commit access to the repository.
>
> So upon re-reading of C4.1 I'm just interested in formalising how one
> gets to be a Maintainer.  C4.1 itself leaves this pretty vague while
> I'd like to give Contributors a clear expectation.
>
> > I also like the whole Problem -> Solution idea as basis for  development
> of
> > the project (section 2.3).
>
> Sure, C4.1 has many good ideas quite a few which we already follow more or
> less.
>
> > Giving everybody commit rights who successfully merged a PR is a
> different
> > idea that could be experimented with, but I would not call it C4.
>
> You're right, there is virtually no overlap between my proposal and
> C4.1.  It had been a very long time since I read C4.1 so honestly I
> didn't really remember what exactly it contained.
>
>
> Floris
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20161116/4f6462a0/attachment.html>

From dan.nealschneider at gmail.com  Wed Nov 16 18:28:14 2016
From: dan.nealschneider at gmail.com (Dan Nealschneider)
Date: Wed, 16 Nov 2016 15:28:14 -0800
Subject: [pytest-dev] Fwd: Error in conftest cache
In-Reply-To: <CAA9fXhxWKT-MiAgtk8+LOyj567fwqybT4E_0-wp-MQjJbgMMYw@mail.gmail.com>
References: <CAA9fXhxWKT-MiAgtk8+LOyj567fwqybT4E_0-wp-MQjJbgMMYw@mail.gmail.com>
Message-ID: <CAA9fXhx7tt_Fo_gUGXZh2VB-_2===EHDAOx7H-JgT5qMKcgPnQ@mail.gmail.com>

I believe that there is a bug in the conftest cache in the Session object.
In some situations, conftests are applied based on the last one imported,
rather than directory hierarchy. The pytest hook docs say "Session and test
running activities will invoke all hooks defined in conftest.py files
closer to the root of the filesystem." (pytest docs
<http://pytest.org/2.2.4/plugins.html#conftest-py-local-per-directory-plugins>
).

I've specifically had problems with creating a new hook, and with the
pytest_ignore_collect
hook, as I reported here: https://github.com/pytest-dev/pytest/issues/2016.

I notice that if I disable the cache (https://github.com/pytest-dev
/pytest/blob/master/_pytest/main.py#L568), both of these hooks will operate
only on subdirectories, as I would have expected. Another option would be
to clear the session's cache each time a new conftest is added (here:
https://github.com/pytest-dev/pytest/blob/master/_pytest/config.py#L342),
but I am worried about that approach because I know that pytest-xdist has
its own session object.

Is this the intended behavior? Or does this sound like a real bug?

Thanks-
Dan W.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20161116/edea8dd4/attachment.html>

From flub at devork.be  Thu Nov 17 16:28:35 2016
From: flub at devork.be (Floris Bruynooghe)
Date: Thu, 17 Nov 2016 21:28:35 +0000
Subject: [pytest-dev] Commit access to pytest
In-Reply-To: <CAAWk_DwOtMNq+jcRZX8JMHSHBCz8xiMB7zjhJZEeZT-QCYwLmg@mail.gmail.com>
References: <CAAWk_Dz1Vs2RtvrOWFGXxzWWnCp45pa2b1j9t771DoaqW1zHMw@mail.gmail.com>
 <21e78b9f-513b-56f3-c990-b3f5b1c7cb7a@ronnypfannschmidt.de>
 <CA+RQFfcbge-jAMqhimqV=3XDQ4kw8Gf7DjwJgxbFGPkN8xCxvA@mail.gmail.com>
 <CAAWk_Dxaa0A+1abmKVqYQSGBz2AQ_jdy1wT6zt4DOH3E1SfR2A@mail.gmail.com>
 <CAG5CgtqUATS8t7Rv7gh+LBnfccTPJsNAmbvSftvKmX5h-5qqUw@mail.gmail.com>
 <CAAWk_DwOtMNq+jcRZX8JMHSHBCz8xiMB7zjhJZEeZT-QCYwLmg@mail.gmail.com>
Message-ID: <CAAWk_Dz+GL-KthY9FrRHkSmqmeEf+2N0WahE63GY6+BL586crg@mail.gmail.com>

Hi all,

I've opened https://github.com/pytest-dev/pytest/pull/2068 if you're
interested in seeing this move forward.  Or if you feel strongly
against this of course.

Thanks,
Floris

On 16 November 2016 at 19:42, Floris Bruynooghe <flub at devork.be> wrote:
> On 15 November 2016 at 23:19, Oliver Bestwalter <oliver at bestwalter.de> wrote:
>> Hi,
>>
>> will this be a "sorta kinda C4" then or do we want to implement the whole
>> thing as described in https://rfc.zeromq.org/spec:42/C4/ ?
>
> Probably not, upon re-reading this I'm not actually a massive fan of
> the document in it's entirety despite it having many good intentions,
> e.g. 2.3.1 (must use real names) ranks pretty high on my scale for a
> bad idea.  But I'm not going to dissect the whole thing here.
>
>> I ask because what you describe Floris is an interesting idea but I do not
>> see the parallel to C4 as that process clearly has maintainers who merge PRs
>> of others, which I think of as a Good Thing. I mean this part of the
>> protocol:
>>
>> A "Contributor" is a person who wishes to provide a patch, being a set of
>> commits that solve some clearly identified problem.
>> A "Maintainer" is a person who merges patches to the project. Maintainers
>> are not developers; their job is to enforce process.
>> Contributors SHALL NOT have commit access to the repository unless they are
>> also Maintainers.
>> Maintainers SHALL have commit access to the repository.
>
> So upon re-reading of C4.1 I'm just interested in formalising how one
> gets to be a Maintainer.  C4.1 itself leaves this pretty vague while
> I'd like to give Contributors a clear expectation.
>
>> I also like the whole Problem -> Solution idea as basis for  development of
>> the project (section 2.3).
>
> Sure, C4.1 has many good ideas quite a few which we already follow more or less.
>
>> Giving everybody commit rights who successfully merged a PR is a different
>> idea that could be experimented with, but I would not call it C4.
>
> You're right, there is virtually no overlap between my proposal and
> C4.1.  It had been a very long time since I read C4.1 so honestly I
> didn't really remember what exactly it contained.
>
>
> Floris

From nicoddemus at gmail.com  Thu Nov 17 18:29:42 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 17 Nov 2016 23:29:42 +0000
Subject: [pytest-dev] Commit access to pytest
In-Reply-To: <CAAWk_Dz+GL-KthY9FrRHkSmqmeEf+2N0WahE63GY6+BL586crg@mail.gmail.com>
References: <CAAWk_Dz1Vs2RtvrOWFGXxzWWnCp45pa2b1j9t771DoaqW1zHMw@mail.gmail.com>
 <21e78b9f-513b-56f3-c990-b3f5b1c7cb7a@ronnypfannschmidt.de>
 <CA+RQFfcbge-jAMqhimqV=3XDQ4kw8Gf7DjwJgxbFGPkN8xCxvA@mail.gmail.com>
 <CAAWk_Dxaa0A+1abmKVqYQSGBz2AQ_jdy1wT6zt4DOH3E1SfR2A@mail.gmail.com>
 <CAG5CgtqUATS8t7Rv7gh+LBnfccTPJsNAmbvSftvKmX5h-5qqUw@mail.gmail.com>
 <CAAWk_DwOtMNq+jcRZX8JMHSHBCz8xiMB7zjhJZEeZT-QCYwLmg@mail.gmail.com>
 <CAAWk_Dz+GL-KthY9FrRHkSmqmeEf+2N0WahE63GY6+BL586crg@mail.gmail.com>
Message-ID: <CA+RQFfcnG5B1jo-GOZOQYptOA3Gb1i7+gFUbyeO8emayVsqVbg@mail.gmail.com>

Hi Floris,

The PR LGTM, I'm just wondering who gives people write access after a
successful PR? The last one to merge it?

Cheers,
Bruno

On Thu, Nov 17, 2016 at 8:38 PM Floris Bruynooghe <flub at devork.be> wrote:

> Hi all,
>
> I've opened https://github.com/pytest-dev/pytest/pull/2068 if you're
> interested in seeing this move forward.  Or if you feel strongly
> against this of course.
>
> Thanks,
> Floris
>
> On 16 November 2016 at 19:42, Floris Bruynooghe <flub at devork.be> wrote:
> > On 15 November 2016 at 23:19, Oliver Bestwalter <oliver at bestwalter.de>
> wrote:
> >> Hi,
> >>
> >> will this be a "sorta kinda C4" then or do we want to implement the
> whole
> >> thing as described in https://rfc.zeromq.org/spec:42/C4/ ?
> >
> > Probably not, upon re-reading this I'm not actually a massive fan of
> > the document in it's entirety despite it having many good intentions,
> > e.g. 2.3.1 (must use real names) ranks pretty high on my scale for a
> > bad idea.  But I'm not going to dissect the whole thing here.
> >
> >> I ask because what you describe Floris is an interesting idea but I do
> not
> >> see the parallel to C4 as that process clearly has maintainers who
> merge PRs
> >> of others, which I think of as a Good Thing. I mean this part of the
> >> protocol:
> >>
> >> A "Contributor" is a person who wishes to provide a patch, being a set
> of
> >> commits that solve some clearly identified problem.
> >> A "Maintainer" is a person who merges patches to the project.
> Maintainers
> >> are not developers; their job is to enforce process.
> >> Contributors SHALL NOT have commit access to the repository unless they
> are
> >> also Maintainers.
> >> Maintainers SHALL have commit access to the repository.
> >
> > So upon re-reading of C4.1 I'm just interested in formalising how one
> > gets to be a Maintainer.  C4.1 itself leaves this pretty vague while
> > I'd like to give Contributors a clear expectation.
> >
> >> I also like the whole Problem -> Solution idea as basis for
> development of
> >> the project (section 2.3).
> >
> > Sure, C4.1 has many good ideas quite a few which we already follow more
> or less.
> >
> >> Giving everybody commit rights who successfully merged a PR is a
> different
> >> idea that could be experimented with, but I would not call it C4.
> >
> > You're right, there is virtually no overlap between my proposal and
> > C4.1.  It had been a very long time since I read C4.1 so honestly I
> > didn't really remember what exactly it contained.
> >
> >
> > Floris
> _______________________________________________
> 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/20161117/f6702871/attachment.html>

From flub at devork.be  Fri Nov 18 03:35:18 2016
From: flub at devork.be (Floris Bruynooghe)
Date: Fri, 18 Nov 2016 08:35:18 +0000
Subject: [pytest-dev] Commit access to pytest
In-Reply-To: <CA+RQFfcnG5B1jo-GOZOQYptOA3Gb1i7+gFUbyeO8emayVsqVbg@mail.gmail.com>
References: <CAAWk_Dz1Vs2RtvrOWFGXxzWWnCp45pa2b1j9t771DoaqW1zHMw@mail.gmail.com>
 <21e78b9f-513b-56f3-c990-b3f5b1c7cb7a@ronnypfannschmidt.de>
 <CA+RQFfcbge-jAMqhimqV=3XDQ4kw8Gf7DjwJgxbFGPkN8xCxvA@mail.gmail.com>
 <CAAWk_Dxaa0A+1abmKVqYQSGBz2AQ_jdy1wT6zt4DOH3E1SfR2A@mail.gmail.com>
 <CAG5CgtqUATS8t7Rv7gh+LBnfccTPJsNAmbvSftvKmX5h-5qqUw@mail.gmail.com>
 <CAAWk_DwOtMNq+jcRZX8JMHSHBCz8xiMB7zjhJZEeZT-QCYwLmg@mail.gmail.com>
 <CAAWk_Dz+GL-KthY9FrRHkSmqmeEf+2N0WahE63GY6+BL586crg@mail.gmail.com>
 <CA+RQFfcnG5B1jo-GOZOQYptOA3Gb1i7+gFUbyeO8emayVsqVbg@mail.gmail.com>
Message-ID: <CAAWk_DymfgLmVHYPQWRWx6EzKZ8pnCWa3w7rJ9_-t5Umq4d=Vg@mail.gmail.com>

On 17 November 2016 at 23:29, Bruno Oliveira <nicoddemus at gmail.com> wrote:
> The PR LGTM, I'm just wondering who gives people write access after a
> successful PR? The last one to merge it?

That's a very good question.  I think you need to be a project admin
rather then committer to be able to add other people as committers?
This means it's a more limited group of people who can do this (and so
far I've avoided talking about how you join that group).  So maybe if
the person doing the merge can't do this directly they should open an
issue for it and we should adopt a label signifying it needs admin
attention?

Floris

From nicoddemus at gmail.com  Tue Nov 22 08:10:22 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Tue, 22 Nov 2016 13:10:22 +0000
Subject: [pytest-dev] Session state
In-Reply-To: <CAP7h-xYvDQCDZxci718nnd_QAyca_W53ZpCnS0bSG11gLYm+uQ@mail.gmail.com>
References: <CAP7h-xYvDQCDZxci718nnd_QAyca_W53ZpCnS0bSG11gLYm+uQ@mail.gmail.com>
Message-ID: <CA+RQFffGx1wPHV2NGGwOoOxvE=+7=jcXFVbUJs=L_0us6mZHFA@mail.gmail.com>

Hi Alexander,

On Mon, Nov 14, 2016 at 9:34 PM Alexander Belopolsky <
alexander.belopolsky at gmail.com> wrote:

> where runtestprotocol() is a function returning a list to reports, but
> this list is apparently discarded by the runner.  Can someone explain how
> reports are passed from the runner hooks to the terminal hooks?
>

The hook implemented by the terminal plugin is pytest_runtest_logreport.
That is called by the runner itself:

def call_and_report(item, when, log=True, **kwds):
    call = call_runtest_hook(item, when, **kwds)
    hook = item.ihook
    report = hook.pytest_runtest_makereport(item=item, call=call)
    if log:
        hook.pytest_runtest_logreport(report=report)
    if check_interactive_exception(call, report):
        hook.pytest_exception_interact(node=item, call=call, report=report)
    return report

Which is called by runtestprotocol. Not sure who is keeping extra
references around, can you make a diff of the objects before and after the
call? Also, did you try calling gc.collect()? There might be some circular
reference somewhere.

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

From alexander.belopolsky at gmail.com  Tue Nov 22 13:13:44 2016
From: alexander.belopolsky at gmail.com (Alexander Belopolsky)
Date: Tue, 22 Nov 2016 13:13:44 -0500
Subject: [pytest-dev] Session state
In-Reply-To: <CA+RQFffGx1wPHV2NGGwOoOxvE=+7=jcXFVbUJs=L_0us6mZHFA@mail.gmail.com>
References: <CAP7h-xYvDQCDZxci718nnd_QAyca_W53ZpCnS0bSG11gLYm+uQ@mail.gmail.com>
 <CA+RQFffGx1wPHV2NGGwOoOxvE=+7=jcXFVbUJs=L_0us6mZHFA@mail.gmail.com>
Message-ID: <CAP7h-xZ5FvEPo6G-7u=h1nafeOQe21KnM=K2NXF4YzR2UtzsVA@mail.gmail.com>

On Tue, Nov 22, 2016 at 8:10 AM, Bruno Oliveira <nicoddemus at gmail.com>
wrote:

>
> Not sure who is keeping extra references around, ...

I have figured out this part.  The problem was that I  originally [0] did
reference counting around a call to item.runtest() which may create new
objects by interacting with features and those objects persist until a
teardown call.  Now I do refcount in the pytest_runtest_protocol hook [1],
but this leaves open the issue of passing the reports to the runner's hooks.

>> where runtestprotocol() is a function returning a list to reports, but
this list is apparently discarded by the runner.  Can someone explain how
reports are passed from the runner hooks to the terminal hooks?
>
>
> The hook implemented by the terminal plugin is pytest_runtest_logreport.
>
> That is called by the runner itself:
>
> def call_and_report(item, when, log=True, **kwds):
>     call = call_runtest_hook(item, when, **kwds)
>     hook = item.ihook
>     report = hook.pytest_runtest_makereport(item=item, call=call)
>     if log:
>         hook.pytest_runtest_logreport(report=report)
>     if check_interactive_exception(call, report):
>         hook.pytest_exception_interact(node=item, call=call,
report=report)
>     return report
>

I am not sure how I can use a similar logic in my code.  As a work-around,
I am storing leaks reports in a global nodeid:rep dictionary which I
process in pytest_report_teststatus and pytest_terminal_summary hooks.  Is
there a better way to do this?

Another open issue is what to do with the fixtures having wider than
"function" scope.

Notwithstanding the remaining issues, my plugin works now with Python 3.5
and I have found one reference leak in my own code (together with 2 false
positives one of which was a poorly written test).  I have published [2] my
plugin as pytest-leaks on PyPI and hopefully others will find it useful.
Any comments or suggestions are most welcome.

[0]:
https://github.com/abalkin/pytest-leaks/blob/v0.1.0/pytest_leaks.py#L103
[1]: https://github.com/abalkin/pytest-leaks/blob/v0.2.0/pytest_leaks.py#L71
[2]: https://pypi.python.org/pypi/pytest-leaks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20161122/d78e0429/attachment.html>

From nicoddemus at gmail.com  Tue Nov 22 14:48:01 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Tue, 22 Nov 2016 19:48:01 +0000
Subject: [pytest-dev] Session state
In-Reply-To: <CAP7h-xZ5FvEPo6G-7u=h1nafeOQe21KnM=K2NXF4YzR2UtzsVA@mail.gmail.com>
References: <CAP7h-xYvDQCDZxci718nnd_QAyca_W53ZpCnS0bSG11gLYm+uQ@mail.gmail.com>
 <CA+RQFffGx1wPHV2NGGwOoOxvE=+7=jcXFVbUJs=L_0us6mZHFA@mail.gmail.com>
 <CAP7h-xZ5FvEPo6G-7u=h1nafeOQe21KnM=K2NXF4YzR2UtzsVA@mail.gmail.com>
Message-ID: <CA+RQFfda3nTwjo8r9YLwi0v9sYdhTW1fr5k=B4G9mPC7_ewYxg@mail.gmail.com>

On Tue, Nov 22, 2016 at 4:13 PM Alexander Belopolsky <
alexander.belopolsky at gmail.com> wrote:

> Notwithstanding the remaining issues, my plugin works now with Python 3.5
> and I have found one reference leak in my own code (together with 2 false
> positives one of which was a poorly written test).  I have published [2] my
> plugin as pytest-leaks on PyPI and hopefully others will find it useful.
> Any comments or suggestions are most welcome.
>
> [0]:
> https://github.com/abalkin/pytest-leaks/blob/v0.1.0/pytest_leaks.py#L103
> [1]:
> https://github.com/abalkin/pytest-leaks/blob/v0.2.0/pytest_leaks.py#L71
> [2]: https://pypi.python.org/pypi/pytest-leaks
>

That's very cool, thanks for sharing this! It would be nice to finish the
README with usage instructions though.

Cheers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20161122/0ae951d5/attachment.html>

From alexander.belopolsky at gmail.com  Tue Nov 22 15:45:47 2016
From: alexander.belopolsky at gmail.com (Alexander Belopolsky)
Date: Tue, 22 Nov 2016 15:45:47 -0500
Subject: [pytest-dev] Session state
In-Reply-To: <CA+RQFfda3nTwjo8r9YLwi0v9sYdhTW1fr5k=B4G9mPC7_ewYxg@mail.gmail.com>
References: <CAP7h-xYvDQCDZxci718nnd_QAyca_W53ZpCnS0bSG11gLYm+uQ@mail.gmail.com>
 <CA+RQFffGx1wPHV2NGGwOoOxvE=+7=jcXFVbUJs=L_0us6mZHFA@mail.gmail.com>
 <CAP7h-xZ5FvEPo6G-7u=h1nafeOQe21KnM=K2NXF4YzR2UtzsVA@mail.gmail.com>
 <CA+RQFfda3nTwjo8r9YLwi0v9sYdhTW1fr5k=B4G9mPC7_ewYxg@mail.gmail.com>
Message-ID: <CAP7h-xZpUpxnbB6oCiNaKLFm-_EW0x4cNM86tJq7FBMgd4JUKA@mail.gmail.com>

On Tue, Nov 22, 2016 at 2:48 PM, Bruno Oliveira <nicoddemus at gmail.com>
wrote:

> It would be nice to finish the README with usage instructions


Done. [1]  Doe anyone know why PyPI did not render README.rst as reST? [2]
 It worked as expected with the previous upload. [3]

[1]:
https://github.com/abalkin/pytest-leaks#pytest-leaks---a-pytest-plugin-to-trace-resource-leaks
[2]: https://pypi.python.org/pypi/pytest-leaks/0.2.1
[3]: https://pypi.python.org/pypi/pytest-leaks/0.2.0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20161122/6dc9c932/attachment.html>

From alexander.belopolsky at gmail.com  Tue Nov 22 16:59:32 2016
From: alexander.belopolsky at gmail.com (Alexander Belopolsky)
Date: Tue, 22 Nov 2016 16:59:32 -0500
Subject: [pytest-dev] Session state
In-Reply-To: <CAP7h-xZpUpxnbB6oCiNaKLFm-_EW0x4cNM86tJq7FBMgd4JUKA@mail.gmail.com>
References: <CAP7h-xYvDQCDZxci718nnd_QAyca_W53ZpCnS0bSG11gLYm+uQ@mail.gmail.com>
 <CA+RQFffGx1wPHV2NGGwOoOxvE=+7=jcXFVbUJs=L_0us6mZHFA@mail.gmail.com>
 <CAP7h-xZ5FvEPo6G-7u=h1nafeOQe21KnM=K2NXF4YzR2UtzsVA@mail.gmail.com>
 <CA+RQFfda3nTwjo8r9YLwi0v9sYdhTW1fr5k=B4G9mPC7_ewYxg@mail.gmail.com>
 <CAP7h-xZpUpxnbB6oCiNaKLFm-_EW0x4cNM86tJq7FBMgd4JUKA@mail.gmail.com>
Message-ID: <CAP7h-xaEinRHT_Ln87dgERZEraW=o1+GM5u_HFGSNTt-=tiLHg@mail.gmail.com>

On Tue, Nov 22, 2016 at 3:45 PM, Alexander Belopolsky <
alexander.belopolsky at gmail.com> wrote:
>
>
>  Does anyone know why PyPI did not render README.rst as reST? [2]  It
worked as expected with the previous upload. [3]


Never mind - restructured-lint [1] to the rescue. See [2].

[1]: https://pypi.python.org/pypi/restructuredtext_lint
[2]: https://pypi.python.org/pypi/pytest-leaks/0.2.2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20161122/e14528eb/attachment.html>

From mail at florian-schulze.net  Thu Nov 24 04:44:46 2016
From: mail at florian-schulze.net (Florian Schulze)
Date: Thu, 24 Nov 2016 10:44:46 +0100
Subject: [pytest-dev] pytest-leaks
Message-ID: <FAD59928-A743-4F29-B510-1B6F07FDA137@florian-schulze.net>

Hi!

I tried pytest-leaks with devpi-server and it seems the way tests are 
rerun cause lots of failures there. I get errors like "Threads can only 
be started once" for session fixtures that use threads etc. Not sure if 
that can be fixed, or if fixing it would interfere with looking for 
leaks.

Regards,
Florian Schulze

From eacosta1976 at gmail.com  Thu Nov 24 04:46:31 2016
From: eacosta1976 at gmail.com (Edgar Acosta)
Date: Thu, 24 Nov 2016 10:46:31 +0100
Subject: [pytest-dev] Remove me from this list,
 my email: eacosta1976@gmail.com
Message-ID: <CANWkGLZ9WufYVJLoEanvK0FQ1quz8=C-aq9n_o7OpnGxJEubiw@mail.gmail.com>


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

From me at the-compiler.org  Thu Nov 24 04:52:55 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Thu, 24 Nov 2016 10:52:55 +0100
Subject: [pytest-dev] Remove me from this list,
 my email: eacosta1976@gmail.com
In-Reply-To: <CANWkGLZ9WufYVJLoEanvK0FQ1quz8=C-aq9n_o7OpnGxJEubiw@mail.gmail.com>
References: <CANWkGLZ9WufYVJLoEanvK0FQ1quz8=C-aq9n_o7OpnGxJEubiw@mail.gmail.com>
Message-ID: <20161124095255.awpn22kx7kd2nr2j@tonks>

Hi,

you can unsubscribe yourself by sending a mail with the subject
'unsubscribe' to pytest-dev-request at python.org, or by doing so here:

https://mail.python.org/mailman/options/pytest-dev

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: 801 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20161124/a30d312c/attachment.sig>

From nicoddemus at gmail.com  Mon Nov 28 14:39:51 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Mon, 28 Nov 2016 19:39:51 +0000
Subject: [pytest-dev] t-shirts and stickers now out, thanks Florian!
In-Reply-To: <CAG5CgtqQLsY4qBVNc-OrButf3aYeYiPNhUCOSXmadkMO8v9xKA@mail.gmail.com>
References: <20161025110411.GH4522@merlinux.eu>
 <e33829f4-3804-981f-b9be-9e43ce538e35@ronnypfannschmidt.de>
 <20161025134308.aqo2qbkndd2dhhmr@tonks>
 <CAG5CgtqQLsY4qBVNc-OrButf3aYeYiPNhUCOSXmadkMO8v9xKA@mail.gmail.com>
Message-ID: <CA+RQFff=+PmTCuzhr9+U505RQuoQYm1UErS+QT1yw4u9TkgtWA@mail.gmail.com>

Hi everyone,

Just received mine, the shirt looks really cool!

Thanks Florian and Vasily!

Cheers,

On Thu, Oct 27, 2016 at 8:18 PM Oliver Bestwalter <oliver at bestwalter.de>
wrote:

> Hi Florian,
>
> I really appreciate, that you opted for the harder but better quality
> route. The quality is really good - this comes from an enthusiastic T-Shirt
> wearer since the early 1980s - so thanks for going through all the trouble
> :)
>
> Cheers
> Oliver
>
>
> On Tue, 25 Oct 2016 at 15:43 Florian Bruhin <me at the-compiler.org> wrote:
>
> * Ronny Pfannschmidt <opensource at ronnypfannschmidt.de> [2016-10-25
> 15:15:06 +0200]:
> > Given the funding volumes and used amounts,
> > i wonder if, with the funds that are left, we could have the next
> > sprints sponsored mostly by cooperates
> > next time,
> >
> > I propose that those of us working in a company that could/should
> > participate kick off the
> > "paperwork mill" to see if that idea is viable.
>
> FWIW more than half of the money was already coming from companies.
>
> 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/20161128/7784e956/attachment.html>

From cdent at anticdent.org  Mon Nov 28 16:10:20 2016
From: cdent at anticdent.org (Chris Dent)
Date: Mon, 28 Nov 2016 21:10:20 +0000 (GMT)
Subject: [pytest-dev] process for replacing yield tests with modern style
In-Reply-To: <alpine.OSX.2.20.1610311526360.61205@shine.local>
References: <alpine.OSX.2.20.1608241314340.27225@shine.local>
 <CAA10jzM21GXmOtjvwTXi5PxU5pqoxwkpAb2gSMinMqjZkOO8yA@mail.gmail.com>
 <CAAWk_DwQaOxALy=QUhK0NfrCASsFOEu+OQ4Qu7GcYA2BE36+9A@mail.gmail.com>
 <alpine.OSX.2.20.1610211257070.52839@shine.local>
 <20161022172711.GA4522@merlinux.eu>
 <alpine.OSX.2.20.1610281456040.58669@shine.local>
 <alpine.OSX.2.20.1610311526360.61205@shine.local>
Message-ID: <alpine.OSX.2.20.1611282106290.26802@shine.local>

On Mon, 31 Oct 2016, Chris Dent wrote:
> On Fri, 28 Oct 2016, Chris Dent wrote:
>> * questions when I get stuck with gabbi

I've made some progress on this but I'm still not entirely
satisfied with the solution. I've encapsulate the necessary changes
in a pull request

     https://github.com/cdent/gabbi/pull/187

and tried to make sure that the added docs explain the problem. To
summarize: The current solution requires that the test author
imports a `test_pytest` method into the module in which they create
a pytest_generate_tests hook.

I'd like to avoid that somehow while continuing to support the prior
modes of supported tests and not requiring a conftest.py file.

I feel like I'm missing something obvious that is hard to discern
without a deeper understanding of the available hooks in pytest.

Any suggestions?

-- 
Chris Dent                 ?\_(?)_/?           https://anticdent.org/
freenode: cdent                                         tw: @anticdent

From me at the-compiler.org  Tue Nov 29 00:14:46 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Tue, 29 Nov 2016 06:14:46 +0100
Subject: [pytest-dev] t-shirts and stickers now out, thanks Florian!
In-Reply-To: <CA+RQFff=+PmTCuzhr9+U505RQuoQYm1UErS+QT1yw4u9TkgtWA@mail.gmail.com>
References: <20161025110411.GH4522@merlinux.eu>
 <e33829f4-3804-981f-b9be-9e43ce538e35@ronnypfannschmidt.de>
 <20161025134308.aqo2qbkndd2dhhmr@tonks>
 <CAG5CgtqQLsY4qBVNc-OrButf3aYeYiPNhUCOSXmadkMO8v9xKA@mail.gmail.com>
 <CA+RQFff=+PmTCuzhr9+U505RQuoQYm1UErS+QT1yw4u9TkgtWA@mail.gmail.com>
Message-ID: <20161129051446.lh4md5gukjt65nht@tonks>

Hey,

* Bruno Oliveira <nicoddemus at gmail.com> [2016-11-28 19:39:51 +0000]:
> Just received mine, the shirt looks really cool!

Glad to hear that! Makes me wonder where it was stuck for a month :D

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: 801 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20161129/79626e7e/attachment.sig>

From nicoddemus at gmail.com  Tue Nov 29 05:36:39 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Tue, 29 Nov 2016 10:36:39 +0000
Subject: [pytest-dev] t-shirts and stickers now out, thanks Florian!
In-Reply-To: <20161129051446.lh4md5gukjt65nht@tonks>
References: <20161025110411.GH4522@merlinux.eu>
 <e33829f4-3804-981f-b9be-9e43ce538e35@ronnypfannschmidt.de>
 <20161025134308.aqo2qbkndd2dhhmr@tonks>
 <CAG5CgtqQLsY4qBVNc-OrButf3aYeYiPNhUCOSXmadkMO8v9xKA@mail.gmail.com>
 <CA+RQFff=+PmTCuzhr9+U505RQuoQYm1UErS+QT1yw4u9TkgtWA@mail.gmail.com>
 <20161129051446.lh4md5gukjt65nht@tonks>
Message-ID: <CA+RQFfeFBQytUOTa9QjB48mAb2YutGFDqdQ_ShA7f_cW1437rw@mail.gmail.com>

On Tue, Nov 29, 2016 at 3:14 AM Florian Bruhin <me at the-compiler.org> wrote:

> Hey,
>
> * Bruno Oliveira <nicoddemus at gmail.com> [2016-11-28 19:39:51 +0000]:
> > Just received mine, the shirt looks really cool!
>
> Glad to hear that! Makes me wonder where it was stuck for a month :D
>

Probably on some container somewhere. :D

Using it right now, the fabric is really good. Congrats again!

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

From oliver.schoenborn at gmail.com  Tue Nov 29 06:54:35 2016
From: oliver.schoenborn at gmail.com (oliver)
Date: Tue, 29 Nov 2016 11:54:35 +0000
Subject: [pytest-dev] t-shirts and stickers now out, thanks Florian!
In-Reply-To: <CA+RQFfeFBQytUOTa9QjB48mAb2YutGFDqdQ_ShA7f_cW1437rw@mail.gmail.com>
References: <20161025110411.GH4522@merlinux.eu>
 <e33829f4-3804-981f-b9be-9e43ce538e35@ronnypfannschmidt.de>
 <20161025134308.aqo2qbkndd2dhhmr@tonks>
 <CAG5CgtqQLsY4qBVNc-OrButf3aYeYiPNhUCOSXmadkMO8v9xKA@mail.gmail.com>
 <CA+RQFff=+PmTCuzhr9+U505RQuoQYm1UErS+QT1yw4u9TkgtWA@mail.gmail.com>
 <20161129051446.lh4md5gukjt65nht@tonks>
 <CA+RQFfeFBQytUOTa9QjB48mAb2YutGFDqdQ_ShA7f_cW1437rw@mail.gmail.com>
Message-ID: <CAMb+DaUeeAG1yS5h2MO7pjsi+dyY5iOWk25GqBtfR94m8-6bzQ@mail.gmail.com>

Where can we see it and order?

On Tue, Nov 29, 2016, 5:36 AM Bruno Oliveira <nicoddemus at gmail.com> wrote:

> On Tue, Nov 29, 2016 at 3:14 AM Florian Bruhin <me at the-compiler.org>
> wrote:
>
> Hey,
>
> * Bruno Oliveira <nicoddemus at gmail.com> [2016-11-28 19:39:51 +0000]:
> > Just received mine, the shirt looks really cool!
>
> Glad to hear that! Makes me wonder where it was stuck for a month :D
>
>
> Probably on some container somewhere. :D
>
> Using it right now, the fabric is really good. Congrats again!
>
> Cheers,
> Bruno.
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
-- 
Oliver
My StackOverflow contributions
My CodeProject articles
My Github projects
My SourceForget.net projects
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20161129/12a92ebd/attachment-0001.html>

From me at the-compiler.org  Tue Nov 29 07:53:26 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Tue, 29 Nov 2016 13:53:26 +0100
Subject: [pytest-dev] t-shirts and stickers now out, thanks Florian!
In-Reply-To: <CAMb+DaUeeAG1yS5h2MO7pjsi+dyY5iOWk25GqBtfR94m8-6bzQ@mail.gmail.com>
References: <20161025110411.GH4522@merlinux.eu>
 <e33829f4-3804-981f-b9be-9e43ce538e35@ronnypfannschmidt.de>
 <20161025134308.aqo2qbkndd2dhhmr@tonks>
 <CAG5CgtqQLsY4qBVNc-OrButf3aYeYiPNhUCOSXmadkMO8v9xKA@mail.gmail.com>
 <CA+RQFff=+PmTCuzhr9+U505RQuoQYm1UErS+QT1yw4u9TkgtWA@mail.gmail.com>
 <20161129051446.lh4md5gukjt65nht@tonks>
 <CA+RQFfeFBQytUOTa9QjB48mAb2YutGFDqdQ_ShA7f_cW1437rw@mail.gmail.com>
 <CAMb+DaUeeAG1yS5h2MO7pjsi+dyY5iOWk25GqBtfR94m8-6bzQ@mail.gmail.com>
Message-ID: <20161129125326.bndyo6t3e2orqogp@tonks>

* oliver <oliver.schoenborn at gmail.com> [2016-11-29 11:54:35 +0000]:
> Where can we see it and order?

It looks like this:
https://twitter.com/flubdevork/status/803320121980751873

They were ordered for the pytest crowdfunding and sprint only.

However, we ordered some extra shirts (mainly black, in XL/L/M if I
remember correctly) - I think those should still be around.

If that'd fit you, I suggest you contact Holger (holger at merlinux.eu)
off-list to discuss the details, as the shirts are at his place.

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: 801 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20161129/5db10982/attachment.sig>