From nicoddemus at gmail.com  Thu Aug  4 18:59:51 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 04 Aug 2016 22:59:51 +0000
Subject: [pytest-dev] 3.0 next week?
Message-ID: <CA+RQFfe_GhpLykf9_FHQAwWDiqhpDvCDEnX6hqaAORu1wAar3g@mail.gmail.com>

Hi everyone,

Is everyone OK with releasing pytest 3.0 next week? My idea is to:

1) Early in the week, create and publish a pytest-3.0 package on my devpi
channel [1] and ask people to test it on twitter and the relevant mailing
lists;
2) If there are no blocking issues reported, release it to PyPI on Thursday;
3) Try to be available during the weekend if any major issue comes up to
hopefully provide a quick fix;
4) Profit!

I know few people usually test "unofficial" releases like this, but I would
feel better to do it for a major release like this one.

After pushing the package to PyPI, I would like to publish the "What's new
on Pytest 3.0" [2] blog post, so if somebody still wants to review it
please do so until then.

Cheers,
Bruno.

[1] https://devpi.net/nicoddemus/dev
[2] https://github.com/pytest-dev/blog.pytest.org/pull/11
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160804/f29c756a/attachment.html>

From me at the-compiler.org  Fri Aug  5 06:09:52 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Fri, 5 Aug 2016 12:09:52 +0200
Subject: [pytest-dev] 3.0 next week?
In-Reply-To: <CA+RQFfe_GhpLykf9_FHQAwWDiqhpDvCDEnX6hqaAORu1wAar3g@mail.gmail.com>
References: <CA+RQFfe_GhpLykf9_FHQAwWDiqhpDvCDEnX6hqaAORu1wAar3g@mail.gmail.com>
Message-ID: <20160805100952.wginy5lb4bpuidxj@tonks>

Hey,

my 0.02 $currency on this:

* Bruno Oliveira <nicoddemus at gmail.com> [2016-08-04 22:59:51 +0000]:
> Is everyone OK with releasing pytest 3.0 next week? My idea is to:

I'd love that, but let's take a quick look at what we *wanted* in 3.0
first.

Anything which is not either a bug introduced since the last release,
or a backwards-incompatible change should be postponed to 3.1 (i.e.
its milestone adjusted), or postponed indefinitely (i.e. its milestone
removed).

----

On the wiki page I checked some stuff which is done already, now "doc
restructuring" and "fixture conftest sharing" is still there:

https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist

I have no idea what the latter is, but the doc restructuring probably
will still take a while and shouldn't block 3.0.

----

On GitHub, we still have some 30 open issues marked as 3.0:
https://github.com/pytest-dev/pytest/milestone/2

I closed some which are already fixed (but not auto-closed because PRs
were merged to features and not master).

Now which of those are important, relatively easy, backwards
incompatible changes? Should we do those before releasing 3.0?

I really wouldn't want to release 3.0 with 28 open issues where we
don't know if they should go to 3.0 or not ;)

----

We also have four open PRs. From my POV:

Almost ready and should go to 3.0:
https://github.com/pytest-dev/pytest/pull/1791
https://github.com/pytest-dev/pytest/pull/1621

No idea what state they're in:
https://github.com/pytest-dev/pytest/pull/1661 (Ronny?)
https://github.com/pytest-dev/pytest/pull/1394
(no answer from @s0undt3ch)

Florian

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

From me at the-compiler.org  Fri Aug  5 08:27:06 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Fri, 5 Aug 2016 14:27:06 +0200
Subject: [pytest-dev] 3.0 next week?
In-Reply-To: <20160805100952.wginy5lb4bpuidxj@tonks>
 <CA+RQFfe_GhpLykf9_FHQAwWDiqhpDvCDEnX6hqaAORu1wAar3g@mail.gmail.com>
Message-ID: <20160805122706.tyse4y7dzfjw6xft@tonks>

Hey,

* Bruno Oliveira <nicoddemus at gmail.com> [2016-08-04 22:59:51 +0000]:
> 1) Early in the week, create and publish a pytest-3.0 package on my devpi
> channel [1] and ask people to test it on twitter and the relevant mailing
> lists;
> 2) If there are no blocking issues reported, release it to PyPI on Thursday;
> 3) Try to be available during the weekend if any major issue comes up to
> hopefully provide a quick fix;

I just tried the current features branch with the qutebrowser
testsuite, and noticed various things, roughly ordered by importance:

- I get a RecursionError in pluggy during teardown of one of my
  fixtures: https://github.com/pytest-dev/pytest/issues/1794

- pytest-bdd breaks in multiple ways, and I gave up trying to get it
  to work: https://github.com/pytest-dev/pytest-bdd/pull/193

- pytest-{cov,rerunfailures,repeat} cause a DeprecationWarning by
  passing a string argument to addoption:
  https://github.com/pytest-dev/pytest-repeat/pull/11
  https://github.com/pytest-dev/pytest-cov/pull/127
  https://github.com/pytest-dev/pytest-rerunfailures/pull/36

- Something really funny I can't explain is broken in
  pytest-rerunfailures setup.py: (not pytest 3.0 related, but odd)
  https://github.com/pytest-dev/pytest-rerunfailures/issues/35

> On GitHub, we still have some 30 open issues marked as 3.0:
> https://github.com/pytest-dev/pytest/milestone/2
> 
> I closed some which are already fixed (but not auto-closed because PRs
> were merged to features and not master).

I also retargeted some, and added comments for others where I was
unsure. Let's clean this up :)

Florian

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

From nicoddemus at gmail.com  Fri Aug  5 19:01:46 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Fri, 05 Aug 2016 23:01:46 +0000
Subject: [pytest-dev] 3.0 next week?
In-Reply-To: <20160805122706.tyse4y7dzfjw6xft@tonks>
References: <20160805100952.wginy5lb4bpuidxj@tonks>
 <CA+RQFfe_GhpLykf9_FHQAwWDiqhpDvCDEnX6hqaAORu1wAar3g@mail.gmail.com>
 <20160805122706.tyse4y7dzfjw6xft@tonks>
Message-ID: <CA+RQFferk6mzfyqvbjjVzaU7d0ypuBX-v4Xe_2NsK-PG9cspmw@mail.gmail.com>

On Fri, Aug 5, 2016 at 9:27 AM Florian Bruhin <me at the-compiler.org> wrote:

> I just tried the current features branch with the qutebrowser
> testsuite, and noticed various things, roughly ordered by importance:
>
> - I get a RecursionError in pluggy during teardown of one of my
>   fixtures: https://github.com/pytest-dev/pytest/issues/1794


This one seems pretty serious, I will try to take a look tomorrow.

- pytest-bdd breaks in multiple ways, and I gave up trying to get it
>   to work: https://github.com/pytest-dev/pytest-bdd/pull/193
>
> - pytest-{cov,rerunfailures,repeat} cause a DeprecationWarning by
>   passing a string argument to addoption:
>   https://github.com/pytest-dev/pytest-repeat/pull/11
>   https://github.com/pytest-dev/pytest-cov/pull/127
>   https://github.com/pytest-dev/pytest-rerunfailures/pull/36


Nice work on the PRs! :)

It would be nice of the authors of those plugins to publish a new release
before pytest-3.0 is out.


> I also retargeted some, and added comments for others where I was
> unsure. Let's clean this up :)
>

I agree, and thanks for taking the time to comment and review all the
issues! :)

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

From flub at devork.be  Sun Aug  7 18:43:50 2016
From: flub at devork.be (Floris Bruynooghe)
Date: Sun, 7 Aug 2016 23:43:50 +0100
Subject: [pytest-dev] py._code
Message-ID: <CAAWk_Dy3ZQ15wt1K9F2NkOuF+h63fnVsOCzO8W08B6ksVojR=A@mail.gmail.com>

Hi,

We did move the py._code library over to pytest._code a little while
ago, I wasn't really involved so don't remember the details.  But
seems it was never removed from the py library itself.  Was this on
purpose?  Do we want to maintain two versions of this code?

Reason I'm asking is because the version in py currently has two test
failures.  If this code now lives in pytest then I'd rather rip it out
from py.  Any objections?


Floris

From opensource at ronnypfannschmidt.de  Mon Aug  8 01:48:53 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Mon, 08 Aug 2016 07:48:53 +0200
Subject: [pytest-dev] py._code
In-Reply-To: <CAAWk_Dy3ZQ15wt1K9F2NkOuF+h63fnVsOCzO8W08B6ksVojR=A@mail.gmail.com>
References: <CAAWk_Dy3ZQ15wt1K9F2NkOuF+h63fnVsOCzO8W08B6ksVojR=A@mail.gmail.com>
Message-ID: <436089B6-E02A-4CDD-90F9-61977CC8E958@ronnypfannschmidt.de>

That would break external code
Pylib is maintenance-only


-- Ronny

Am 8. August 2016 00:43:50 MESZ, schrieb Floris Bruynooghe <flub at devork.be>:
>Hi,
>
>We did move the py._code library over to pytest._code a little while
>ago, I wasn't really involved so don't remember the details.  But
>seems it was never removed from the py library itself.  Was this on
>purpose?  Do we want to maintain two versions of this code?
>
>Reason I'm asking is because the version in py currently has two test
>failures.  If this code now lives in pytest then I'd rather rip it out
>from py.  Any objections?
>
>
>Floris
>_______________________________________________
>pytest-dev mailing list
>pytest-dev at python.org
>https://mail.python.org/mailman/listinfo/pytest-dev


From me at the-compiler.org  Mon Aug  8 06:13:02 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Mon, 8 Aug 2016 12:13:02 +0200
Subject: [pytest-dev] pytest and Mozilla's Open Source Support program
Message-ID: <20160808101302.zc4c425i53hwtoml@tonks>

Hey,

via [1] (German) I just stumbled upon Mozilla's MOSS program[2].

They have a track[3] where they found generic OSS projects furthering
their mission, and another one[4] (probably more relevant to us) where
they fund projects they use themselves. From what I've seen via
Dave Hunt, Mozilla is quite a heavy pytest user with various plugins
they wrote.

The grants are between $10k and $250k. If time permits, this could
e.g. be used by Merlinux (i.e., Holger's company) to allow someone to
work on pytest (or possibly, tox/devpi - not sure if those are used at
Mozilla too?) full-time for a while.

It seems for the next round of founding, we'd have to apply until the
end of August.

I haven't really thought much about it yet, just thought I'd throw it
out here - thoughts?

Florian

[1] http://www.heise.de/developer/meldung/Mozilla-nimmt-PyPy-in-Foerderprogramm-auf-3289656.html
[2] https://wiki.mozilla.org/MOSS
[3] https://wiki.mozilla.org/MOSS/Mission_Partners
[4] https://wiki.mozilla.org/MOSS/Foundational_Technology

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

From sivan at vitakka.co  Mon Aug  8 07:20:32 2016
From: sivan at vitakka.co (Sivan Greenberg)
Date: Mon, 8 Aug 2016 14:20:32 +0300
Subject: [pytest-dev] pytest and Mozilla's Open Source Support program
In-Reply-To: <20160808101302.zc4c425i53hwtoml@tonks>
References: <20160808101302.zc4c425i53hwtoml@tonks>
Message-ID: <CAMB+yF2UnAuspq51rkuCPZKMr+zA2513bZ6NEr9vfwrNSnTgWA@mail.gmail.com>

Hi Florian & List

 If help is needed in taking care of filling the forms and submitting this
with instructions from project leads, I would be interested. Even though I
did not manage to attend the sprint, I remained excited in furthering
pytest's goals and the surrounding 'ecosystem' (e.g. tox and friends).

 Since I'm now free of my last project,   I'd love to help the coding as
well, if project lead think I can be of that help. Ideally I feel that we
should start attracting student or fresh graduates as 'interns' and enlarge
the contributors list.

 P.S. Has anybody documented the sprint in a free form documentation  or
were they only closed bugs in the issue tracker and new commits made?  :) I
would love to read some summary of the sprint achievements and it's story
as I really feel I missed. Do we have the similar to peps?

Thanks! (for pytest as well),

-Sivan

On Mon, Aug 8, 2016 at 1:13 PM, Florian Bruhin <me at the-compiler.org> wrote:

> Hey,
>
> via [1] (German) I just stumbled upon Mozilla's MOSS program[2].
>
> They have a track[3] where they found generic OSS projects furthering
> their mission, and another one[4] (probably more relevant to us) where
> they fund projects they use themselves. From what I've seen via
> Dave Hunt, Mozilla is quite a heavy pytest user with various plugins
> they wrote.
>
> The grants are between $10k and $250k. If time permits, this could
> e.g. be used by Merlinux (i.e., Holger's company) to allow someone to
> work on pytest (or possibly, tox/devpi - not sure if those are used at
> Mozilla too?) full-time for a while.
>
> It seems for the next round of founding, we'd have to apply until the
> end of August.
>
> I haven't really thought much about it yet, just thought I'd throw it
> out here - thoughts?
>
> Florian
>
> [1] http://www.heise.de/developer/meldung/Mozilla-nimmt-PyPy-in-
> Foerderprogramm-auf-3289656.html
> [2] https://wiki.mozilla.org/MOSS
> [3] https://wiki.mozilla.org/MOSS/Mission_Partners
> [4] https://wiki.mozilla.org/MOSS/Foundational_Technology
>
> --
> 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
>
>


-- 
Sivan Greenberg
Co founder & CTO
Vitakka Consulting
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160808/9cdbf555/attachment.html>

From sivan at vitakka.co  Mon Aug  8 07:21:49 2016
From: sivan at vitakka.co (Sivan Greenberg)
Date: Mon, 8 Aug 2016 14:21:49 +0300
Subject: [pytest-dev] pytest and Mozilla's Open Source Support program
In-Reply-To: <CAMB+yF2UnAuspq51rkuCPZKMr+zA2513bZ6NEr9vfwrNSnTgWA@mail.gmail.com>
References: <20160808101302.zc4c425i53hwtoml@tonks>
 <CAMB+yF2UnAuspq51rkuCPZKMr+zA2513bZ6NEr9vfwrNSnTgWA@mail.gmail.com>
Message-ID: <CAMB+yF1HQtkDXyw+deB0jj8qZMtEwrwF56acdAr2U5zarfnX5A@mail.gmail.com>

P.S.S If not already done so, we should start also enlist in GSoCs /
PyLadies / etc projects to maybe get some attention there as well.

-Sivan

On Mon, Aug 8, 2016 at 2:20 PM, Sivan Greenberg <sivan at vitakka.co> wrote:

> Hi Florian & List
>
>  If help is needed in taking care of filling the forms and submitting this
> with instructions from project leads, I would be interested. Even though I
> did not manage to attend the sprint, I remained excited in furthering
> pytest's goals and the surrounding 'ecosystem' (e.g. tox and friends).
>
>  Since I'm now free of my last project,   I'd love to help the coding as
> well, if project lead think I can be of that help. Ideally I feel that we
> should start attracting student or fresh graduates as 'interns' and enlarge
> the contributors list.
>
>  P.S. Has anybody documented the sprint in a free form documentation  or
> were they only closed bugs in the issue tracker and new commits made?  :) I
> would love to read some summary of the sprint achievements and it's story
> as I really feel I missed. Do we have the similar to peps?
>
> Thanks! (for pytest as well),
>
> -Sivan
>
> On Mon, Aug 8, 2016 at 1:13 PM, Florian Bruhin <me at the-compiler.org>
> wrote:
>
>> Hey,
>>
>> via [1] (German) I just stumbled upon Mozilla's MOSS program[2].
>>
>> They have a track[3] where they found generic OSS projects furthering
>> their mission, and another one[4] (probably more relevant to us) where
>> they fund projects they use themselves. From what I've seen via
>> Dave Hunt, Mozilla is quite a heavy pytest user with various plugins
>> they wrote.
>>
>> The grants are between $10k and $250k. If time permits, this could
>> e.g. be used by Merlinux (i.e., Holger's company) to allow someone to
>> work on pytest (or possibly, tox/devpi - not sure if those are used at
>> Mozilla too?) full-time for a while.
>>
>> It seems for the next round of founding, we'd have to apply until the
>> end of August.
>>
>> I haven't really thought much about it yet, just thought I'd throw it
>> out here - thoughts?
>>
>> Florian
>>
>> [1] http://www.heise.de/developer/meldung/Mozilla-nimmt-PyPy-in-
>> Foerderprogramm-auf-3289656.html
>> [2] https://wiki.mozilla.org/MOSS
>> [3] https://wiki.mozilla.org/MOSS/Mission_Partners
>> [4] https://wiki.mozilla.org/MOSS/Foundational_Technology
>>
>> --
>> 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
>>
>>
>
>
> --
> Sivan Greenberg
> Co founder & CTO
> Vitakka Consulting
>



-- 
Sivan Greenberg
Co founder & CTO
Vitakka Consulting
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160808/173652ae/attachment-0001.html>

From me at the-compiler.org  Mon Aug  8 07:24:39 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Mon, 8 Aug 2016 13:24:39 +0200
Subject: [pytest-dev] pytest and Mozilla's Open Source Support program
In-Reply-To: <CAMB+yF2UnAuspq51rkuCPZKMr+zA2513bZ6NEr9vfwrNSnTgWA@mail.gmail.com>
References: <20160808101302.zc4c425i53hwtoml@tonks>
 <CAMB+yF2UnAuspq51rkuCPZKMr+zA2513bZ6NEr9vfwrNSnTgWA@mail.gmail.com>
Message-ID: <20160808112439.garzlmqiipmfuzsu@tonks>

* Sivan Greenberg <sivan at vitakka.co> [2016-08-08 14:20:32 +0300]:
>  P.S. Has anybody documented the sprint in a free form documentation  or
> were they only closed bugs in the issue tracker and new commits made?  :) I
> would love to read some summary of the sprint achievements and it's story
> as I really feel I missed. Do we have the similar to peps?

There was a blog post:
http://blog.pytest.org/2016/pytest-development-sprint/

Florian

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

From nicoddemus at gmail.com  Mon Aug  8 09:37:58 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Mon, 08 Aug 2016 13:37:58 +0000
Subject: [pytest-dev] pytest and Mozilla's Open Source Support program
In-Reply-To: <20160808101302.zc4c425i53hwtoml@tonks>
References: <20160808101302.zc4c425i53hwtoml@tonks>
Message-ID: <CA+RQFfcyQQsJO1aCP-=Y6r+QN-jVxxbdVj4ajBOrjUitqzHAUg@mail.gmail.com>

On Mon, Aug 8, 2016 at 7:13 AM Florian Bruhin <me at the-compiler.org> wrote:

> Hey,
>
> via [1] (German) I just stumbled upon Mozilla's MOSS program[2].
>
> They have a track[3] where they found generic OSS projects furthering
> their mission, and another one[4] (probably more relevant to us) where
> they fund projects they use themselves. From what I've seen via
> Dave Hunt, Mozilla is quite a heavy pytest user with various plugins
> they wrote.
>
> The grants are between $10k and $250k. If time permits, this could
> e.g. be used by Merlinux (i.e., Holger's company) to allow someone to
> work on pytest (or possibly, tox/devpi - not sure if those are used at
> Mozilla too?) full-time for a while.
>

That sounds great, but first we would need to find someone willing to do
the work. Does anybody on the mailing list volunteers? I can't volunteer
myself as I already have a full time job.

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

From mail at florian-schulze.net  Mon Aug  8 09:57:15 2016
From: mail at florian-schulze.net (Florian Schulze)
Date: Mon, 08 Aug 2016 15:57:15 +0200
Subject: [pytest-dev] pytest and Mozilla's Open Source Support program
In-Reply-To: <CA+RQFfcyQQsJO1aCP-=Y6r+QN-jVxxbdVj4ajBOrjUitqzHAUg@mail.gmail.com>
References: <20160808101302.zc4c425i53hwtoml@tonks>
 <CA+RQFfcyQQsJO1aCP-=Y6r+QN-jVxxbdVj4ajBOrjUitqzHAUg@mail.gmail.com>
Message-ID: <449D65F4-2061-4E16-81B2-57AC6A6CED84@florian-schulze.net>

Hi!

I know Holger is on vacation for a while. I doubt he got time to handle 
this in August.

I would be available for development work. I got no experience with 
organizational and legal stuff in regard to US based foundations when 
living in Germany.

Regards,
Florian Schulze

On 8 Aug 2016, at 15:37, Bruno Oliveira wrote:

> On Mon, Aug 8, 2016 at 7:13 AM Florian Bruhin <me at the-compiler.org> 
> wrote:
>
>> Hey,
>>
>> via [1] (German) I just stumbled upon Mozilla's MOSS program[2].
>>
>> They have a track[3] where they found generic OSS projects furthering
>> their mission, and another one[4] (probably more relevant to us) 
>> where
>> they fund projects they use themselves. From what I've seen via
>> Dave Hunt, Mozilla is quite a heavy pytest user with various plugins
>> they wrote.
>>
>> The grants are between $10k and $250k. If time permits, this could
>> e.g. be used by Merlinux (i.e., Holger's company) to allow someone to
>> work on pytest (or possibly, tox/devpi - not sure if those are used 
>> at
>> Mozilla too?) full-time for a while.
>>
>
> That sounds great, but first we would need to find someone willing to 
> do
> the work. Does anybody on the mailing list volunteers? I can't 
> volunteer
> myself as I already have a full time job.
>
> Cheers,
> Bruno
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev

From flub at devork.be  Mon Aug  8 10:08:36 2016
From: flub at devork.be (Floris Bruynooghe)
Date: Mon, 8 Aug 2016 15:08:36 +0100
Subject: [pytest-dev] py._code
In-Reply-To: <436089B6-E02A-4CDD-90F9-61977CC8E958@ronnypfannschmidt.de>
References: <CAAWk_Dy3ZQ15wt1K9F2NkOuF+h63fnVsOCzO8W08B6ksVojR=A@mail.gmail.com>
 <436089B6-E02A-4CDD-90F9-61977CC8E958@ronnypfannschmidt.de>
Message-ID: <CAAWk_DzWoh2ZhOFBJyD0w2EajO=Vw9wnxYP=0cxE+1EyShDpPQ@mail.gmail.com>

On 8 August 2016 at 06:48, Ronny Pfannschmidt
<opensource at ronnypfannschmidt.de> wrote:
> That would break external code

Uhm, so we've committed to mainting py._code in two places?  Makes me
wonder what the motivation to merge into pytest was.

> Pylib is maintenance-only

While it's not terribly actively developed there's still scope for new
features I think.  E.g. the PR for PEP 519 support counts as a new
features, I wouldn't want to block it.

Floris

From opensource at ronnypfannschmidt.de  Mon Aug  8 13:04:06 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Mon, 8 Aug 2016 19:04:06 +0200
Subject: [pytest-dev] py._code
In-Reply-To: <CAAWk_DzWoh2ZhOFBJyD0w2EajO=Vw9wnxYP=0cxE+1EyShDpPQ@mail.gmail.com>
References: <CAAWk_Dy3ZQ15wt1K9F2NkOuF+h63fnVsOCzO8W08B6ksVojR=A@mail.gmail.com>
 <436089B6-E02A-4CDD-90F9-61977CC8E958@ronnypfannschmidt.de>
 <CAAWk_DzWoh2ZhOFBJyD0w2EajO=Vw9wnxYP=0cxE+1EyShDpPQ@mail.gmail.com>
Message-ID: <a12a75b5-abfa-6f3f-a793-3b3fddf88188@ronnypfannschmidt.de>



On 08.08.2016 16:08, Floris Bruynooghe wrote:
> On 8 August 2016 at 06:48, Ronny Pfannschmidt
> <opensource at ronnypfannschmidt.de> wrote:
>> That would break external code
> Uhm, so we've committed to mainting py._code in two places?  Makes me
> wonder what the motivation to merge into pytest was.
no, pylib will no longer evolve, its a relative dead end
the main reason to copy it is, that now that it is mostly an internal 
api, we are allowed to change it without breaking downstreams - we moved 
it so we can change it again.
>> Pylib is maintenance-only
> While it's not terribly actively developed there's still scope for new
> features I think.  E.g. the PR for PEP 519 support counts as a new
> features, I wouldn't want to block it.
the ideal case there is to eventually get rid pf py.path - in particular 
since pathlib/pathlib2 is the way to go on more recent python and 
py.path is really hairy to evolve

pep 519 as addition is not really a evolution i'd argue - however we are 
unable to ever do that correct with py.path due to its broken bytes vs 
unicode semantics that we cannot fix without subtle breakages of 
downstream (hence the idea of eventually no longer needing pylib as its 
under bad constraints wrt evolving it)
>
> Floris


-- Ronny

From sivan at vitakka.co  Tue Aug  9 05:35:52 2016
From: sivan at vitakka.co (Sivan Greenberg)
Date: Tue, 9 Aug 2016 12:35:52 +0300
Subject: [pytest-dev] pytest and Mozilla's Open Source Support program
In-Reply-To: <449D65F4-2061-4E16-81B2-57AC6A6CED84@florian-schulze.net>
References: <20160808101302.zc4c425i53hwtoml@tonks>
 <CA+RQFfcyQQsJO1aCP-=Y6r+QN-jVxxbdVj4ajBOrjUitqzHAUg@mail.gmail.com>
 <449D65F4-2061-4E16-81B2-57AC6A6CED84@florian-schulze.net>
Message-ID: <CAMB+yF0RguavGLKViaKroHyHm1rPs2LFdyR517KS9ci9g1P-Ww@mail.gmail.com>

Hi again,

 I am happy to volunteer for that - I will sure need to ask people here for
data that I cannot find myself. I have had experience working with US based
Linux foundation ,GSoC and the Freescale  organizations, I think this
should not be too much different and not a huge task.

 If anybody here is happy with me attempting at that, I'll set to do it. I
will also be highly keen on doing even part of the development, so doing
community and coding is much fun :)

-Sivan

On Mon, Aug 8, 2016 at 4:57 PM, Florian Schulze <mail at florian-schulze.net>
wrote:

> Hi!
>
> I know Holger is on vacation for a while. I doubt he got time to handle
> this in August.
>
> I would be available for development work. I got no experience with
> organizational and legal stuff in regard to US based foundations when
> living in Germany.
>
> Regards,
> Florian Schulze
>
>
> On 8 Aug 2016, at 15:37, Bruno Oliveira wrote:
>
> On Mon, Aug 8, 2016 at 7:13 AM Florian Bruhin <me at the-compiler.org> wrote:
>>
>> Hey,
>>>
>>> via [1] (German) I just stumbled upon Mozilla's MOSS program[2].
>>>
>>> They have a track[3] where they found generic OSS projects furthering
>>> their mission, and another one[4] (probably more relevant to us) where
>>> they fund projects they use themselves. From what I've seen via
>>> Dave Hunt, Mozilla is quite a heavy pytest user with various plugins
>>> they wrote.
>>>
>>> The grants are between $10k and $250k. If time permits, this could
>>> e.g. be used by Merlinux (i.e., Holger's company) to allow someone to
>>> work on pytest (or possibly, tox/devpi - not sure if those are used at
>>> Mozilla too?) full-time for a while.
>>>
>>>
>> That sounds great, but first we would need to find someone willing to do
>> the work. Does anybody on the mailing list volunteers? I can't volunteer
>> myself as I already have a full time job.
>>
>> Cheers,
>> Bruno
>> _______________________________________________
>> 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
>



-- 
Sivan Greenberg
Co founder & CTO
Vitakka Consulting
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160809/77c4425b/attachment.html>

From nicoddemus at gmail.com  Sun Aug 14 21:15:14 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Mon, 15 Aug 2016 01:15:14 +0000
Subject: [pytest-dev] Remove invocation fixtures from 3.0?
Message-ID: <CA+RQFffJUTH=Cefsw64RtW_h5ik8h7-DqYdf7iAhE1fc5=LCvA@mail.gmail.com>

Hi everyone,

I've worked on the weekend on the issue discovered by Florian on the
qutebrowser test suite, and unfortunately I think the current
implementation will have to be re-thought because it contains a serious
problem regarding finalizers when fixtures are being overwritten.

Because redesigning it might take a awhile, I suggest we remove invocation
fixtures for now so we can make the 3.0 release. We can then work this week
on the remaining issues[1] and make a release candidate by the middle of
the week, aiming for the official release by the end of the week.

How does that sound?

Cheers,
Bruno.

[1] https://github.com/pytest-dev/pytest/milestone/2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160815/d9121376/attachment.html>

From mail at florian-schulze.net  Mon Aug 15 04:43:15 2016
From: mail at florian-schulze.net (Florian Schulze)
Date: Mon, 15 Aug 2016 10:43:15 +0200
Subject: [pytest-dev] Remove invocation fixtures from 3.0?
In-Reply-To: <CA+RQFffJUTH=Cefsw64RtW_h5ik8h7-DqYdf7iAhE1fc5=LCvA@mail.gmail.com>
References: <CA+RQFffJUTH=Cefsw64RtW_h5ik8h7-DqYdf7iAhE1fc5=LCvA@mail.gmail.com>
Message-ID: <CD20380A-3E07-43E6-A32D-120BBF37D6E6@florian-schulze.net>

Hi!

Since this is not a breaking change, but a feature, it can easily be 
added in 3.1, right? If so, I'd say postpone it.

Regards,
Florian Schulze


On 15 Aug 2016, at 3:15, Bruno Oliveira wrote:

> Hi everyone,
>
> I've worked on the weekend on the issue discovered by Florian on the
> qutebrowser test suite, and unfortunately I think the current
> implementation will have to be re-thought because it contains a 
> serious
> problem regarding finalizers when fixtures are being overwritten.
>
> Because redesigning it might take a awhile, I suggest we remove 
> invocation
> fixtures for now so we can make the 3.0 release. We can then work this 
> week
> on the remaining issues[1] and make a release candidate by the middle 
> of
> the week, aiming for the official release by the end of the week.
>
> How does that sound?
>
> Cheers,
> Bruno.
>
> [1] https://github.com/pytest-dev/pytest/milestone/2
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev

From flub at devork.be  Mon Aug 15 07:32:46 2016
From: flub at devork.be (Floris Bruynooghe)
Date: Mon, 15 Aug 2016 12:32:46 +0100
Subject: [pytest-dev] Remove invocation fixtures from 3.0?
In-Reply-To: <CD20380A-3E07-43E6-A32D-120BBF37D6E6@florian-schulze.net>
References: <CA+RQFffJUTH=Cefsw64RtW_h5ik8h7-DqYdf7iAhE1fc5=LCvA@mail.gmail.com>
 <CD20380A-3E07-43E6-A32D-120BBF37D6E6@florian-schulze.net>
Message-ID: <CAAWk_Dy38NyT_sarOGfQMdgEDRn+bm-xD2XCBVza2TitXHtLgA@mail.gmail.com>

On 15 Aug 2016 09:43, "Florian Schulze" <mail at florian-schulze.net> wrote:
> Since this is not a breaking change, but a feature, it can easily be
added in 3.1, right? If so, I'd say postpone it.

Seems like a sensible choice, +1

Floris

> On 15 Aug 2016, at 3:15, Bruno Oliveira wrote:
>
>> Hi everyone,
>>
>> I've worked on the weekend on the issue discovered by Florian on the
>> qutebrowser test suite, and unfortunately I think the current
>> implementation will have to be re-thought because it contains a serious
>> problem regarding finalizers when fixtures are being overwritten.
>>
>> Because redesigning it might take a awhile, I suggest we remove
invocation
>> fixtures for now so we can make the 3.0 release. We can then work this
week
>> on the remaining issues[1] and make a release candidate by the middle of
>> the week, aiming for the official release by the end of the week.
>>
>> How does that sound?
>>
>> Cheers,
>> Bruno.
>>
>> [1] https://github.com/pytest-dev/pytest/milestone/2
>> _______________________________________________
>> 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/20160815/e6365e2c/attachment.html>

From me at the-compiler.org  Mon Aug 15 15:15:07 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Mon, 15 Aug 2016 21:15:07 +0200
Subject: [pytest-dev] GitHub and PR base branch switching
Message-ID: <20160815191507.h4egzyzqviri4ign@tonks>

Hey,

good news, GitHub now allows to switch the base branch for pull
requests:
https://github.com/blog/2224-change-the-base-branch-of-a-pull-request

Some while ago they also added notifications for new PR pushes:
https://github.com/blog/2203-email-updates-about-your-own-activity
(at the bottom)

So... yay, stuff is getting better! \o/

Florian

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

From me at the-compiler.org  Mon Aug 15 15:22:33 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Mon, 15 Aug 2016 21:22:33 +0200
Subject: [pytest-dev] Remove invocation fixtures from 3.0?
In-Reply-To: <CA+RQFffJUTH=Cefsw64RtW_h5ik8h7-DqYdf7iAhE1fc5=LCvA@mail.gmail.com>
References: <CA+RQFffJUTH=Cefsw64RtW_h5ik8h7-DqYdf7iAhE1fc5=LCvA@mail.gmail.com>
Message-ID: <20160815192233.rntw3xjbozqvef7m@tonks>

Hey,

* Bruno Oliveira <nicoddemus at gmail.com> [2016-08-15 01:15:14 +0000]:
> I've worked on the weekend on the issue discovered by Florian on the
> qutebrowser test suite, and unfortunately I think the current
> implementation will have to be re-thought because it contains a serious
> problem regarding finalizers when fixtures are being overwritten.

Thanks for all the debugging and all the other great work you do to
get 3.0 out! :)

> Because redesigning it might take a awhile, I suggest we remove invocation
> fixtures for now so we can make the 3.0 release. We can then work this week
> on the remaining issues[1] and make a release candidate by the middle of
> the week, aiming for the official release by the end of the week.
> 
> How does that sound?

I agree with the other Flori.* people :D

I guess it's better to take them out and reintroduce them in 3.1 with
the rough edges smoothened out than breaking stuff now.

Florian

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

From nicoddemus at gmail.com  Mon Aug 15 15:38:02 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Mon, 15 Aug 2016 19:38:02 +0000
Subject: [pytest-dev] GitHub and PR base branch switching
In-Reply-To: <20160815191507.h4egzyzqviri4ign@tonks>
References: <20160815191507.h4egzyzqviri4ign@tonks>
Message-ID: <CA+RQFfe9FYRq878haS_SLQ9Z2YSyBWu6ksLyVg1B+ULiR9-cXg@mail.gmail.com>

On Mon, Aug 15, 2016 at 4:20 PM Florian Bruhin <me at the-compiler.org> wrote:

> Hey,
>
> good news, GitHub now allows to switch the base branch for pull
> requests:
> https://github.com/blog/2224-change-the-base-branch-of-a-pull-request


Cool! \o/

[]s
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160815/7aa4d5a4/attachment.html>

From nicoddemus at gmail.com  Mon Aug 15 21:44:53 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Tue, 16 Aug 2016 01:44:53 +0000
Subject: [pytest-dev] Remove invocation fixtures from 3.0?
In-Reply-To: <20160815192233.rntw3xjbozqvef7m@tonks>
References: <CA+RQFffJUTH=Cefsw64RtW_h5ik8h7-DqYdf7iAhE1fc5=LCvA@mail.gmail.com>
 <20160815192233.rntw3xjbozqvef7m@tonks>
Message-ID: <CA+RQFfdwwaiHByBhvG4guyHGrvJywoptVx=jVnZA1_nVkOgABA@mail.gmail.com>

I guess it?s better to take them out and reintroduce them in 3.1 with
the rough edges smoothened out than breaking stuff now.

Thanks everyone for the feedback.

While further debugging the issue, I managed to isolate the problem in a
small reproducible case, similar to what is found in qutebrowser?s test
suite. Problem is, I can?t explain the behavior I?m seeing, both in master
and in the features branches.

Consider these files (mind the directory layout):

# ---------- contents of tests/conftest.py ----------import pytest
@pytest.yield_fixture(scope='session')def app(app):
    yield 'customapp'
@pytest.yield_fixture(scope='session', autouse=True)def httpbin(app):
    yield
# ---------- contents of tests/test_dummy.py ----------import pytest
@pytest.mark.parametrize('i', range(10))def test_dummy(i, request):
    finalizers = request._fixturemanager._arg2fixturedefs['app'][0]._finalizer
    assert len(finalizers) == 1
# ---------- contents of ./conftest.py ----------import pytest
@pytest.yield_fixture(scope='session')def app():
    yield 'app'

Running this produces (cutting out some of the output):

$ py.test
============================= test session starts =============================
platform win32 -- Python 3.5.0, pytest-2.9.3.dev0, py-1.4.31, pluggy-0.3.1
rootdir: X:\pytest\tmp\bug, inifile: pytest.ini
plugins: hypothesis-3.1.0, xdist-1.14
collected 10 items

tests\test_dummy.py FFFFFFFFFF

================================== FAILURES ===================================
________________________________ test_dummy[0] ________________________________

i = 0, request = <FixtureRequest for <Function 'test_dummy[0]'>>

    @pytest.mark.parametrize('i', range(10))
    def test_dummy(i, request):
        finalizers =
request._fixturemanager._arg2fixturedefs['app'][0]._finalizer
>       assert len(finalizers) == 1
E       assert 2 == 1
E        +  where 2 = len([<function
call_fixture_func.<locals>.teardown at 0x034C3198>, <bound method
FixtureDef.finish of <FixtureDef name='app' scope='session'
baseid='tests' >>])

tests\test_dummy.py:7: AssertionError
________________________________ test_dummy[1] ________________________________

i = 1, request = <FixtureRequest for <Function 'test_dummy[1]'>>

    @pytest.mark.parametrize('i', range(10))
    def test_dummy(i, request):
        finalizers =
request._fixturemanager._arg2fixturedefs['app'][0]._finalizer
>       assert len(finalizers) == 1
E       assert 3 == 1
E        +  where 3 = len([<function
call_fixture_func.<locals>.teardown at 0x034C3198>, <bound method
FixtureDef.finish of <FixtureDef name='ap...ession' baseid='tests' >>,
<bound method FixtureDef.finish of <FixtureDef name='app'
scope='session' baseid='tests' >>])

tests\test_dummy.py:7: AssertionError

(and it continues...)
________________________________ test_dummy[9] ________________________________

i = 9, request = <FixtureRequest for <Function 'test_dummy[9]'>>

    @pytest.mark.parametrize('i', range(10))
    def test_dummy(i, request):
        finalizers =
request._fixturemanager._arg2fixturedefs['app'][0]._finalizer
>       assert len(finalizers) == 1
E       assert 11 == 1
E        +  where 11 = len([<function
call_fixture_func.<locals>.teardown at 0x034C3198>, <bound method
FixtureDef.finish of <FixtureDef name='ap...n' baseid='tests' >>,
<bound method FixtureDef.finish of <FixtureDef name='app'
scope='session' baseid='tests' >>, ...])

tests\test_dummy.py:7: AssertionError
========================== 10 failed in 0.06 seconds ==========================

As can be seen here, the number of finalizers registered for the FixtureDef
"app" just grows as the number of tests grows. The same can be said of the
?next? app fixture in the chain (._arg2fixturedefs['app'][1]).

Can anybody with some knowledge on the fixture mechanism explain the above
behavior and if it was intentional?

Cheers,
Bruno.
?

On Mon, Aug 15, 2016 at 4:22 PM Florian Bruhin <me at the-compiler.org> wrote:

> Hey,
>
> * Bruno Oliveira <nicoddemus at gmail.com> [2016-08-15 01:15:14 +0000]:
> > I've worked on the weekend on the issue discovered by Florian on the
> > qutebrowser test suite, and unfortunately I think the current
> > implementation will have to be re-thought because it contains a serious
> > problem regarding finalizers when fixtures are being overwritten.
>
> Thanks for all the debugging and all the other great work you do to
> get 3.0 out! :)
>
> > Because redesigning it might take a awhile, I suggest we remove
> invocation
> > fixtures for now so we can make the 3.0 release. We can then work this
> week
> > on the remaining issues[1] and make a release candidate by the middle of
> > the week, aiming for the official release by the end of the week.
> >
> > How does that sound?
>
> I agree with the other Flori.* people :D
>
> I guess it's better to take them out and reintroduce them in 3.1 with
> the rough edges smoothened out than breaking stuff now.
>
> 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/20160816/17386e04/attachment-0001.html>

From nicoddemus at gmail.com  Tue Aug 16 20:52:37 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Wed, 17 Aug 2016 00:52:37 +0000
Subject: [pytest-dev] Release candidate soon(tm)?
Message-ID: <CA+RQFffY5o0Ku1X9jkLydAKFqt6QPEZ8MPrw53mYPqOBWKFO7w@mail.gmail.com>

Hi everyone!

There are now 4 open PRs which handle the last remaining issues for 3.0:

* WIP Change outcome to 'passed' for xfail unless it's strict:
https://github.com/pytest-dev/pytest/pull/1795
* Support [tool:pytest] in setup.cfg files:
https://github.com/pytest-dev/pytest/pull/1813
* Deprecate --resultlog cmdline option:
https://github.com/pytest-dev/pytest/pull/1812
* Revert invocation-fixtures code:
https://github.com/pytest-dev/pytest/pull/1811

So help reviewing/merging them is welcome!

As soon as those are merged, I would like to push a 3.0 release to my devpi
channel and ask people here on the mailing list to give it a try. If
nothing critical comes up, we can publish it on Thursday/Friday. I will
also try my best to be available during the weekend in case anything
critical pops up.

The "what's new on pytest 3.0" post is also ready, and I would like to
publish it as soon as the package is officially published on PyPI, if the
blog maintainers don't object. Help announcing the release and/or the
"whats new" post on twitter is welcome! :)

Any suggestions or comments?

Excited with the release! :)

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

From florian.schulze at gmx.net  Wed Aug 17 01:17:36 2016
From: florian.schulze at gmx.net (Florian Schulze)
Date: Wed, 17 Aug 2016 07:17:36 +0200
Subject: [pytest-dev] Release candidate soon(tm)?
In-Reply-To: <CA+RQFffY5o0Ku1X9jkLydAKFqt6QPEZ8MPrw53mYPqOBWKFO7w@mail.gmail.com>
References: <CA+RQFffY5o0Ku1X9jkLydAKFqt6QPEZ8MPrw53mYPqOBWKFO7w@mail.gmail.com>
Message-ID: <A1D7D299-560C-4934-BB46-492D2926CB39@gmx.net>

Is it possible to preview the blog post somewhere?

> On 17.08.2016, at 02:52, Bruno Oliveira <nicoddemus at gmail.com> wrote:
> 
> Hi everyone!
> 
> There are now 4 open PRs which handle the last remaining issues for 3.0:
> 
> * WIP Change outcome to 'passed' for xfail unless it's strict: https://github.com/pytest-dev/pytest/pull/1795
> * Support [tool:pytest] in setup.cfg files: https://github.com/pytest-dev/pytest/pull/1813
> * Deprecate --resultlog cmdline option: https://github.com/pytest-dev/pytest/pull/1812
> * Revert invocation-fixtures code: https://github.com/pytest-dev/pytest/pull/1811
> 
> So help reviewing/merging them is welcome!
> 
> As soon as those are merged, I would like to push a 3.0 release to my devpi channel and ask people here on the mailing list to give it a try. If nothing critical comes up, we can publish it on Thursday/Friday. I will also try my best to be available during the weekend in case anything critical pops up.
> 
> The "what's new on pytest 3.0" post is also ready, and I would like to publish it as soon as the package is officially published on PyPI, if the blog maintainers don't object. Help announcing the release and/or the "whats new" post on twitter is welcome! :)
> 
> Any suggestions or comments?
> 
> Excited with the release! :)
> 
> Cheers,
> Bruno.
> 
> _______________________________________________
> 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/20160817/8f8ea6c1/attachment.html>

From nicoddemus at gmail.com  Wed Aug 17 08:51:52 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Wed, 17 Aug 2016 12:51:52 +0000
Subject: [pytest-dev] Release candidate soon(tm)?
In-Reply-To: <A1D7D299-560C-4934-BB46-492D2926CB39@gmx.net>
References: <CA+RQFffY5o0Ku1X9jkLydAKFqt6QPEZ8MPrw53mYPqOBWKFO7w@mail.gmail.com>
 <A1D7D299-560C-4934-BB46-492D2926CB39@gmx.net>
Message-ID: <CA+RQFfcRfYA2tT-ctFSdd7D6S1xVD6VNst497TfjAmK5sTi0Kg@mail.gmail.com>

On Wed, Aug 17, 2016 at 2:17 AM Florian Schulze <florian.schulze at gmx.net>
wrote:

> Is it possible to preview the blog post somewhere?
>

I'm not sure, but you can clone it and preview it locally.

Cheers,
Bruno.


> On 17.08.2016, at 02:52, Bruno Oliveira <nicoddemus at gmail.com> wrote:
>
> Hi everyone!
>
> There are now 4 open PRs which handle the last remaining issues for 3.0:
>
> * WIP Change outcome to 'passed' for xfail unless it's strict:
> https://github.com/pytest-dev/pytest/pull/1795
> * Support [tool:pytest] in setup.cfg files:
> https://github.com/pytest-dev/pytest/pull/1813
> * Deprecate --resultlog cmdline option:
> https://github.com/pytest-dev/pytest/pull/1812
> * Revert invocation-fixtures code:
> https://github.com/pytest-dev/pytest/pull/1811
>
> So help reviewing/merging them is welcome!
>
> As soon as those are merged, I would like to push a 3.0 release to my
> devpi channel and ask people here on the mailing list to give it a try. If
> nothing critical comes up, we can publish it on Thursday/Friday. I will
> also try my best to be available during the weekend in case anything
> critical pops up.
>
> The "what's new on pytest 3.0" post is also ready, and I would like to
> publish it as soon as the package is officially published on PyPI, if the
> blog maintainers don't object. Help announcing the release and/or the
> "whats new" post on twitter is welcome! :)
>
> Any suggestions or comments?
>
> Excited with the release! :)
>
> Cheers,
> Bruno.
>
> _______________________________________________
> 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/20160817/ff1cb058/attachment.html>

From nicoddemus at gmail.com  Thu Aug 18 14:11:41 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 18 Aug 2016 18:11:41 +0000
Subject: [pytest-dev] pytest 3.0.0 pre-release
Message-ID: <CA+RQFfdunUB-cBmfUQrWXVCaBXDetk4uFnwAXe_F6gqDuyuoyQ@mail.gmail.com>

Hello everyone,

The pytest team has generated a 3.0.0 release candidate and would like to
ask users to test the new package with their test suites.

The package can be installed with:

    pip install -U -i https://devpi.net/nicoddemus/dev pytest

Please report any serious regression on the issue tracker:

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

We will push the release to PyPI in the next couple of days if nothing
critical is reported by then.

Thanks!

The pytest team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160818/543bf3b6/attachment.html>

From mail at florian-schulze.net  Thu Aug 18 14:15:07 2016
From: mail at florian-schulze.net (Florian Schulze)
Date: Thu, 18 Aug 2016 20:15:07 +0200
Subject: [pytest-dev] pytest 3.0.0 pre-release
In-Reply-To: <CA+RQFfdunUB-cBmfUQrWXVCaBXDetk4uFnwAXe_F6gqDuyuoyQ@mail.gmail.com>
References: <CA+RQFfdunUB-cBmfUQrWXVCaBXDetk4uFnwAXe_F6gqDuyuoyQ@mail.gmail.com>
Message-ID: <4E3417B7-0706-4668-BBC2-72A777E5D44E@florian-schulze.net>

For some reason I had to use this to get it installed:

   pip install -U -i https://devpi.net/nicoddemus/dev pytest==3.0.0

Regards,
Florian Schulze

On 18 Aug 2016, at 20:11, Bruno Oliveira wrote:

> Hello everyone,
>
> The pytest team has generated a 3.0.0 release candidate and would like to
> ask users to test the new package with their test suites.
>
> The package can be installed with:
>
>     pip install -U -i https://devpi.net/nicoddemus/dev pytest
>
> Please report any serious regression on the issue tracker:
>
> https://github.com/pytest-dev/pytest/issues
>
> We will push the release to PyPI in the next couple of days if nothing
> critical is reported by then.
>
> Thanks!
>
> The pytest team
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev

From me at the-compiler.org  Thu Aug 18 14:40:19 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Thu, 18 Aug 2016 20:40:19 +0200
Subject: [pytest-dev] [TIP] pytest 3.0.0 pre-release
In-Reply-To: <CA+RQFfdunUB-cBmfUQrWXVCaBXDetk4uFnwAXe_F6gqDuyuoyQ@mail.gmail.com>
References: <CA+RQFfdunUB-cBmfUQrWXVCaBXDetk4uFnwAXe_F6gqDuyuoyQ@mail.gmail.com>
Message-ID: <20160818184019.srukr2qzg7f7nzph@tonks>

Hey,

* Bruno Oliveira <nicoddemus at gmail.com> [2016-08-18 18:11:41 +0000]:
> The pytest team has generated a 3.0.0 release candidate and would like to
> ask users to test the new package with their test suites.

Thanks Bruno!

The good news: It works fine for me!

The bad news: Minus the BDD tests of course... so I'll not be able to
upgrade to 3.0 until someone helps me fix[1] pytest-bdd (as I really
don't know enough about fixture internals and pytest-bdd) or I get to
writing my own BDD plugin without such a deep (and therefore hackish)
fixture integration :(

[1] https://github.com/pytest-dev/pytest-bdd/pull/193

Florian

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

From mail at florian-schulze.net  Thu Aug 18 15:43:53 2016
From: mail at florian-schulze.net (Florian Schulze)
Date: Thu, 18 Aug 2016 21:43:53 +0200
Subject: [pytest-dev] pytest 3.0.0 pre-release
In-Reply-To: <CA+RQFfdunUB-cBmfUQrWXVCaBXDetk4uFnwAXe_F6gqDuyuoyQ@mail.gmail.com>
References: <CA+RQFfdunUB-cBmfUQrWXVCaBXDetk4uFnwAXe_F6gqDuyuoyQ@mail.gmail.com>
Message-ID: <E47F3818-330D-4244-873B-B058E3471364@florian-schulze.net>

Besides one issue in devpi-server where we use monkeypatch in a non 
regular way (which Holger already warned me about) pytest 3.0.0 works 
fine with devpi tests!

None of my other stuff is anywhere near the complexity of devpi. So from 
my side pytest 3.0.0 looks good.

Regards,
Florian Schulze


On 18 Aug 2016, at 20:11, Bruno Oliveira wrote:

> Hello everyone,
>
> The pytest team has generated a 3.0.0 release candidate and would like 
> to
> ask users to test the new package with their test suites.
>
> The package can be installed with:
>
>     pip install -U -i https://devpi.net/nicoddemus/dev pytest
>
> Please report any serious regression on the issue tracker:
>
> https://github.com/pytest-dev/pytest/issues
>
> We will push the release to PyPI in the next couple of days if nothing
> critical is reported by then.
>
> Thanks!
>
> The pytest team
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev

From rpfannsc at redhat.com  Thu Aug 18 15:46:02 2016
From: rpfannsc at redhat.com (Ronny Pfannschmidt)
Date: Thu, 18 Aug 2016 21:46:02 +0200
Subject: [pytest-dev] [TIP] pytest 3.0.0 pre-release
In-Reply-To: <20160818184019.srukr2qzg7f7nzph@tonks>
References: <CA+RQFfdunUB-cBmfUQrWXVCaBXDetk4uFnwAXe_F6gqDuyuoyQ@mail.gmail.com>
 <20160818184019.srukr2qzg7f7nzph@tonks>
Message-ID: <CAA10jzP6djSZk5Bvfz0crLR5NaFCUvK_NT1uHYf54SnKik0PbA@mail.gmail.com>

for good measure i also scheduled a full run at a work project that does
its fair share of tricky things

2016-08-18 20:40 GMT+02:00 Florian Bruhin <me at the-compiler.org>:

> Hey,
>
> * Bruno Oliveira <nicoddemus at gmail.com> [2016-08-18 18:11:41 +0000]:
> > The pytest team has generated a 3.0.0 release candidate and would like to
> > ask users to test the new package with their test suites.
>
> Thanks Bruno!
>
> The good news: It works fine for me!
>
> The bad news: Minus the BDD tests of course... so I'll not be able to
> upgrade to 3.0 until someone helps me fix[1] pytest-bdd (as I really
> don't know enough about fixture internals and pytest-bdd) or I get to
> writing my own BDD plugin without such a deep (and therefore hackish)
> fixture integration :(
>
> [1] https://github.com/pytest-dev/pytest-bdd/pull/193
>
> 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
>
>


-- 

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/20160818/a8bb7b6c/attachment.html>

From genml+pytest-dev at thequod.de  Thu Aug 18 16:41:27 2016
From: genml+pytest-dev at thequod.de (Daniel Hahler)
Date: Thu, 18 Aug 2016 22:41:27 +0200
Subject: [pytest-dev] pytest 3.0.0 pre-release
In-Reply-To: <CA+RQFfdunUB-cBmfUQrWXVCaBXDetk4uFnwAXe_F6gqDuyuoyQ@mail.gmail.com>
References: <CA+RQFfdunUB-cBmfUQrWXVCaBXDetk4uFnwAXe_F6gqDuyuoyQ@mail.gmail.com>
Message-ID: <3c9bdb8e-ac0f-eb4a-def9-6e8ea6e3d0e2@thequod.de>

On 18.08.2016 20:11, Bruno Oliveira wrote:

> The pytest team has generated a 3.0.0 release candidate and would like to ask users to test the new package with their test suites. 
> 
> The package can be installed with:
> 
>     pip install -U -i https://devpi.net/nicoddemus/dev pytest

Worked flawlessly with our tests at work!
This was using pytest-django from git's master branch already, but
pytest-django's tests also worked (only tested with PyPy3).


Cheers,
Daniel.

From raphael at hackebrot.de  Thu Aug 18 16:54:22 2016
From: raphael at hackebrot.de (Raphael Pierzina)
Date: Thu, 18 Aug 2016 21:54:22 +0100
Subject: [pytest-dev] pytest 3.0.0 pre-release
In-Reply-To: <CA+RQFfdunUB-cBmfUQrWXVCaBXDetk4uFnwAXe_F6gqDuyuoyQ@mail.gmail.com>
References: <CA+RQFfdunUB-cBmfUQrWXVCaBXDetk4uFnwAXe_F6gqDuyuoyQ@mail.gmail.com>
Message-ID: <5601D3DD-2C2C-41F5-974E-EC87482E01C9@hackebrot.de>

Looking good for cookiecutter! :)
https://github.com/audreyr/cookiecutter/pull/796/files <https://github.com/audreyr/cookiecutter/pull/796/files>

> On 18 Aug 2016, at 19:11, Bruno Oliveira <nicoddemus at gmail.com> wrote:
> 
>   pip install -U -i https://devpi.net/nicoddemus/dev <https://devpi.net/nicoddemus/dev> pytest

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

From nicoddemus at gmail.com  Thu Aug 18 17:55:11 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 18 Aug 2016 21:55:11 +0000
Subject: [pytest-dev] pytest 3.0.0 pre-release
In-Reply-To: <5601D3DD-2C2C-41F5-974E-EC87482E01C9@hackebrot.de>
References: <CA+RQFfdunUB-cBmfUQrWXVCaBXDetk4uFnwAXe_F6gqDuyuoyQ@mail.gmail.com>
 <5601D3DD-2C2C-41F5-974E-EC87482E01C9@hackebrot.de>
Message-ID: <CA+RQFffCy8sTbXGWfg0o2iXNnsdWvdmr=L=T6=pmQbBpSjDUOg@mail.gmail.com>

Thanks everyone for testing!

If you could, please re-tweet[1] to help this reach more people! :)

[1] https://twitter.com/nicoddemus/status/766336953751072768

Cheers,


On Thu, Aug 18, 2016 at 5:54 PM Raphael Pierzina <raphael at hackebrot.de>
wrote:

> Looking good for cookiecutter! :)
> https://github.com/audreyr/cookiecutter/pull/796/files
>
> On 18 Aug 2016, at 19:11, Bruno Oliveira <nicoddemus at gmail.com> wrote:
>
>   pip install -U -i https://devpi.net/nicoddemus/dev pytest
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160818/b2c50822/attachment.html>

From isaulv at gmail.com  Thu Aug 18 17:56:20 2016
From: isaulv at gmail.com (Isaul Vargas)
Date: Thu, 18 Aug 2016 17:56:20 -0400
Subject: [pytest-dev] [TIP] pytest 3.0.0 pre-release
In-Reply-To: <CAA10jzP6djSZk5Bvfz0crLR5NaFCUvK_NT1uHYf54SnKik0PbA@mail.gmail.com>
References: <CA+RQFfdunUB-cBmfUQrWXVCaBXDetk4uFnwAXe_F6gqDuyuoyQ@mail.gmail.com>
 <20160818184019.srukr2qzg7f7nzph@tonks>
 <CAA10jzP6djSZk5Bvfz0crLR5NaFCUvK_NT1uHYf54SnKik0PbA@mail.gmail.com>
Message-ID: <CAFB36JExr_JYixHsygaWzn8-fOV1EPx_0-wWUREKmMPh0OSJQQ@mail.gmail.com>

Worked for me. It even showed that I had used @pytest.skip incorrectly in a
test I wanted to skip.
Tested with pytest-xdist 1.15, flaky 3.1.1.
The maxfail issue seems to be fixed but I'll have to test on Jenkins.
Pretty nice update.

On Thu, Aug 18, 2016 at 3:46 PM, Ronny Pfannschmidt <rpfannsc at redhat.com>
wrote:

> for good measure i also scheduled a full run at a work project that does
> its fair share of tricky things
>
> 2016-08-18 20:40 GMT+02:00 Florian Bruhin <me at the-compiler.org>:
>
>> Hey,
>>
>> * Bruno Oliveira <nicoddemus at gmail.com> [2016-08-18 18:11:41 +0000]:
>> > The pytest team has generated a 3.0.0 release candidate and would like
>> to
>> > ask users to test the new package with their test suites.
>>
>> Thanks Bruno!
>>
>> The good news: It works fine for me!
>>
>> The bad news: Minus the BDD tests of course... so I'll not be able to
>> upgrade to 3.0 until someone helps me fix[1] pytest-bdd (as I really
>> don't know enough about fixture internals and pytest-bdd) or I get to
>> writing my own BDD plugin without such a deep (and therefore hackish)
>> fixture integration :(
>>
>> [1] https://github.com/pytest-dev/pytest-bdd/pull/193
>>
>> 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
>>
>>
>
>
> --
>
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160818/f635d560/attachment.html>

From raphael at hackebrot.de  Thu Aug 18 17:58:30 2016
From: raphael at hackebrot.de (Raphael Pierzina)
Date: Thu, 18 Aug 2016 22:58:30 +0100
Subject: [pytest-dev] pytest 3.0.0 pre-release
In-Reply-To: <CA+RQFffCy8sTbXGWfg0o2iXNnsdWvdmr=L=T6=pmQbBpSjDUOg@mail.gmail.com>
References: <CA+RQFfdunUB-cBmfUQrWXVCaBXDetk4uFnwAXe_F6gqDuyuoyQ@mail.gmail.com>
 <5601D3DD-2C2C-41F5-974E-EC87482E01C9@hackebrot.de>
 <CA+RQFffCy8sTbXGWfg0o2iXNnsdWvdmr=L=T6=pmQbBpSjDUOg@mail.gmail.com>
Message-ID: <20DA8F4D-F74B-4DFF-8864-AF64BFD76A65@hackebrot.de>

Done! :)

Both with my personal account as well as our pytestdotorg twitter account.

> On 18 Aug 2016, at 22:55, Bruno Oliveira <nicoddemus at gmail.com> wrote:
> 
> Thanks everyone for testing!
> 
> If you could, please re-tweet[1] to help this reach more people! :)
> 
> [1] https://twitter.com/nicoddemus/status/766336953751072768 <https://twitter.com/nicoddemus/status/766336953751072768>
> 
> Cheers,
> 
> 
> On Thu, Aug 18, 2016 at 5:54 PM Raphael Pierzina <raphael at hackebrot.de <mailto:raphael at hackebrot.de>> wrote:
> Looking good for cookiecutter! :)
> https://github.com/audreyr/cookiecutter/pull/796/files <https://github.com/audreyr/cookiecutter/pull/796/files>
> 
>> On 18 Aug 2016, at 19:11, Bruno Oliveira <nicoddemus at gmail.com <mailto:nicoddemus at gmail.com>> wrote:
>> 
>>   pip install -U -i https://devpi.net/nicoddemus/dev <https://devpi.net/nicoddemus/dev> pytest
> 

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

From me at the-compiler.org  Fri Aug 19 11:13:03 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Fri, 19 Aug 2016 17:13:03 +0200
Subject: [pytest-dev] [TIP] pytest 3.0.0 pre-release
In-Reply-To: <20160818184019.srukr2qzg7f7nzph@tonks>
References: <CA+RQFfdunUB-cBmfUQrWXVCaBXDetk4uFnwAXe_F6gqDuyuoyQ@mail.gmail.com>
 <20160818184019.srukr2qzg7f7nzph@tonks>
Message-ID: <20160819151303.d7oa5v2qaoi5wmbk@tonks>

* Florian Bruhin <me at the-compiler.org> [2016-08-18 20:40:19 +0200]:
> Hey,
> 
> * Bruno Oliveira <nicoddemus at gmail.com> [2016-08-18 18:11:41 +0000]:
> > The pytest team has generated a 3.0.0 release candidate and would like to
> > ask users to test the new package with their test suites.
> 
> Thanks Bruno!
> 
> The good news: It works fine for me!
> 
> The bad news: Minus the BDD tests of course... so I'll not be able to
> upgrade to 3.0 until someone helps me fix[1] pytest-bdd (as I really
> don't know enough about fixture internals and pytest-bdd) or I get to
> writing my own BDD plugin without such a deep (and therefore hackish)
> fixture integration :(
> 
> [1] https://github.com/pytest-dev/pytest-bdd/pull/193

Thanks to Bruno pytest-bdd is now fixed (at least in my PR):
https://github.com/pytest-dev/pytest-bdd/pull/193#issuecomment-240868947

And I made myself a 3.0 checklist for qutebrowser ;)
https://github.com/The-Compiler/qutebrowser/issues/1877

Can't wait! \o/

Florian

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

From nicoddemus at gmail.com  Fri Aug 19 17:25:11 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Fri, 19 Aug 2016 21:25:11 +0000
Subject: [pytest-dev] pytest 3.0.0 released!
Message-ID: <CA+RQFffASN_tvMf2QrnLFuYqdOOzV59qaWmA5f_56KyPvnM7RQ@mail.gmail.com>

Hello everyone,

The pytest team is proud to announce the 3.0.0 release!

pytest is a mature Python testing tool with more than a 1600 tests
against itself, passing on many different interpreters and platforms.

This release contains a lot of bugs and improvements, and much of
the work done on it was possible because of the 2016 Sprint[1], which
was funded by an indiegogo campaign which raised over US$12,000 with
nearly 100 backers.

There's a "What's new in pytest 3.0" [2] blog post highlighting the
major features in this release.

To see the complete changelog and documentation, please visit:

    http://docs.pytest.org

As usual, you can upgrade from pypi via:

    pip install -U pytest

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

    AbdealiJK
    Ana Ribeiro
    Antony Lee
    Brandon W Maister
    Brianna Laugher
    Bruno Oliveira
    Ceridwen
    Christian Boelsen
    Daniel Hahler
    Danielle Jenkins
    Dave Hunt
    Diego Russo
    Dmitry Dygalo
    Edoardo Batini
    Eli Boyarski
    Florian Bruhin
    Floris Bruynooghe
    Greg Price
    Guyzmo
    HEAD KANGAROO
    JJ
    Javi Romero
    Javier Domingo Cansino
    Kale Kundert
    Kalle Bronsen
    Marius Gedminas
    Matt Williams
    Mike Lundy
    Oliver Bestwalter
    Omar Kohl
    Raphael Pierzina
    RedBeardCode
    Roberto Polli
    Romain Dorgueil
    Roman Bolshakov
    Ronny Pfannschmidt
    Stefan Zimmermann
    Steffen Allner
    Tareq Alayan
    Ted Xiao
    Thomas Grainger
    Tom Viner
    TomV
    Vasily Kuznetsov
    aostr
    marscher
    palaviv
    satoru
    taschini


Happy testing,
The py.test Development Team

[1] http://blog.pytest.org/2016/pytest-development-sprint/
[2] http://blog.pytest.org/2016/whats-new-in-pytest-30/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160819/6400d778/attachment.html>

From nicoddemus at gmail.com  Fri Aug 19 17:57:35 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Fri, 19 Aug 2016 21:57:35 +0000
Subject: [pytest-dev] pytest 3.0.0 released!
In-Reply-To: <CA+RQFffASN_tvMf2QrnLFuYqdOOzV59qaWmA5f_56KyPvnM7RQ@mail.gmail.com>
References: <CA+RQFffASN_tvMf2QrnLFuYqdOOzV59qaWmA5f_56KyPvnM7RQ@mail.gmail.com>
Message-ID: <CA+RQFfeN_wwEgMjveMxQckgSZDPSFOdPhie_BaWqnZFVwZgE7w@mail.gmail.com>

On Fri, Aug 19, 2016 at 6:24 PM Bruno Oliveira <nicoddemus at gmail.com> wrote:

> This release contains a lot of bugs and improvements, and ...
>

Of course I meant "lot of bug *fixes*", sorry for the typo. :)

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

From oliver at bestwalter.de  Sat Aug 20 05:20:34 2016
From: oliver at bestwalter.de (Oliver Bestwalter)
Date: Sat, 20 Aug 2016 09:20:34 +0000
Subject: [pytest-dev] pytest 3.0.0 released!
In-Reply-To: <CA+RQFfeN_wwEgMjveMxQckgSZDPSFOdPhie_BaWqnZFVwZgE7w@mail.gmail.com>
References: <CA+RQFffASN_tvMf2QrnLFuYqdOOzV59qaWmA5f_56KyPvnM7RQ@mail.gmail.com>
 <CA+RQFfeN_wwEgMjveMxQckgSZDPSFOdPhie_BaWqnZFVwZgE7w@mail.gmail.com>
Message-ID: <CAG5CgtriwNwOV3TzE94zV_X=1JeqnF7ZvTVi7r5JsooiRjG9uw@mail.gmail.com>

Hi Bruno,

wow, you're fast! Great! I wanted to do some testing over the weekend with
the release candidate. Will do it with 3.0 now instead :)

What I can already say is that I checked the feature branch against my main
projects since the sprint and didn't have any problems.

Cheers
Oliver


On Fri, 19 Aug 2016 at 23:58 Bruno Oliveira <nicoddemus at gmail.com> wrote:

>
>
> On Fri, Aug 19, 2016 at 6:24 PM Bruno Oliveira <nicoddemus at gmail.com>
> wrote:
>
>> This release contains a lot of bugs and improvements, and ...
>>
>
> Of course I meant "lot of bug *fixes*", sorry for the typo. :)
>
> Cheers,
> Bruno.
> _______________________________________________
> 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/20160820/63fe9b74/attachment.html>

From oliver at bestwalter.de  Sat Aug 20 16:39:27 2016
From: oliver at bestwalter.de (Oliver Bestwalter)
Date: Sat, 20 Aug 2016 20:39:27 +0000
Subject: [pytest-dev] pytest 3.0.0 released!
In-Reply-To: <CAG5CgtriwNwOV3TzE94zV_X=1JeqnF7ZvTVi7r5JsooiRjG9uw@mail.gmail.com>
References: <CA+RQFffASN_tvMf2QrnLFuYqdOOzV59qaWmA5f_56KyPvnM7RQ@mail.gmail.com>
 <CA+RQFfeN_wwEgMjveMxQckgSZDPSFOdPhie_BaWqnZFVwZgE7w@mail.gmail.com>
 <CAG5CgtriwNwOV3TzE94zV_X=1JeqnF7ZvTVi7r5JsooiRjG9uw@mail.gmail.com>
Message-ID: <CAG5CgtrhD_3WJmvzjTKsAky=LB+CX-YV0Hho0WYob81=McFepQ@mail.gmail.com>

Hi,

I played with the release today and found no major problems.

The deprecation warnings could be more helpful, but I guess that will be
solved as a side effect of fixing
https://github.com/pytest-dev/pytest/issues/1804

A "None" sneaks into the output where a warning number should be if you
pass a string to pytest.main instead of a list. Needs some polishing, I
will hope to get into the next bugfix release.

import pytest; pytest.main('-v')

results in: WC1 None passing a string to pytest.main() is deprecated, pass
a list of arguments instead.
                ^^^^

I updated the checklist to reflect the current status as that is the first
hit, if somebody is searchin for pytest 3.0 atm.

https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist

Cheers
Oliver


On Sat, 20 Aug 2016 at 11:20 Oliver Bestwalter <oliver at bestwalter.de> wrote:

> Hi Bruno,
>
> wow, you're fast! Great! I wanted to do some testing over the weekend with
> the release candidate. Will do it with 3.0 now instead :)
>
> What I can already say is that I checked the feature branch against my
> main projects since the sprint and didn't have any problems.
>
> Cheers
> Oliver
>
>
> On Fri, 19 Aug 2016 at 23:58 Bruno Oliveira <nicoddemus at gmail.com> wrote:
>
>>
>>
>> On Fri, Aug 19, 2016 at 6:24 PM Bruno Oliveira <nicoddemus at gmail.com>
>> wrote:
>>
>>> This release contains a lot of bugs and improvements, and ...
>>>
>>
>> Of course I meant "lot of bug *fixes*", sorry for the typo. :)
>>
>> Cheers,
>> Bruno.
>> _______________________________________________
>> 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/20160820/a09aa709/attachment.html>

From kentaro0919 at gmail.com  Sun Aug 21 17:33:35 2016
From: kentaro0919 at gmail.com (Kentaro Hori)
Date: Mon, 22 Aug 2016 06:33:35 +0900
Subject: [pytest-dev] Documentation translations
Message-ID: <CAPLHawcC3+Tcz9QeZO81SR0VZCOshJ8dh8-6aOxryo5QW3iEcw@mail.gmail.com>

Congratulations on 3.0 release.

I was reading the
Contribution getting started
<http://docs.pytest.org/en/latest/contributing.html#id2>

It mention "Documentation translations." but there is no link for more
information.

Is there any action on it?


I'd like to translate to Japanese.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160822/a8a8f485/attachment.html>

From rpfannsc at redhat.com  Mon Aug 22 03:26:46 2016
From: rpfannsc at redhat.com (Ronny Pfannschmidt)
Date: Mon, 22 Aug 2016 09:26:46 +0200
Subject: [pytest-dev] Documentation translations
In-Reply-To: <CAPLHawcC3+Tcz9QeZO81SR0VZCOshJ8dh8-6aOxryo5QW3iEcw@mail.gmail.com>
References: <CAPLHawcC3+Tcz9QeZO81SR0VZCOshJ8dh8-6aOxryo5QW3iEcw@mail.gmail.com>
Message-ID: <CAA10jzNE9cV4asiPdvDKhUzT_0r_Fn_OSfh7KRtkDORvBZv1Xg@mail.gmail.com>

Hi Kentaro (i hope i'm addressing you correct there)

a while back we had a traditional translation attempt to translate the
documentation (also to Japanese)
using a copy of the text files

however that turned out impossible to keep in sync nicely

for the next attempt there is probably need for some gettext based
infrastructure (so we can track the translations and doc changes in a
manageable way)
sphinx also has some gettext based tooling to work in turn

however the whole infrastructure needs a basic setup for keeping in sync
and managing translations nicely
as far as i know nobody of the core team managed to get into that topic,
so there indeed is no documentation/detail write-ups

it is important to get some kind of automation in that area so we can
actively track how good the translations are

if you are very motivated, you can try to set it up and i can also
volunteer some time to help the infrastructure setup
i believe the main reason nobody did set it up is, that we currently don't
have any active translators at all

-- Ronny



2016-08-21 23:33 GMT+02:00 Kentaro Hori <kentaro0919 at gmail.com>:

> Congratulations on 3.0 release.
>
> I was reading the
> Contribution getting started
> <http://docs.pytest.org/en/latest/contributing.html#id2>
>
> It mention "Documentation translations." but there is no link for more
> information.
>
> Is there any action on it?
>
>
> I'd like to translate to Japanese.
>
> _______________________________________________
> 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/20160822/ca73f024/attachment.html>

From sivan at vitakka.co  Mon Aug 22 07:40:42 2016
From: sivan at vitakka.co (Sivan Greenberg)
Date: Mon, 22 Aug 2016 14:40:42 +0300
Subject: [pytest-dev] pytest and Mozilla's Open Source Support program
In-Reply-To: <CAMB+yF0RguavGLKViaKroHyHm1rPs2LFdyR517KS9ci9g1P-Ww@mail.gmail.com>
References: <20160808101302.zc4c425i53hwtoml@tonks>
 <CA+RQFfcyQQsJO1aCP-=Y6r+QN-jVxxbdVj4ajBOrjUitqzHAUg@mail.gmail.com>
 <449D65F4-2061-4E16-81B2-57AC6A6CED84@florian-schulze.net>
 <CAMB+yF0RguavGLKViaKroHyHm1rPs2LFdyR517KS9ci9g1P-Ww@mail.gmail.com>
Message-ID: <CAMB+yF1p23ER_VKLZS-O0z=Ntk2nwBCu-RxJRNyjm1WjGj5Jcw@mail.gmail.com>

Hi list,

 I did not see any responses to my last note - I guess everybody are on
vacation? Any new input on that?


 With regards to prospective freelancers to do work, so far we have me and
Florian Schulze. Anybody else interested as well?

 I've mentioned before also that I'd like us to start an internship
initiative, so we can list in GSoC and similar new-comers to coding
communities to expedite the development effort. I'll mail the list
separately.

Thanks,

-Sivan

On Tue, Aug 9, 2016 at 12:35 PM, Sivan Greenberg <sivan at vitakka.co> wrote:

> Hi again,
>
>  I am happy to volunteer for that - I will sure need to ask people here
> for data that I cannot find myself. I have had experience working with US
> based Linux foundation ,GSoC and the Freescale  organizations, I think this
> should not be too much different and not a huge task.
>
>  If anybody here is happy with me attempting at that, I'll set to do it. I
> will also be highly keen on doing even part of the development, so doing
> community and coding is much fun :)
>
> -Sivan
>
> On Mon, Aug 8, 2016 at 4:57 PM, Florian Schulze <mail at florian-schulze.net>
> wrote:
>
>> Hi!
>>
>> I know Holger is on vacation for a while. I doubt he got time to handle
>> this in August.
>>
>> I would be available for development work. I got no experience with
>> organizational and legal stuff in regard to US based foundations when
>> living in Germany.
>>
>> Regards,
>> Florian Schulze
>>
>>
>> On 8 Aug 2016, at 15:37, Bruno Oliveira wrote:
>>
>> On Mon, Aug 8, 2016 at 7:13 AM Florian Bruhin <me at the-compiler.org>
>>> wrote:
>>>
>>> Hey,
>>>>
>>>> via [1] (German) I just stumbled upon Mozilla's MOSS program[2].
>>>>
>>>> They have a track[3] where they found generic OSS projects furthering
>>>> their mission, and another one[4] (probably more relevant to us) where
>>>> they fund projects they use themselves. From what I've seen via
>>>> Dave Hunt, Mozilla is quite a heavy pytest user with various plugins
>>>> they wrote.
>>>>
>>>> The grants are between $10k and $250k. If time permits, this could
>>>> e.g. be used by Merlinux (i.e., Holger's company) to allow someone to
>>>> work on pytest (or possibly, tox/devpi - not sure if those are used at
>>>> Mozilla too?) full-time for a while.
>>>>
>>>>
>>> That sounds great, but first we would need to find someone willing to do
>>> the work. Does anybody on the mailing list volunteers? I can't volunteer
>>> myself as I already have a full time job.
>>>
>>> Cheers,
>>> Bruno
>>> _______________________________________________
>>> 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
>>
>
>
>
> --
> Sivan Greenberg
> Co founder & CTO
> Vitakka Consulting
>



-- 
Sivan Greenberg
Co founder & CTO
Vitakka Consulting
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160822/60ff9c71/attachment.html>

From nicoddemus at gmail.com  Mon Aug 22 11:13:02 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Mon, 22 Aug 2016 15:13:02 +0000
Subject: [pytest-dev] pytest and Mozilla's Open Source Support program
In-Reply-To: <CAMB+yF1p23ER_VKLZS-O0z=Ntk2nwBCu-RxJRNyjm1WjGj5Jcw@mail.gmail.com>
References: <20160808101302.zc4c425i53hwtoml@tonks>
 <CA+RQFfcyQQsJO1aCP-=Y6r+QN-jVxxbdVj4ajBOrjUitqzHAUg@mail.gmail.com>
 <449D65F4-2061-4E16-81B2-57AC6A6CED84@florian-schulze.net>
 <CAMB+yF0RguavGLKViaKroHyHm1rPs2LFdyR517KS9ci9g1P-Ww@mail.gmail.com>
 <CAMB+yF1p23ER_VKLZS-O0z=Ntk2nwBCu-RxJRNyjm1WjGj5Jcw@mail.gmail.com>
Message-ID: <CA+RQFfe-Nmtt0m_cgoKM0raYFfomKzVo4d8Z2iChGowYLqkzUw@mail.gmail.com>

On Mon, Aug 22, 2016 at 8:40 AM Sivan Greenberg <sivan at vitakka.co> wrote:

> Hi list,
>
>  I did not see any responses to my last note - I guess everybody are on
> vacation? Any new input on that?
>

Hi Sivan,

I guess we are waiting for Holger's input on this, and he is (was?) on
vacation.

Cheers,
Bruno

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

From flub at devork.be  Mon Aug 22 18:09:42 2016
From: flub at devork.be (Floris Bruynooghe)
Date: Mon, 22 Aug 2016 23:09:42 +0100
Subject: [pytest-dev] pytest and Mozilla's Open Source Support program
In-Reply-To: <CAMB+yF1p23ER_VKLZS-O0z=Ntk2nwBCu-RxJRNyjm1WjGj5Jcw@mail.gmail.com>
References: <20160808101302.zc4c425i53hwtoml@tonks>
 <CA+RQFfcyQQsJO1aCP-=Y6r+QN-jVxxbdVj4ajBOrjUitqzHAUg@mail.gmail.com>
 <449D65F4-2061-4E16-81B2-57AC6A6CED84@florian-schulze.net>
 <CAMB+yF0RguavGLKViaKroHyHm1rPs2LFdyR517KS9ci9g1P-Ww@mail.gmail.com>
 <CAMB+yF1p23ER_VKLZS-O0z=Ntk2nwBCu-RxJRNyjm1WjGj5Jcw@mail.gmail.com>
Message-ID: <CAAWk_DwsQEuJuzAtoP+LRmBWCztX0TvHZAiRVMWxjQvTkxW1gQ@mail.gmail.com>

Hi Sivan,

I've had a quick look at this as well and Mozilla's guidance says you
need to submit a particular project rather then general maintenance.
There probably are a bunch of smaller things which could make up a
proposal but I'm struggling of coming up with a few large projects to
list right away.  Did you have anything particular in mind which would
benefit from a focussed effort?  What are the exact deadlines for this
application round?  Also I gather they have several application rounds
so I don't think we have to rush and can happily prepare a possible
application with plenty of time?

And yes, when GSoC comes around it would be really nice if we could
join.  I guess the trick is again finding someone who can dedicate
enough time and knowledge of pytest over the whole summer to mentor.
But a reminder when applications are due would certainly be good, we
should probably do the effort for this (I might even volunteer for
mentoring).

Regards,
Floris

On 22 August 2016 at 12:40, Sivan Greenberg <sivan at vitakka.co> wrote:
> Hi list,
>
>  I did not see any responses to my last note - I guess everybody are on
> vacation? Any new input on that?
>
>
>  With regards to prospective freelancers to do work, so far we have me and
> Florian Schulze. Anybody else interested as well?
>
>  I've mentioned before also that I'd like us to start an internship
> initiative, so we can list in GSoC and similar new-comers to coding
> communities to expedite the development effort. I'll mail the list
> separately.
>
> Thanks,
>
> -Sivan
>
> On Tue, Aug 9, 2016 at 12:35 PM, Sivan Greenberg <sivan at vitakka.co> wrote:
>>
>> Hi again,
>>
>>  I am happy to volunteer for that - I will sure need to ask people here
>> for data that I cannot find myself. I have had experience working with US
>> based Linux foundation ,GSoC and the Freescale  organizations, I think this
>> should not be too much different and not a huge task.
>>
>>  If anybody here is happy with me attempting at that, I'll set to do it. I
>> will also be highly keen on doing even part of the development, so doing
>> community and coding is much fun :)
>>
>> -Sivan
>>
>> On Mon, Aug 8, 2016 at 4:57 PM, Florian Schulze <mail at florian-schulze.net>
>> wrote:
>>>
>>> Hi!
>>>
>>> I know Holger is on vacation for a while. I doubt he got time to handle
>>> this in August.
>>>
>>> I would be available for development work. I got no experience with
>>> organizational and legal stuff in regard to US based foundations when living
>>> in Germany.
>>>
>>> Regards,
>>> Florian Schulze
>>>
>>>
>>> On 8 Aug 2016, at 15:37, Bruno Oliveira wrote:
>>>
>>>> On Mon, Aug 8, 2016 at 7:13 AM Florian Bruhin <me at the-compiler.org>
>>>> wrote:
>>>>
>>>>> Hey,
>>>>>
>>>>> via [1] (German) I just stumbled upon Mozilla's MOSS program[2].
>>>>>
>>>>> They have a track[3] where they found generic OSS projects furthering
>>>>> their mission, and another one[4] (probably more relevant to us) where
>>>>> they fund projects they use themselves. From what I've seen via
>>>>> Dave Hunt, Mozilla is quite a heavy pytest user with various plugins
>>>>> they wrote.
>>>>>
>>>>> The grants are between $10k and $250k. If time permits, this could
>>>>> e.g. be used by Merlinux (i.e., Holger's company) to allow someone to
>>>>> work on pytest (or possibly, tox/devpi - not sure if those are used at
>>>>> Mozilla too?) full-time for a while.
>>>>>
>>>>
>>>> That sounds great, but first we would need to find someone willing to do
>>>> the work. Does anybody on the mailing list volunteers? I can't volunteer
>>>> myself as I already have a full time job.
>>>>
>>>> Cheers,
>>>> Bruno
>>>> _______________________________________________
>>>> 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
>>
>>
>>
>>
>> --
>> Sivan Greenberg
>> Co founder & CTO
>> Vitakka Consulting
>
>
>
>
> --
> Sivan Greenberg
> Co founder & CTO
> Vitakka Consulting
>
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>

From thomas at thomas-lotze.de  Mon Aug 22 18:35:29 2016
From: thomas at thomas-lotze.de (Thomas Lotze)
Date: Tue, 23 Aug 2016 00:35:29 +0200
Subject: [pytest-dev] pytest and Mozilla's Open Source Support program
In-Reply-To: <449D65F4-2061-4E16-81B2-57AC6A6CED84@florian-schulze.net>
References: <20160808101302.zc4c425i53hwtoml@tonks>
 <CA+RQFfcyQQsJO1aCP-=Y6r+QN-jVxxbdVj4ajBOrjUitqzHAUg@mail.gmail.com>
 <449D65F4-2061-4E16-81B2-57AC6A6CED84@florian-schulze.net>
Message-ID: <20160823003529.0e9d63ac@alpha>

"Florian Schulze" <mail at florian-schulze.net> wrote:

> I would be available for development work. I got no experience with 
> organizational and legal stuff in regard to US based foundations when 
> living in Germany.

Just a quick "same here". I'll be available for working on a funded project
soon (probably starting at the beginning of October), and of course I'm
willing to help with the proposal as long as the legal stuff is seen to by
someone who knows what they are doing...

Regards,
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/20160823/f50d27e2/attachment.sig>

From nicoddemus at gmail.com  Tue Aug 23 12:12:03 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Tue, 23 Aug 2016 16:12:03 +0000
Subject: [pytest-dev] 3.0.1 tonight?
Message-ID: <CA+RQFfe7-2rUc7eFP2OAQzL2JJROHnb4yUXHPs90QTECqs90+w@mail.gmail.com>

Hi everyone,

Since 3.0.0 was released, two regressions have been reported and this
afternoon the fix for the last one was merged.

Unless someone still has some issue that they would like to work on for
this release, I was thinking of making a 3.0.1 release tonight. What you
guys think? Should we wait a few more days to see if other regressions show
up, or the two we found so far are enough to warrant a release?

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

From mail at florian-schulze.net  Tue Aug 23 15:45:35 2016
From: mail at florian-schulze.net (Florian Schulze)
Date: Tue, 23 Aug 2016 21:45:35 +0200
Subject: [pytest-dev] 3.0.1 tonight?
In-Reply-To: <CA+RQFfe7-2rUc7eFP2OAQzL2JJROHnb4yUXHPs90QTECqs90+w@mail.gmail.com>
References: <CA+RQFfe7-2rUc7eFP2OAQzL2JJROHnb4yUXHPs90QTECqs90+w@mail.gmail.com>
Message-ID: <58E6AF85-C0E4-4EF0-A503-511E10060FF3@florian-schulze.net>

I'd say it depends on how much work a release is. If it's ok for you, 
then do a release. If it takes too much time in comparison to the 
severity of the issues, then old back a bit longer.

Regards,
Florian Schulze


On 23 Aug 2016, at 18:12, Bruno Oliveira wrote:

> Hi everyone,
>
> Since 3.0.0 was released, two regressions have been reported and this
> afternoon the fix for the last one was merged.
>
> Unless someone still has some issue that they would like to work on 
> for
> this release, I was thinking of making a 3.0.1 release tonight. What 
> you
> guys think? Should we wait a few more days to see if other regressions 
> show
> up, or the two we found so far are enough to warrant a release?
>
> Cheers,
> Bruno
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev

From me at the-compiler.org  Tue Aug 23 17:02:18 2016
From: me at the-compiler.org (Florian Bruhin)
Date: Tue, 23 Aug 2016 23:02:18 +0200
Subject: [pytest-dev] 3.0.1 tonight?
In-Reply-To: <CA+RQFfe7-2rUc7eFP2OAQzL2JJROHnb4yUXHPs90QTECqs90+w@mail.gmail.com>
References: <CA+RQFfe7-2rUc7eFP2OAQzL2JJROHnb4yUXHPs90QTECqs90+w@mail.gmail.com>
Message-ID: <20160823210218.nesfk7p2mvnsvjjd@tonks>

* Bruno Oliveira <nicoddemus at gmail.com> [2016-08-23 16:12:03 +0000]:
> Since 3.0.0 was released, two regressions have been reported and this
> afternoon the fix for the last one was merged.
> 
> Unless someone still has some issue that they would like to work on for
> this release, I was thinking of making a 3.0.1 release tonight. What you
> guys think? Should we wait a few more days to see if other regressions show
> up, or the two we found so far are enough to warrant a release?

Maybe we should try and get in a fix for the empty parametrization
regression too? https://github.com/pytest-dev/pytest/issues/1849

I can take a look, but that definitely won't be tonight, and probably
won't be until the weekend.

Other than that, +1 for a 3.0.1 sooner than later - I think the
parametrization thing is potentially dangerous (we're just calling
functions with arguments nobody wanted them to be called with...) and
affecting a handful of people.

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/20160823/84997157/attachment.sig>

From nicoddemus at gmail.com  Tue Aug 23 17:26:41 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Tue, 23 Aug 2016 21:26:41 +0000
Subject: [pytest-dev] 3.0.1 tonight?
In-Reply-To: <20160823210218.nesfk7p2mvnsvjjd@tonks>
References: <CA+RQFfe7-2rUc7eFP2OAQzL2JJROHnb4yUXHPs90QTECqs90+w@mail.gmail.com>
 <20160823210218.nesfk7p2mvnsvjjd@tonks>
Message-ID: <CA+RQFfcm_WOGoqDipdaKv4uDre9ebxwBtQgRR6cUm85Vt7TEVQ@mail.gmail.com>

On Tue, Aug 23, 2016 at 6:02 PM Florian Bruhin <me at the-compiler.org> wrote:

> * Bruno Oliveira <nicoddemus at gmail.com> [2016-08-23 16:12:03 +0000]:
> Maybe we should try and get in a fix for the empty parametrization
> regression too? https://github.com/pytest-dev/pytest/issues/1849


Agreed, just opened a PR: https://github.com/pytest-dev/pytest/pull/1855

As soon as we get this reviewed and merged I will release 3.0.1. :)

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

From raphael at hackebrot.de  Tue Aug 23 18:21:30 2016
From: raphael at hackebrot.de (Raphael Pierzina)
Date: Tue, 23 Aug 2016 23:21:30 +0100
Subject: [pytest-dev] 3.0.1 tonight?
In-Reply-To: <CA+RQFfcm_WOGoqDipdaKv4uDre9ebxwBtQgRR6cUm85Vt7TEVQ@mail.gmail.com>
References: <CA+RQFfe7-2rUc7eFP2OAQzL2JJROHnb4yUXHPs90QTECqs90+w@mail.gmail.com>
 <20160823210218.nesfk7p2mvnsvjjd@tonks>
 <CA+RQFfcm_WOGoqDipdaKv4uDre9ebxwBtQgRR6cUm85Vt7TEVQ@mail.gmail.com>
Message-ID: <48A87441-EA77-43F9-9038-A3D3CA4CFA29@hackebrot.de>

Sounds good! I?ll upgrade as soon as 3.0.1 is released :D Wohoo

(https://github.com/pytest-dev/pytest/pull/1847 <https://github.com/pytest-dev/pytest/pull/1847> is holding me back right now)

Thank you Bruno for managing the releases!

Raphael

> On 23 Aug 2016, at 22:26, Bruno Oliveira <nicoddemus at gmail.com> wrote:
> 
> 
> 
> On Tue, Aug 23, 2016 at 6:02 PM Florian Bruhin <me at the-compiler.org <mailto:me at the-compiler.org>> wrote:
> * Bruno Oliveira <nicoddemus at gmail.com <mailto:nicoddemus at gmail.com>> [2016-08-23 16:12:03 +0000]:
> Maybe we should try and get in a fix for the empty parametrization
> regression too? https://github.com/pytest-dev/pytest/issues/1849 <https://github.com/pytest-dev/pytest/issues/1849>
> 
> Agreed, just opened a PR: https://github.com/pytest-dev/pytest/pull/1855 <https://github.com/pytest-dev/pytest/pull/1855>
> 
> As soon as we get this reviewed and merged I will release 3.0.1. :)
> 
> Cheers,
> Bruno.
> _______________________________________________
> 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/20160823/6c8dca27/attachment.html>

From nicoddemus at gmail.com  Tue Aug 23 20:29:03 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Wed, 24 Aug 2016 00:29:03 +0000
Subject: [pytest-dev] pytest 3.0.1 released!
Message-ID: <CA+RQFfdR7feh1oVaGTW88Xqeux7LMVyjV5msWSj6HNzgFPH=WQ@mail.gmail.com>

Hi all,

pytest 3.0.1 has just been released to PyPI.

This release fixes some regressions reported in version 3.0.0, 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:

      Adam Chainz
      Andrew Svetlov
      Bruno Oliveira
      Daniel Hahler
      Dmitry Dygalo
      Florian Bruhin
      Marcin Bachry
      Ronny Pfannschmidt
      matthiasha

Happy testing,
The py.test Development Team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160824/0cb981dd/attachment-0001.html>

From cdent at anticdent.org  Wed Aug 24 08:31:28 2016
From: cdent at anticdent.org (Chris Dent)
Date: Wed, 24 Aug 2016 13:31:28 +0100 (IST)
Subject: [pytest-dev] process for replacing yield tests with modern style
Message-ID: <alpine.OSX.2.20.1608241314340.27225@shine.local>


Several years ago I developed a relative simple YAML-based way of
doing HTTP tests. The processed turned yaml into tests and yielded
them for pytest to collect. At the time yield was the pytest
approved way of doing such things. That's here:

    https://github.com/tiddlyweb/tiddlyweb/blob/master/test/http_runner.py

A few years later I took that idea and turned it into gabbi[1].

Because of local constraints (OpenStack) gabbi needed to be unittest,
subunit and testrepository compliant and oriented. Only later, and in
rather a hurry, did I add pytest support, using the yield style that I
already knew.

It's a bit of hacky mess because the tests are ordered
unittest.TestCases inside a unittest.TestSuite that has fixtures in
the scope of the TestSuite. Each yaml file becomes a TestSuite.
For the pytest side of things, plugin code[2] uses the modifyitems
hooks to get the fixtures working effectively. Some "driver"[3] code
yields tests to a user-code[4] for loading the tests.

I recognize that this is all a bit messy, but it does the job. Now,
with the advent of pytest 3.x yield tests are deprecated and I'm not
sure of the correct way to get the same behavior in modern-style.

I'm aware of solutions for using yaml files themselves as the test
files[5] but that would be a problem for existing deployed tests
that use the style shown in [4] and would also require conftest.py
or command line arguments and what I'm hoping to maintain is a way
for unadorned discovery to work and for the gabbi tests to be fairly
integrated with other tests.

I can certainly migrate to the [5] style but I see this as a good
opportunity to learn more of the details of how pytest generates
tests and use it. Can anyone give me some pointers please?

Thanks very much.

[1] https://gabbi.readthedocs.io/
[2] https://github.com/cdent/gabbi/blob/master/gabbi/pytester.py
[3] https://github.com/cdent/gabbi/blob/2bd1c803b71bd26be7822be87e249a811467b863/gabbi/driver.py#L111
[4] https://github.com/cdent/gabbi/blob/master/gabbi/tests/test_gabbits_pytest.py
[5] http://docs.pytest.org/en/latest/example/nonpython.html#a-basic-example-for-specifying-tests-in-yaml-files

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

From opensource at ronnypfannschmidt.de  Fri Aug 26 03:41:20 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Fri, 26 Aug 2016 09:41:20 +0200
Subject: [pytest-dev] [proposal] deprecating the pytest_namespace hook
Message-ID: <ff0c4605-7ef5-7ad9-9d0b-efeab2261e94@ronnypfannschmidt.de>



hi all

currently the need to initialize the namespace makes it necessary to do 
the initialization of the plugin-manager in a relatively ugly fashion 
and without full knowledge of what should happen to the process

i would like to remove that need, so we only ever initialize a 
pluginmanager from a call to pytest.main


-- Ronny


From nicoddemus at gmail.com  Fri Aug 26 07:45:41 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Fri, 26 Aug 2016 11:45:41 +0000
Subject: [pytest-dev] [proposal] deprecating the pytest_namespace hook
In-Reply-To: <ff0c4605-7ef5-7ad9-9d0b-efeab2261e94@ronnypfannschmidt.de>
References: <ff0c4605-7ef5-7ad9-9d0b-efeab2261e94@ronnypfannschmidt.de>
Message-ID: <CA+RQFfeZALPjy0j+-uF5bwZiEfJveNTk6sPVMQKbq-f2ns1e4A@mail.gmail.com>

Hi Ronny,

I'm not sure I understand what you mean by "ugly and without full knowledge
of what should happen"... could you give more details?

Also, what would we provide instead? This is a largely used feature, I'm
sure we can't just remove it.

Cheers

On Fri, Aug 26, 2016 at 4:41 AM Ronny Pfannschmidt <
opensource at ronnypfannschmidt.de> wrote:

>
>
> hi all
>
> currently the need to initialize the namespace makes it necessary to do
> the initialization of the plugin-manager in a relatively ugly fashion
> and without full knowledge of what should happen to the process
>
> i would like to remove that need, so we only ever initialize a
> pluginmanager from a call to pytest.main
>
>
> -- Ronny
>
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160826/c8b7a2f9/attachment.html>

From opensource at ronnypfannschmidt.de  Fri Aug 26 08:54:52 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Fri, 26 Aug 2016 14:54:52 +0200
Subject: [pytest-dev] [proposal] deprecating the pytest_namespace hook
In-Reply-To: <CA+RQFfeZALPjy0j+-uF5bwZiEfJveNTk6sPVMQKbq-f2ns1e4A@mail.gmail.com>
References: <ff0c4605-7ef5-7ad9-9d0b-efeab2261e94@ronnypfannschmidt.de>
 <CA+RQFfeZALPjy0j+-uF5bwZiEfJveNTk6sPVMQKbq-f2ns1e4A@mail.gmail.com>
Message-ID: <2dadfdf1-c45e-c85e-8b86-cc31e62e8d57@ronnypfannschmidt.de>

Hi Bruno,

the problem it creates is, that we need to load plugins before even 
parsing the config and before even having config object just in order to 
literally monkeypatch a module

the second problem it creates is, it makes the pytest namespace 
impossible to introspect for external tools

also - import works just fine - there is no need for a dynamic 
namespace, people can import from concrete/correct locations

-- Ronny

On 26.08.2016 13:45, Bruno Oliveira wrote:
> Hi Ronny,
>
> I'm not sure I understand what you mean by "ugly and without full 
> knowledge of what should happen"... could you give more details?
>
> Also, what would we provide instead? This is a largely used feature, 
> I'm sure we can't just remove it.
>
> Cheers
>
> On Fri, Aug 26, 2016 at 4:41 AM Ronny Pfannschmidt 
> <opensource at ronnypfannschmidt.de 
> <mailto:opensource at ronnypfannschmidt.de>> wrote:
>
>
>
>     hi all
>
>     currently the need to initialize the namespace makes it necessary
>     to do
>     the initialization of the plugin-manager in a relatively ugly fashion
>     and without full knowledge of what should happen to the process
>
>     i would like to remove that need, so we only ever initialize a
>     pluginmanager from a call to pytest.main
>
>
>     -- Ronny
>
>     _______________________________________________
>     pytest-dev mailing list
>     pytest-dev at python.org <mailto:pytest-dev at python.org>
>     https://mail.python.org/mailman/listinfo/pytest-dev
>

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

From nicoddemus at gmail.com  Fri Aug 26 09:00:56 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Fri, 26 Aug 2016 13:00:56 +0000
Subject: [pytest-dev] [proposal] deprecating the pytest_namespace hook
In-Reply-To: <2dadfdf1-c45e-c85e-8b86-cc31e62e8d57@ronnypfannschmidt.de>
References: <ff0c4605-7ef5-7ad9-9d0b-efeab2261e94@ronnypfannschmidt.de>
 <CA+RQFfeZALPjy0j+-uF5bwZiEfJveNTk6sPVMQKbq-f2ns1e4A@mail.gmail.com>
 <2dadfdf1-c45e-c85e-8b86-cc31e62e8d57@ronnypfannschmidt.de>
Message-ID: <CA+RQFfeKf_hD__OHKjemK+CFXfXSAwimc6LTrrAx4S7dLSwjyw@mail.gmail.com>

On Fri, Aug 26, 2016 at 9:54 AM Ronny Pfannschmidt <
opensource at ronnypfannschmidt.de> wrote:

> the problem it creates is, that we need to load plugins before even
> parsing the config and before even having config object just in order to
> literally monkeypatch a module
>

You mean that just importing "pytest" you automatically load all plugins?
Hmmm I agree that's not very nice.

the second problem it creates is, it makes the pytest namespace impossible
> to introspect for external tools
>

I agree that's annoying, but that's a problem in general on how dynamic
pytest is (IDEs don't autocomplete on fixture parameters either), so I
would say this is small.


> also - import works just fine - there is no need for a dynamic namespace,
> people can import from concrete/correct locations
>

I see, but TBH I don't see how we could just deprecate that without
providing an alternative solution which won't break user code. Too many
plugins and code depend on that, and we would need to have a **really**
good reason to break them all in a future pytest version (I wouldn't even
dare to introduce such a deprecation until 4.0 for example).

But that's my opinion of course.

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

From opensource at ronnypfannschmidt.de  Fri Aug 26 09:06:57 2016
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Fri, 26 Aug 2016 15:06:57 +0200
Subject: [pytest-dev] [proposal] deprecating the pytest_namespace hook
In-Reply-To: <CA+RQFfeKf_hD__OHKjemK+CFXfXSAwimc6LTrrAx4S7dLSwjyw@mail.gmail.com>
References: <ff0c4605-7ef5-7ad9-9d0b-efeab2261e94@ronnypfannschmidt.de>
 <CA+RQFfeZALPjy0j+-uF5bwZiEfJveNTk6sPVMQKbq-f2ns1e4A@mail.gmail.com>
 <2dadfdf1-c45e-c85e-8b86-cc31e62e8d57@ronnypfannschmidt.de>
 <CA+RQFfeKf_hD__OHKjemK+CFXfXSAwimc6LTrrAx4S7dLSwjyw@mail.gmail.com>
Message-ID: <7dbcc626-05fd-6a29-22a0-6594a65cd195@ronnypfannschmidt.de>



On 26.08.2016 15:00, Bruno Oliveira wrote:
> On Fri, Aug 26, 2016 at 9:54 AM Ronny Pfannschmidt 
> <opensource at ronnypfannschmidt.de 
> <mailto:opensource at ronnypfannschmidt.de>> wrote:
>
>     the problem it creates is, that we need to load plugins before
>     even parsing the config and before even having config object just
>     in order to literally monkeypatch a module
>
>
> You mean that just importing "pytest" you automatically load all 
> plugins? Hmmm I agree that's not very nice.
>
>     the second problem it creates is, it makes the pytest namespace
>     impossible to introspect for external tools
>
>
> I agree that's annoying, but that's a problem in general on how 
> dynamic pytest is (IDEs don't autocomplete on fixture parameters 
> either), so I would say this is small.
>
>     also - import works just fine - there is no need for a dynamic
>     namespace, people can import from concrete/correct locations
>
>
> I see, but TBH I don't see how we could just deprecate that without 
> providing an alternative solution which won't break user code. Too 
> many plugins and code depend on that, and we would need to have a 
> **really** good reason to break them all in a future pytest version (I 
> wouldn't even dare to introduce such a deprecation until 4.0 for example).
>
it does not even need an alternative - there is *import* of python 
people can just import their objects from their locations *and* have 
code completion/analysis work

since the namespace hook is executed at pre config time it has next to 
no added value except for monkeypatching py.test's own namespace
  as a utility of convenience

i think all it needs is some kind of wrapper for the namespace noting 
that this feature was deprecated on usage

then for 4.0 we could make the namespace lazy-loaded, and for 5.0 we 
could remove it altogether

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

From rpfannsc at redhat.com  Mon Aug 29 04:31:47 2016
From: rpfannsc at redhat.com (Ronny Pfannschmidt)
Date: Mon, 29 Aug 2016 10:31:47 +0200
Subject: [pytest-dev] process for replacing yield tests with modern style
In-Reply-To: <alpine.OSX.2.20.1608241314340.27225@shine.local>
References: <alpine.OSX.2.20.1608241314340.27225@shine.local>
Message-ID: <CAA10jzM21GXmOtjvwTXi5PxU5pqoxwkpAb2gSMinMqjZkOO8yA@mail.gmail.com>

Hi Chris,

currently there is no easy/good Replacement for the use-case you outline.
the "correct" way would be a custom py.test specific collector

note that it was mostly luck this worked at all - ever since py.test
switched to collect first yield tests where semantically broken due to
running and destroying their own setupstate at collection time

-- Ronny

2016-08-24 14:31 GMT+02:00 Chris Dent <cdent at anticdent.org>:

>
> Several years ago I developed a relative simple YAML-based way of
> doing HTTP tests. The processed turned yaml into tests and yielded
> them for pytest to collect. At the time yield was the pytest
> approved way of doing such things. That's here:
>
>    https://github.com/tiddlyweb/tiddlyweb/blob/master/test/http_runner.py
>
> A few years later I took that idea and turned it into gabbi[1].
>
> Because of local constraints (OpenStack) gabbi needed to be unittest,
> subunit and testrepository compliant and oriented. Only later, and in
> rather a hurry, did I add pytest support, using the yield style that I
> already knew.
>
> It's a bit of hacky mess because the tests are ordered
> unittest.TestCases inside a unittest.TestSuite that has fixtures in
> the scope of the TestSuite. Each yaml file becomes a TestSuite.
> For the pytest side of things, plugin code[2] uses the modifyitems
> hooks to get the fixtures working effectively. Some "driver"[3] code
> yields tests to a user-code[4] for loading the tests.
>
> I recognize that this is all a bit messy, but it does the job. Now,
> with the advent of pytest 3.x yield tests are deprecated and I'm not
> sure of the correct way to get the same behavior in modern-style.
>
> I'm aware of solutions for using yaml files themselves as the test
> files[5] but that would be a problem for existing deployed tests
> that use the style shown in [4] and would also require conftest.py
> or command line arguments and what I'm hoping to maintain is a way
> for unadorned discovery to work and for the gabbi tests to be fairly
> integrated with other tests.
>
> I can certainly migrate to the [5] style but I see this as a good
> opportunity to learn more of the details of how pytest generates
> tests and use it. Can anyone give me some pointers please?
>
> Thanks very much.
>
> [1] https://gabbi.readthedocs.io/
> [2] https://github.com/cdent/gabbi/blob/master/gabbi/pytester.py
> [3] https://github.com/cdent/gabbi/blob/2bd1c803b71bd26be7822be8
> 7e249a811467b863/gabbi/driver.py#L111
> [4] https://github.com/cdent/gabbi/blob/master/gabbi/tests/test_
> gabbits_pytest.py
> [5] http://docs.pytest.org/en/latest/example/nonpython.html#a-
> basic-example-for-specifying-tests-in-yaml-files
>
> --
> Chris Dent               ????( ? _ ??)        https://anticdent.org/
> freenode: cdent                                         tw: @anticdent
> _______________________________________________
> 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/20160829/209e998c/attachment.html>

From variedthoughts at gmail.com  Mon Aug 15 01:42:15 2016
From: variedthoughts at gmail.com (Brian Okken)
Date: Sun, 14 Aug 2016 22:42:15 -0700
Subject: [pytest-dev] Remove invocation fixtures from 3.0?
In-Reply-To: <CA+RQFffJUTH=Cefsw64RtW_h5ik8h7-DqYdf7iAhE1fc5=LCvA@mail.gmail.com>
References: <CA+RQFffJUTH=Cefsw64RtW_h5ik8h7-DqYdf7iAhE1fc5=LCvA@mail.gmail.com>
Message-ID: <054168F9-3C2A-46C9-B112-978BB38515A1@gmail.com>

Hi,

I know you weren't asking me, but I do lurk on the mailing list. 
I think pulling invocation scoped fixtures for the 3.0 release is an awesome solution for now. If this were a commercial software system this feature would be regarded as a nice to have feature for the release. Meaning it doesn't get to hold up shipment to get fixed.

My two cents. 

BTW. Thanks for all the hard work to get 3.0 out, and all the previous work you've done on the project. 

- Brian Okken

> On Aug 14, 2016, at 6:15 PM, Bruno Oliveira <nicoddemus at gmail.com> wrote:
> 
> Hi everyone,
> 
> I've worked on the weekend on the issue discovered by Florian on the qutebrowser test suite, and unfortunately I think the current implementation will have to be re-thought because it contains a serious problem regarding finalizers when fixtures are being overwritten.
> 
> Because redesigning it might take a awhile, I suggest we remove invocation fixtures for now so we can make the 3.0 release. We can then work this week on the remaining issues[1] and make a release candidate by the middle of the week, aiming for the official release by the end of the week.
> 
> How does that sound?
> 
> Cheers,
> Bruno.
> 
> [1] https://github.com/pytest-dev/pytest/milestone/2 
> 
> 
> _______________________________________________
> 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/20160814/d5ec28ba/attachment.html>

From rpfannsc at redhat.com  Wed Aug 31 10:51:33 2016
From: rpfannsc at redhat.com (Ronny Pfannschmidt)
Date: Wed, 31 Aug 2016 16:51:33 +0200
Subject: [pytest-dev] [proposal] collection roots
Message-ID: <CAA10jzOX5OaTnu7TNfCJoKREX=n1DJume=y-0qZQhuwwr+6Wxg@mail.gmail.com>

Hi everyone,

at work i am hitting a problem where tests have to be shared between teams,
while fixtures may differ

in order to ease that i came up with a initial idea for specifying where to
look for tests in pytest.ini


example:
[pytest]
collect_roots=
  base=module://framework.basetests
  myteam=file://./test/


with a default value of

collect_roots=
  . = file://.


the specification would give the possibility to make test suite repos
and import test suites



-- 

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/20160831/0764768f/attachment.html>

From nicoddemus at gmail.com  Wed Aug 31 13:48:17 2016
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Wed, 31 Aug 2016 17:48:17 +0000
Subject: [pytest-dev] [proposal] collection roots
In-Reply-To: <CAA10jzOX5OaTnu7TNfCJoKREX=n1DJume=y-0qZQhuwwr+6Wxg@mail.gmail.com>
References: <CAA10jzOX5OaTnu7TNfCJoKREX=n1DJume=y-0qZQhuwwr+6Wxg@mail.gmail.com>
Message-ID: <CA+RQFfdmPLdbv56csaN73beJk32N-MFnosC7qPMYxdjb45d5HA@mail.gmail.com>

Hi Ronny,

We?ve had the same need at work, although it seems in a smaller scale than
yours. This is the approach we took:

Shared tests are always in classes without a Test prefix so they won?t be
collected. Those base classes may be then subclassed in different projects
and implement the required fixtures:

# file in a "base project" somewhereclass BaseSerializerTests:

    @pytest.fixture
    def serializer(self):
        assert 0, 'implement fixture in your subclass'

    def test_dump(serializer):
        d = {'data': 1}
        assert serializer.loads(serializer.dumps(d)) == d

    def test_numericals(serializer):
        assert serializer.loads(serializer.dumps(99)) == 99

# file in "json" project somewherefrom base_project import BaseSerializerTests
class TestJSONSerializer(BaseSerializerTests):

    @pytest.fixture
    def serializer(self):
        return JSONSerializer()

# file in "hdf" project somewherefrom base_project import BaseSerializerTests
class TestHDFSerializer(BaseSerializerTests):

    @pytest.fixture
    def serializer(self, tmpdir):
        return HDFSerializer(tmpdir.join('test.hdf'))

The advantages are that we don?t need to customize pytest at all and tests
added to the base test classes propagate naturally to the subclasses in
other projects. Also, each fixture is free to depend on other fixtures
naturally, like tmpdir on the second example.

Not sure if the above scales for your company thought.

Back to your proposal: can?t it be implemented as a plugin instead of in
the core?

Cheers,
Bruno.
?

On Wed, Aug 31, 2016 at 2:37 PM Ronny Pfannschmidt <rpfannsc at redhat.com>
wrote:

> Hi everyone,
>
> at work i am hitting a problem where tests have to be shared between
> teams, while fixtures may differ
>
> in order to ease that i came up with a initial idea for specifying where
> to look for tests in pytest.ini
>
>
> example:
> [pytest]
> collect_roots=
>   base=module://framework.basetests
>   myteam=file://./test/
>
>
> with a default value of
>
> collect_roots=
>   . = file://.
>
>
> the specification would give the possibility to make test suite repos
> and import test suites
>
>
>
> --
>
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160831/036aea74/attachment.html>

From variedthoughts at gmail.com  Wed Aug 31 17:07:39 2016
From: variedthoughts at gmail.com (Brian Okken)
Date: Wed, 31 Aug 2016 14:07:39 -0700
Subject: [pytest-dev] [proposal] collection roots
In-Reply-To: <CA+RQFfdmPLdbv56csaN73beJk32N-MFnosC7qPMYxdjb45d5HA@mail.gmail.com>
References: <CAA10jzOX5OaTnu7TNfCJoKREX=n1DJume=y-0qZQhuwwr+6Wxg@mail.gmail.com>
 <CA+RQFfdmPLdbv56csaN73beJk32N-MFnosC7qPMYxdjb45d5HA@mail.gmail.com>
Message-ID: <B14DFADC-80D9-43E9-8C6B-896A69629171@gmail.com>

I have recommended Bruno's solution several times. 
Same model works with unittest. 
If Ronny's idea moves forward I'd rather see that as a plugin than in core if possible. 

- Brian

> On Aug 31, 2016, at 10:48 AM, Bruno Oliveira <nicoddemus at gmail.com> wrote:
> 
> Hi Ronny,
> 
> We?ve had the same need at work, although it seems in a smaller scale than yours. This is the approach we took:
> 
> Shared tests are always in classes without a Test prefix so they won?t be collected. Those base classes may be then subclassed in different projects and implement the required fixtures:
> 
> # file in a "base project" somewhere
> class BaseSerializerTests:
> 
>     @pytest.fixture
>     def serializer(self):
>         assert 0, 'implement fixture in your subclass'
> 
>     def test_dump(serializer):
>         d = {'data': 1}
>         assert serializer.loads(serializer.dumps(d)) == d
> 
>     def test_numericals(serializer):
>         assert serializer.loads(serializer.dumps(99)) == 99
> # file in "json" project somewhere
> from base_project import BaseSerializerTests
> 
> class TestJSONSerializer(BaseSerializerTests):
> 
>     @pytest.fixture
>     def serializer(self):
>         return JSONSerializer()
> # file in "hdf" project somewhere
> from base_project import BaseSerializerTests
> 
> class TestHDFSerializer(BaseSerializerTests):
> 
>     @pytest.fixture
>     def serializer(self, tmpdir):
>         return HDFSerializer(tmpdir.join('test.hdf'))
> The advantages are that we don?t need to customize pytest at all and tests added to the base test classes propagate naturally to the subclasses in other projects. Also, each fixture is free to depend on other fixtures naturally, like tmpdir on the second example.
> 
> Not sure if the above scales for your company thought.
> 
> Back to your proposal: can?t it be implemented as a plugin instead of in the core?
> 
> Cheers,
> Bruno.
> 
> 
>> On Wed, Aug 31, 2016 at 2:37 PM Ronny Pfannschmidt <rpfannsc at redhat.com> wrote:
>> Hi everyone,
>> 
>> at work i am hitting a problem where tests have to be shared between teams, while fixtures may differ
>> 
>> in order to ease that i came up with a initial idea for specifying where to look for tests in pytest.ini
>> 
>> 
>> example:
>> [pytest]
>> collect_roots=
>>   base=module://framework.basetests
>>   myteam=file://./test/
>> 
>> 
>> with a default value of 
>> 
>> collect_roots=
>>   . = file://.
>> 
>> 
>> the specification would give the possibility to make test suite repos 
>> and import test suites
>> 
>>   
>> 
>> -- 
>> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160831/1e2f22f7/attachment-0001.html>