From aidis at pycon.lt  Wed Mar  4 01:22:10 2020
From: aidis at pycon.lt (Aidis Stukas @ PyConLT)
Date: Wed, 4 Mar 2020 08:22:10 +0200
Subject: [pytest-dev] Invitation to PyCon Lithuania for talks/sprints
Message-ID: <CA+JkJxSQpMRpP=DiphmozWa4RN0oKVhkK-5THvB_whdRRU1B_Q@mail.gmail.com>

 Hi PyTest developers,

I am looking for someone to give a talk/run a sprint on pytest at PyCon
Lithuania conference (https://www.pycon.lt)
The conference will take place on May 22-24 with 300+ participants.

Please contact me if you are interested.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20200304/f93e2b81/attachment.html>

From opensource at ronnypfannschmidt.de  Sat Mar  7 13:48:34 2020
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Sat, 7 Mar 2020 19:48:34 +0100
Subject: [pytest-dev] Proposal: Elevating Ran Benita/@bluetech from
 Contributor to Core
Message-ID: <f4502ee1-7c88-0e7d-b828-ccb0bf1414f1@ronnypfannschmidt.de>

Hi everyone,

over the last few months Ran demonstrated both excellent communication 
and contribution.
I believe Ran would make a great addition to the Core team.

So after reaching out to Ran to check if that's ok,
I'm asking the rest us to formalize addition..

-- Ronny


From nicoddemus at gmail.com  Sun Mar  8 14:57:31 2020
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Sun, 8 Mar 2020 15:57:31 -0300
Subject: [pytest-dev] Proposal: Elevating Ran Benita/@bluetech from
 Contributor to Core
In-Reply-To: <f4502ee1-7c88-0e7d-b828-ccb0bf1414f1@ronnypfannschmidt.de>
References: <f4502ee1-7c88-0e7d-b828-ccb0bf1414f1@ronnypfannschmidt.de>
Message-ID: <CA+RQFffEpDJL5JTz+NNTKGY_wnC=kmM7PdMVupx0vTVQiHXVfQ@mail.gmail.com>

Definitely +1

On Sat, Mar 7, 2020 at 3:55 PM Ronny Pfannschmidt <
opensource at ronnypfannschmidt.de> wrote:

> Hi everyone,
>
> over the last few months Ran demonstrated both excellent communication
> and contribution.
> I believe Ran would make a great addition to the Core team.
>
> So after reaching out to Ran to check if that's ok,
> I'm asking the rest us to formalize addition..
>
> -- 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/20200308/7f930deb/attachment.html>

From tgoodlet at gmail.com  Sun Mar  8 15:51:05 2020
From: tgoodlet at gmail.com (Tyler Goodlet)
Date: Sun, 8 Mar 2020 15:51:05 -0400
Subject: [pytest-dev] Proposal: Elevating Ran Benita/@bluetech from
 Contributor to Core
In-Reply-To: <f4502ee1-7c88-0e7d-b828-ccb0bf1414f1@ronnypfannschmidt.de>
References: <f4502ee1-7c88-0e7d-b828-ccb0bf1414f1@ronnypfannschmidt.de>
Message-ID: <CAOfDtvokg+QTsrVTXSfmm=27+tvmA1E0+9QY4_=U3hoH22e-Pw@mail.gmail.com>

+1 from myself as well considering the couple contribs to pluggy :)

- goodboy

On Sat, Mar 7, 2020 at 1:55 PM Ronny Pfannschmidt
<opensource at ronnypfannschmidt.de> wrote:
>
> Hi everyone,
>
> over the last few months Ran demonstrated both excellent communication
> and contribution.
> I believe Ran would make a great addition to the Core team.
>
> So after reaching out to Ran to check if that's ok,
> I'm asking the rest us to formalize addition..
>
> -- Ronny
>
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev

From nicoddemus at gmail.com  Mon Mar  9 16:25:44 2020
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Mon, 9 Mar 2020 17:25:44 -0300
Subject: [pytest-dev] Proposal: Elevating Ran Benita/@bluetech from
 Contributor to Core
In-Reply-To: <CAOfDtvokg+QTsrVTXSfmm=27+tvmA1E0+9QY4_=U3hoH22e-Pw@mail.gmail.com>
References: <f4502ee1-7c88-0e7d-b828-ccb0bf1414f1@ronnypfannschmidt.de>
 <CAOfDtvokg+QTsrVTXSfmm=27+tvmA1E0+9QY4_=U3hoH22e-Pw@mail.gmail.com>
Message-ID: <CA+RQFfd1B0=dkv4yO-TnQ8CL2ueijLzM-FQ3Ef9xfVLfjq810Q@mail.gmail.com>

Hi everyone,

I think this is unanimous then, I've added bluetech to the Core team.

Cheers,
Bruno

On Sun, Mar 8, 2020 at 4:51 PM Tyler Goodlet <tgoodlet at gmail.com> wrote:

> +1 from myself as well considering the couple contribs to pluggy :)
>
> - goodboy
>
> On Sat, Mar 7, 2020 at 1:55 PM Ronny Pfannschmidt
> <opensource at ronnypfannschmidt.de> wrote:
> >
> > Hi everyone,
> >
> > over the last few months Ran demonstrated both excellent communication
> > and contribution.
> > I believe Ran would make a great addition to the Core team.
> >
> > So after reaching out to Ran to check if that's ok,
> > I'm asking the rest us to formalize addition..
> >
> > -- Ronny
> >
> > _______________________________________________
> > 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/20200309/b2989537/attachment.html>

From ran at unusedvar.com  Tue Mar 10 14:31:20 2020
From: ran at unusedvar.com (Ran Benita)
Date: Tue, 10 Mar 2020 20:31:20 +0200
Subject: [pytest-dev] 
 =?utf-8?q?Proposal=3A_Elevating_Ran_Benita/=40bluet?=
 =?utf-8?q?ech_from_Contributor_to_Core?=
In-Reply-To: <CA+RQFfd1B0=dkv4yO-TnQ8CL2ueijLzM-FQ3Ef9xfVLfjq810Q@mail.gmail.com>
References: <f4502ee1-7c88-0e7d-b828-ccb0bf1414f1@ronnypfannschmidt.de>
 <CAOfDtvokg+QTsrVTXSfmm=27+tvmA1E0+9QY4_=U3hoH22e-Pw@mail.gmail.com>
 <CA+RQFfd1B0=dkv4yO-TnQ8CL2ueijLzM-FQ3Ef9xfVLfjq810Q@mail.gmail.com>
Message-ID: <9f7a717d-45d8-4f2f-9aa1-aade1253b362@www.fastmail.com>

Thanks everyone. I'm happy to be a part of the team.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20200310/2bb6ef6c/attachment.html>

From opensource at ronnypfannschmidt.de  Thu Mar 12 15:32:59 2020
From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt)
Date: Thu, 12 Mar 2020 20:32:59 +0100
Subject: [pytest-dev] pytest 5.4.0 released
Message-ID: <2ab8d7e7-83fb-5938-2dc9-18ea1f3b1104@ronnypfannschmidt.de>

pytest-5.4.0
=======================================

The pytest team is proud to announce the 5.4.0 release!

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

This release contains a number of bug fixes and improvements, so users are encouraged
to take a look at the CHANGELOG:

     https://docs.pytest.org/en/latest/changelog.html

For complete documentation, please visit:

     https://docs.pytest.org/en/latest/

As usual, you can upgrade from PyPI via:

     pip install -U pytest

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

* Anthony Sottile
* Bruno Oliveira
* Christoph Buelter
* Christoph B?lter
* Daniel Arndt
* Daniel Hahler
* Holger Kohr
* Hugo
* Hugo van Kemenade
* Jakub Mitoraj
* Kyle Altendorf
* Minuddin Ahmed Rana
* Nathaniel Compton
* ParetoLife
* Pauli Virtanen
* Philipp Loose
* Ran Benita
* Ronny Pfannschmidt
* Stefan Scherfke
* Stefano Mazzucco
* TWood67
* Tobias Schmidt
* Tom?? Gaven?iak
* Vinay Calastry
* Vladyslav Rachek
* Zac Hatfield-Dodds
* captainCapitalism
* cmachalo
* gftea
* kpinc
* rebecca-palmer
* sdementen


Happy testing,
The pytest Development Team


From nicoddemus at gmail.com  Fri Mar 13 10:08:11 2020
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Fri, 13 Mar 2020 11:08:11 -0300
Subject: [pytest-dev] pytest 5.4.1 released!
Message-ID: <CA+RQFffMtzdG+aGE0G=et9YcPj8J+LCSVw==eTJp3JTYH6cL=g@mail.gmail.com>

pytest 5.4.1 has just been released to PyPI.

This is a bug-fix release, fixing a regression discovered in 5.4.0, being a
drop-in replacement. To upgrade::

  pip install --upgrade pytest

The full changelog is available at
https://docs.pytest.org/en/latest/changelog.html.

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

* Bruno Oliveira


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

From holger at merlinux.eu  Tue Mar 17 07:46:49 2020
From: holger at merlinux.eu (holger krekel)
Date: Tue, 17 Mar 2020 12:46:49 +0100
Subject: [pytest-dev] message to my IT/hacking friends Mar17
Message-ID: <20200317114649.GN32362@beto>

Dear pytestonistas, 

i sincerely hope that you all are well or find ways of adjusting --
#covid19 is a social and emotional challenge of planeraty scale. 
I've written down a little "message to my IT/hacking" friends: 

https://holgerkrekel.net/2020/03/17/message-to-my-it-hacking-friends-mar17/

As some of you know i am involved in Delta Chat and if you feel
you would like to help build a resilient messaging eco-system 
that works well in shutdown situations (it does in Cuba, Russia, Iran
and other places) ... and if you feel you and people around you and close
to you are in a good enough situation to help ... then maybe join #deltachat
on freenode and https://lists.codespeak.net/postorius/lists/delta.codespeak.net/ ...
i intend to post some bits there where i'd love help from Pythonistas and pytestas :) 
But really, don't feel obliged in any way -- stay safe and socially distant,
take breaks from the digital!

holger

From m at maximilianroos.com  Thu Mar 26 18:29:16 2020
From: m at maximilianroos.com (Maximilian Roos)
Date: Thu, 26 Mar 2020 18:29:16 -0400
Subject: [pytest-dev] Fwd: Continuing on failures
In-Reply-To: <CAFeL3qFb_bU7oyw3o6vtvqR_5Nr+aVJQ1JGFDXQqx3mHyR8DWQ@mail.gmail.com>
References: <CAFeL3qFb_bU7oyw3o6vtvqR_5Nr+aVJQ1JGFDXQqx3mHyR8DWQ@mail.gmail.com>
Message-ID: <CAFeL3qEgaLqQDBMUp6+Q5arFi1VQjr=AhXBQVs5Q7pWc-n_-mQ@mail.gmail.com>

Hi there,

To prefix: as a long time user and evangelizer of pytest, a big thank you
for the superb tool.

I wanted to build a tool that replaces incorrect values in tests with
correct values, similar to frameworks like rust's insta
<https://github.com/mitsuhiko/insta> or ocaml's ppx_expect
<https://github.com/janestreet/ppx_expect>, but ideally in the pytest
spirit of retaining the use of `assert` rather than a custom function. I
built a PoC <https://github.com/max-sixty/pytest-accept> that successfully
replaces the *first* error in a test with the correct value.

As per that README, it only works on the first failure, because the test
doesn't continue execution beyond that. *Is there any way of allowing
execution to continue, without ripping up the internals of pytest?* My
prior is "no", since the assertion rewrite still retains an assertion, and
there's no hook for changing that.

Ref: a similar question I asked @okken
https://github.com/okken/pytest-check/issues/32

Thank you,
Max
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20200326/9f8c84de/attachment.html>

From nicoddemus at gmail.com  Fri Mar 27 07:46:51 2020
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Fri, 27 Mar 2020 08:46:51 -0300
Subject: [pytest-dev] Fwd: Continuing on failures
In-Reply-To: <CAFeL3qEgaLqQDBMUp6+Q5arFi1VQjr=AhXBQVs5Q7pWc-n_-mQ@mail.gmail.com>
References: <CAFeL3qFb_bU7oyw3o6vtvqR_5Nr+aVJQ1JGFDXQqx3mHyR8DWQ@mail.gmail.com>
 <CAFeL3qEgaLqQDBMUp6+Q5arFi1VQjr=AhXBQVs5Q7pWc-n_-mQ@mail.gmail.com>
Message-ID: <CA+RQFfdedebFG0+DFuqmY1_FCMo8_6eJHJemc-hBPL7zVsUd7A@mail.gmail.com>

Hi Maximilian,

On Thu, Mar 26, 2020 at 7:29 PM Maximilian Roos <m at maximilianroos.com>
wrote:

>
> To prefix: as a long time user and evangelizer of pytest, a big thank you
> for the superb tool.
>

Thanks for the kind words, we appreciate it.


> As per that README, it only works on the first failure, because the test
> doesn't continue execution beyond that. *Is there any way of allowing
> execution to continue, without ripping up the internals of pytest?* My
> prior is "no", since the assertion rewrite still retains an assertion, and
> there's no hook for changing that.
>

Not at the moment I'm afraid.

I think it should be possible to implement a hook that transforms the AST,
which our rewriter would then call. I think, with this hook in place, you
would be able to rewrite assert statements into a function call of your
plugin, which would then be free to do whatever it wanted. If you are
interested, I suggest writing up a proposal in the issue tracker so it can
be discussed.

Cheers,
Bruno


> Ref: a similar question I asked @okken
> https://github.com/okken/pytest-check/issues/32
>
> Thank you,
> Max
> _______________________________________________
> 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/20200327/bb2c463d/attachment.html>

From victor.maryama at gmail.com  Fri Mar 27 09:26:12 2020
From: victor.maryama at gmail.com (Victor Maryama)
Date: Fri, 27 Mar 2020 14:26:12 +0100
Subject: [pytest-dev] Fwd: Continuing on failures
In-Reply-To: <CA+RQFfdedebFG0+DFuqmY1_FCMo8_6eJHJemc-hBPL7zVsUd7A@mail.gmail.com>
References: <CAFeL3qFb_bU7oyw3o6vtvqR_5Nr+aVJQ1JGFDXQqx3mHyR8DWQ@mail.gmail.com>
 <CAFeL3qEgaLqQDBMUp6+Q5arFi1VQjr=AhXBQVs5Q7pWc-n_-mQ@mail.gmail.com>
 <CA+RQFfdedebFG0+DFuqmY1_FCMo8_6eJHJemc-hBPL7zVsUd7A@mail.gmail.com>
Message-ID: <CAN0FtzN+g8y78wvOe9TOMPU-BJhU7kOR+SEUhULM7ndqbmQofg@mail.gmail.com>

What about pytest-assume as a context manager around the assert line?
That way you get the soft assertions feature and pytest still rewrites the
assertions.

On Fri, Mar 27, 2020, 12:47 PM Bruno Oliveira <nicoddemus at gmail.com> wrote:

> Hi Maximilian,
>
> On Thu, Mar 26, 2020 at 7:29 PM Maximilian Roos <m at maximilianroos.com>
> wrote:
>
>>
>> To prefix: as a long time user and evangelizer of pytest, a big thank you
>> for the superb tool.
>>
>
> Thanks for the kind words, we appreciate it.
>
>
>> As per that README, it only works on the first failure, because the test
>> doesn't continue execution beyond that. *Is there any way of allowing
>> execution to continue, without ripping up the internals of pytest?* My
>> prior is "no", since the assertion rewrite still retains an assertion, and
>> there's no hook for changing that.
>>
>
> Not at the moment I'm afraid.
>
> I think it should be possible to implement a hook that transforms the AST,
> which our rewriter would then call. I think, with this hook in place, you
> would be able to rewrite assert statements into a function call of your
> plugin, which would then be free to do whatever it wanted. If you are
> interested, I suggest writing up a proposal in the issue tracker so it can
> be discussed.
>
> Cheers,
> Bruno
>
>
>> Ref: a similar question I asked @okken
>> https://github.com/okken/pytest-check/issues/32
>>
>> Thank you,
>> Max
>> _______________________________________________
>> 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/20200327/a59d9e65/attachment.html>

From m at maximilianroos.com  Fri Mar 27 12:09:39 2020
From: m at maximilianroos.com (Maximilian Roos)
Date: Fri, 27 Mar 2020 12:09:39 -0400
Subject: [pytest-dev] Fwd: Continuing on failures
In-Reply-To: <CAN0FtzN+g8y78wvOe9TOMPU-BJhU7kOR+SEUhULM7ndqbmQofg@mail.gmail.com>
References: <CAFeL3qFb_bU7oyw3o6vtvqR_5Nr+aVJQ1JGFDXQqx3mHyR8DWQ@mail.gmail.com>
 <CAFeL3qEgaLqQDBMUp6+Q5arFi1VQjr=AhXBQVs5Q7pWc-n_-mQ@mail.gmail.com>
 <CA+RQFfdedebFG0+DFuqmY1_FCMo8_6eJHJemc-hBPL7zVsUd7A@mail.gmail.com>
 <CAN0FtzN+g8y78wvOe9TOMPU-BJhU7kOR+SEUhULM7ndqbmQofg@mail.gmail.com>
Message-ID: <CAFeL3qE=xp2EGYQXibAs0kh8rGXjup+YTaVnsyS=977EmzYZpQ@mail.gmail.com>

Hi Victor,

> What about pytest-assume as a context manager around the assert line?

Yes, this could work with either a context manager or a function like
pytest-check uses.
But it couples the plugin to the tests; it's no longer possible to run the
plugin on normal tests with a plain `assert`, which is some of the
brilliant philosophy of pytest.

Without such a hook, I think the function or context manager is the best
path forward, and is a reasonable way to build a better prototype before
adding hooks deep in pytest internals.

Thank you!
Max

On Fri, 27 Mar 2020 at 09:26, Victor Maryama <victor.maryama at gmail.com>
wrote:

> What about pytest-assume as a context manager around the assert line?
> That way you get the soft assertions feature and pytest still rewrites the
> assertions.
>
> On Fri, Mar 27, 2020, 12:47 PM Bruno Oliveira <nicoddemus at gmail.com>
> wrote:
>
>> Hi Maximilian,
>>
>> On Thu, Mar 26, 2020 at 7:29 PM Maximilian Roos <m at maximilianroos.com>
>> wrote:
>>
>>>
>>> To prefix: as a long time user and evangelizer of pytest, a big thank
>>> you for the superb tool.
>>>
>>
>> Thanks for the kind words, we appreciate it.
>>
>>
>>> As per that README, it only works on the first failure, because the test
>>> doesn't continue execution beyond that. *Is there any way of allowing
>>> execution to continue, without ripping up the internals of pytest?* My
>>> prior is "no", since the assertion rewrite still retains an assertion, and
>>> there's no hook for changing that.
>>>
>>
>> Not at the moment I'm afraid.
>>
>> I think it should be possible to implement a hook that transforms the
>> AST, which our rewriter would then call. I think, with this hook in place,
>> you would be able to rewrite assert statements into a function call of your
>> plugin, which would then be free to do whatever it wanted. If you are
>> interested, I suggest writing up a proposal in the issue tracker so it can
>> be discussed.
>>
>> Cheers,
>> Bruno
>>
>>
>>> Ref: a similar question I asked @okken
>>> https://github.com/okken/pytest-check/issues/32
>>>
>>> Thank you,
>>> Max
>>> _______________________________________________
>>> 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/20200327/6da6e8bb/attachment.html>

From victor.maryama at gmail.com  Fri Mar 27 12:19:28 2020
From: victor.maryama at gmail.com (Victor Maryama)
Date: Fri, 27 Mar 2020 17:19:28 +0100
Subject: [pytest-dev] Fwd: Continuing on failures
In-Reply-To: <CAFeL3qE=xp2EGYQXibAs0kh8rGXjup+YTaVnsyS=977EmzYZpQ@mail.gmail.com>
References: <CAFeL3qFb_bU7oyw3o6vtvqR_5Nr+aVJQ1JGFDXQqx3mHyR8DWQ@mail.gmail.com>
 <CAFeL3qEgaLqQDBMUp6+Q5arFi1VQjr=AhXBQVs5Q7pWc-n_-mQ@mail.gmail.com>
 <CA+RQFfdedebFG0+DFuqmY1_FCMo8_6eJHJemc-hBPL7zVsUd7A@mail.gmail.com>
 <CAN0FtzN+g8y78wvOe9TOMPU-BJhU7kOR+SEUhULM7ndqbmQofg@mail.gmail.com>
 <CAFeL3qE=xp2EGYQXibAs0kh8rGXjup+YTaVnsyS=977EmzYZpQ@mail.gmail.com>
Message-ID: <CAN0FtzM=4t_q=abBQrfQODsHAtcSotN-1DFsfq9584S8wFmSZQ@mail.gmail.com>

Oh sure, I see now what you mean.

Back then when I was thinking about this subject it seemed to me that soft
assertions could be something implemented in pytest core itself using the
assertion rewriting module (which in turn would put the assertion calls
around the context manager), along the lines of what Bruno mentioned.
Except that I probably would not go for a generic hook, but just the soft
assertion feature itself.


On Fri, Mar 27, 2020, 5:09 PM Maximilian Roos <m at maximilianroos.com> wrote:

> Hi Victor,
>
> > What about pytest-assume as a context manager around the assert line?
>
> Yes, this could work with either a context manager or a function like
> pytest-check uses.
> But it couples the plugin to the tests; it's no longer possible to run the
> plugin on normal tests with a plain `assert`, which is some of the
> brilliant philosophy of pytest.
>
> Without such a hook, I think the function or context manager is the best
> path forward, and is a reasonable way to build a better prototype before
> adding hooks deep in pytest internals.
>
> Thank you!
> Max
>
> On Fri, 27 Mar 2020 at 09:26, Victor Maryama <victor.maryama at gmail.com>
> wrote:
>
>> What about pytest-assume as a context manager around the assert line?
>> That way you get the soft assertions feature and pytest still rewrites
>> the assertions.
>>
>> On Fri, Mar 27, 2020, 12:47 PM Bruno Oliveira <nicoddemus at gmail.com>
>> wrote:
>>
>>> Hi Maximilian,
>>>
>>> On Thu, Mar 26, 2020 at 7:29 PM Maximilian Roos <m at maximilianroos.com>
>>> wrote:
>>>
>>>>
>>>> To prefix: as a long time user and evangelizer of pytest, a big thank
>>>> you for the superb tool.
>>>>
>>>
>>> Thanks for the kind words, we appreciate it.
>>>
>>>
>>>> As per that README, it only works on the first failure, because the
>>>> test doesn't continue execution beyond that. *Is there any way of
>>>> allowing execution to continue, without ripping up the internals of pytest?*
>>>> My prior is "no", since the assertion rewrite still retains an assertion,
>>>> and there's no hook for changing that.
>>>>
>>>
>>> Not at the moment I'm afraid.
>>>
>>> I think it should be possible to implement a hook that transforms the
>>> AST, which our rewriter would then call. I think, with this hook in place,
>>> you would be able to rewrite assert statements into a function call of your
>>> plugin, which would then be free to do whatever it wanted. If you are
>>> interested, I suggest writing up a proposal in the issue tracker so it can
>>> be discussed.
>>>
>>> Cheers,
>>> Bruno
>>>
>>>
>>>> Ref: a similar question I asked @okken
>>>> https://github.com/okken/pytest-check/issues/32
>>>>
>>>> Thank you,
>>>> Max
>>>> _______________________________________________
>>>> 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/20200327/a64c3b9b/attachment.html>

From m at maximilianroos.com  Fri Mar 27 12:28:03 2020
From: m at maximilianroos.com (Maximilian Roos)
Date: Fri, 27 Mar 2020 12:28:03 -0400
Subject: [pytest-dev] Fwd: Continuing on failures
In-Reply-To: <CAN0FtzM=4t_q=abBQrfQODsHAtcSotN-1DFsfq9584S8wFmSZQ@mail.gmail.com>
References: <CAFeL3qFb_bU7oyw3o6vtvqR_5Nr+aVJQ1JGFDXQqx3mHyR8DWQ@mail.gmail.com>
 <CAFeL3qEgaLqQDBMUp6+Q5arFi1VQjr=AhXBQVs5Q7pWc-n_-mQ@mail.gmail.com>
 <CA+RQFfdedebFG0+DFuqmY1_FCMo8_6eJHJemc-hBPL7zVsUd7A@mail.gmail.com>
 <CAN0FtzN+g8y78wvOe9TOMPU-BJhU7kOR+SEUhULM7ndqbmQofg@mail.gmail.com>
 <CAFeL3qE=xp2EGYQXibAs0kh8rGXjup+YTaVnsyS=977EmzYZpQ@mail.gmail.com>
 <CAN0FtzM=4t_q=abBQrfQODsHAtcSotN-1DFsfq9584S8wFmSZQ@mail.gmail.com>
Message-ID: <CAFeL3qHA3WMvYnHVbCk0JigT1pJ9q+qCrGFEtRHWo_eHgZXPCg@mail.gmail.com>

Yes exactly, we're aligned. Thanks Victor.

On Fri, 27 Mar 2020 at 12:19, Victor Maryama <victor.maryama at gmail.com>
wrote:

> Oh sure, I see now what you mean.
>
> Back then when I was thinking about this subject it seemed to me that soft
> assertions could be something implemented in pytest core itself using the
> assertion rewriting module (which in turn would put the assertion calls
> around the context manager), along the lines of what Bruno mentioned.
> Except that I probably would not go for a generic hook, but just the soft
> assertion feature itself.
>
>
> On Fri, Mar 27, 2020, 5:09 PM Maximilian Roos <m at maximilianroos.com>
> wrote:
>
>> Hi Victor,
>>
>> > What about pytest-assume as a context manager around the assert line?
>>
>> Yes, this could work with either a context manager or a function like
>> pytest-check uses.
>> But it couples the plugin to the tests; it's no longer possible to run
>> the plugin on normal tests with a plain `assert`, which is some of the
>> brilliant philosophy of pytest.
>>
>> Without such a hook, I think the function or context manager is the best
>> path forward, and is a reasonable way to build a better prototype before
>> adding hooks deep in pytest internals.
>>
>> Thank you!
>> Max
>>
>> On Fri, 27 Mar 2020 at 09:26, Victor Maryama <victor.maryama at gmail.com>
>> wrote:
>>
>>> What about pytest-assume as a context manager around the assert line?
>>> That way you get the soft assertions feature and pytest still rewrites
>>> the assertions.
>>>
>>> On Fri, Mar 27, 2020, 12:47 PM Bruno Oliveira <nicoddemus at gmail.com>
>>> wrote:
>>>
>>>> Hi Maximilian,
>>>>
>>>> On Thu, Mar 26, 2020 at 7:29 PM Maximilian Roos <m at maximilianroos.com>
>>>> wrote:
>>>>
>>>>>
>>>>> To prefix: as a long time user and evangelizer of pytest, a big thank
>>>>> you for the superb tool.
>>>>>
>>>>
>>>> Thanks for the kind words, we appreciate it.
>>>>
>>>>
>>>>> As per that README, it only works on the first failure, because the
>>>>> test doesn't continue execution beyond that. *Is there any way of
>>>>> allowing execution to continue, without ripping up the internals of pytest?*
>>>>> My prior is "no", since the assertion rewrite still retains an assertion,
>>>>> and there's no hook for changing that.
>>>>>
>>>>
>>>> Not at the moment I'm afraid.
>>>>
>>>> I think it should be possible to implement a hook that transforms the
>>>> AST, which our rewriter would then call. I think, with this hook in place,
>>>> you would be able to rewrite assert statements into a function call of your
>>>> plugin, which would then be free to do whatever it wanted. If you are
>>>> interested, I suggest writing up a proposal in the issue tracker so it can
>>>> be discussed.
>>>>
>>>> Cheers,
>>>> Bruno
>>>>
>>>>
>>>>> Ref: a similar question I asked @okken
>>>>> https://github.com/okken/pytest-check/issues/32
>>>>>
>>>>> Thank you,
>>>>> Max
>>>>> _______________________________________________
>>>>> 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/20200327/409db9f0/attachment-0001.html>

From variedthoughts at gmail.com  Fri Mar 27 12:30:49 2020
From: variedthoughts at gmail.com (Brian Okken)
Date: Fri, 27 Mar 2020 09:30:49 -0700
Subject: [pytest-dev] Fwd: Continuing on failures
In-Reply-To: <CAN0FtzM=4t_q=abBQrfQODsHAtcSotN-1DFsfq9584S8wFmSZQ@mail.gmail.com>
References: <CAFeL3qFb_bU7oyw3o6vtvqR_5Nr+aVJQ1JGFDXQqx3mHyR8DWQ@mail.gmail.com>
 <CAFeL3qEgaLqQDBMUp6+Q5arFi1VQjr=AhXBQVs5Q7pWc-n_-mQ@mail.gmail.com>
 <CA+RQFfdedebFG0+DFuqmY1_FCMo8_6eJHJemc-hBPL7zVsUd7A@mail.gmail.com>
 <CAN0FtzN+g8y78wvOe9TOMPU-BJhU7kOR+SEUhULM7ndqbmQofg@mail.gmail.com>
 <CAFeL3qE=xp2EGYQXibAs0kh8rGXjup+YTaVnsyS=977EmzYZpQ@mail.gmail.com>
 <CAN0FtzM=4t_q=abBQrfQODsHAtcSotN-1DFsfq9584S8wFmSZQ@mail.gmail.com>
Message-ID: <CAHsuHJ2h4+=yrKEyExkbx8J==hgvO=rc5XCPSfgbkwpPUmACGg@mail.gmail.com>

Victor,

This would be brilliant. There is a fairly large need for a soft assert
feature.
pytest-check would not be needed if it existed.

I personally would not want it to be an overriding of assert, but perhaps a
different function that is used almost identically to assert, including
failing the test, but just not stopping execution.
This is also the reason why many people resort to subtest.

-Brian Okken

On Fri, Mar 27, 2020 at 9:19 AM Victor Maryama <victor.maryama at gmail.com>
wrote:

> Oh sure, I see now what you mean.
>
> Back then when I was thinking about this subject it seemed to me that soft
> assertions could be something implemented in pytest core itself using the
> assertion rewriting module (which in turn would put the assertion calls
> around the context manager), along the lines of what Bruno mentioned.
> Except that I probably would not go for a generic hook, but just the soft
> assertion feature itself.
>
>
> On Fri, Mar 27, 2020, 5:09 PM Maximilian Roos <m at maximilianroos.com>
> wrote:
>
>> Hi Victor,
>>
>> > What about pytest-assume as a context manager around the assert line?
>>
>> Yes, this could work with either a context manager or a function like
>> pytest-check uses.
>> But it couples the plugin to the tests; it's no longer possible to run
>> the plugin on normal tests with a plain `assert`, which is some of the
>> brilliant philosophy of pytest.
>>
>> Without such a hook, I think the function or context manager is the best
>> path forward, and is a reasonable way to build a better prototype before
>> adding hooks deep in pytest internals.
>>
>> Thank you!
>> Max
>>
>> On Fri, 27 Mar 2020 at 09:26, Victor Maryama <victor.maryama at gmail.com>
>> wrote:
>>
>>> What about pytest-assume as a context manager around the assert line?
>>> That way you get the soft assertions feature and pytest still rewrites
>>> the assertions.
>>>
>>> On Fri, Mar 27, 2020, 12:47 PM Bruno Oliveira <nicoddemus at gmail.com>
>>> wrote:
>>>
>>>> Hi Maximilian,
>>>>
>>>> On Thu, Mar 26, 2020 at 7:29 PM Maximilian Roos <m at maximilianroos.com>
>>>> wrote:
>>>>
>>>>>
>>>>> To prefix: as a long time user and evangelizer of pytest, a big thank
>>>>> you for the superb tool.
>>>>>
>>>>
>>>> Thanks for the kind words, we appreciate it.
>>>>
>>>>
>>>>> As per that README, it only works on the first failure, because the
>>>>> test doesn't continue execution beyond that. *Is there any way of
>>>>> allowing execution to continue, without ripping up the internals of pytest?*
>>>>> My prior is "no", since the assertion rewrite still retains an assertion,
>>>>> and there's no hook for changing that.
>>>>>
>>>>
>>>> Not at the moment I'm afraid.
>>>>
>>>> I think it should be possible to implement a hook that transforms the
>>>> AST, which our rewriter would then call. I think, with this hook in place,
>>>> you would be able to rewrite assert statements into a function call of your
>>>> plugin, which would then be free to do whatever it wanted. If you are
>>>> interested, I suggest writing up a proposal in the issue tracker so it can
>>>> be discussed.
>>>>
>>>> Cheers,
>>>> Bruno
>>>>
>>>>
>>>>> Ref: a similar question I asked @okken
>>>>> https://github.com/okken/pytest-check/issues/32
>>>>>
>>>>> Thank you,
>>>>> Max
>>>>> _______________________________________________
>>>>> pytest-dev mailing list
>>>>> pytest-dev at python.org
>>>>> https://mail.python.org/mailman/listinfo/pytest-dev
>>>>>
>>>> _______________________________________________
>>>> pytest-dev mailing list
>>>> pytest-dev at python.org
>>>> https://mail.python.org/mailman/listinfo/pytest-dev
>>>>
>>>> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20200327/e99085b0/attachment.html>

From variedthoughts at gmail.com  Fri Mar 27 12:32:53 2020
From: variedthoughts at gmail.com (Brian Okken)
Date: Fri, 27 Mar 2020 09:32:53 -0700
Subject: [pytest-dev] Fwd: Continuing on failures
In-Reply-To: <CAHsuHJ2h4+=yrKEyExkbx8J==hgvO=rc5XCPSfgbkwpPUmACGg@mail.gmail.com>
References: <CAFeL3qFb_bU7oyw3o6vtvqR_5Nr+aVJQ1JGFDXQqx3mHyR8DWQ@mail.gmail.com>
 <CAFeL3qEgaLqQDBMUp6+Q5arFi1VQjr=AhXBQVs5Q7pWc-n_-mQ@mail.gmail.com>
 <CA+RQFfdedebFG0+DFuqmY1_FCMo8_6eJHJemc-hBPL7zVsUd7A@mail.gmail.com>
 <CAN0FtzN+g8y78wvOe9TOMPU-BJhU7kOR+SEUhULM7ndqbmQofg@mail.gmail.com>
 <CAFeL3qE=xp2EGYQXibAs0kh8rGXjup+YTaVnsyS=977EmzYZpQ@mail.gmail.com>
 <CAN0FtzM=4t_q=abBQrfQODsHAtcSotN-1DFsfq9584S8wFmSZQ@mail.gmail.com>
 <CAHsuHJ2h4+=yrKEyExkbx8J==hgvO=rc5XCPSfgbkwpPUmACGg@mail.gmail.com>
Message-ID: <CAHsuHJ3CN6tDsTKvUoAkZOK_pNS6q+qDWQGVU+hoJ3HS++2--g@mail.gmail.com>

I'd even be more than ok with a context manager approach and even using
asserts within the context manager.
As long as you can have more than one assert fail within the context.
-Brian

On Fri, Mar 27, 2020 at 9:30 AM Brian Okken <variedthoughts at gmail.com>
wrote:

> Victor,
>
> This would be brilliant. There is a fairly large need for a soft assert
> feature.
> pytest-check would not be needed if it existed.
>
> I personally would not want it to be an overriding of assert, but perhaps
> a different function that is used almost identically to assert, including
> failing the test, but just not stopping execution.
> This is also the reason why many people resort to subtest.
>
> -Brian Okken
>
> On Fri, Mar 27, 2020 at 9:19 AM Victor Maryama <victor.maryama at gmail.com>
> wrote:
>
>> Oh sure, I see now what you mean.
>>
>> Back then when I was thinking about this subject it seemed to me that
>> soft assertions could be something implemented in pytest core itself using
>> the assertion rewriting module (which in turn would put the assertion calls
>> around the context manager), along the lines of what Bruno mentioned.
>> Except that I probably would not go for a generic hook, but just the soft
>> assertion feature itself.
>>
>>
>> On Fri, Mar 27, 2020, 5:09 PM Maximilian Roos <m at maximilianroos.com>
>> wrote:
>>
>>> Hi Victor,
>>>
>>> > What about pytest-assume as a context manager around the assert line?
>>>
>>> Yes, this could work with either a context manager or a function like
>>> pytest-check uses.
>>> But it couples the plugin to the tests; it's no longer possible to run
>>> the plugin on normal tests with a plain `assert`, which is some of the
>>> brilliant philosophy of pytest.
>>>
>>> Without such a hook, I think the function or context manager is the best
>>> path forward, and is a reasonable way to build a better prototype before
>>> adding hooks deep in pytest internals.
>>>
>>> Thank you!
>>> Max
>>>
>>> On Fri, 27 Mar 2020 at 09:26, Victor Maryama <victor.maryama at gmail.com>
>>> wrote:
>>>
>>>> What about pytest-assume as a context manager around the assert line?
>>>> That way you get the soft assertions feature and pytest still rewrites
>>>> the assertions.
>>>>
>>>> On Fri, Mar 27, 2020, 12:47 PM Bruno Oliveira <nicoddemus at gmail.com>
>>>> wrote:
>>>>
>>>>> Hi Maximilian,
>>>>>
>>>>> On Thu, Mar 26, 2020 at 7:29 PM Maximilian Roos <m at maximilianroos.com>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> To prefix: as a long time user and evangelizer of pytest, a big thank
>>>>>> you for the superb tool.
>>>>>>
>>>>>
>>>>> Thanks for the kind words, we appreciate it.
>>>>>
>>>>>
>>>>>> As per that README, it only works on the first failure, because the
>>>>>> test doesn't continue execution beyond that. *Is there any way of
>>>>>> allowing execution to continue, without ripping up the internals of pytest?*
>>>>>> My prior is "no", since the assertion rewrite still retains an assertion,
>>>>>> and there's no hook for changing that.
>>>>>>
>>>>>
>>>>> Not at the moment I'm afraid.
>>>>>
>>>>> I think it should be possible to implement a hook that transforms the
>>>>> AST, which our rewriter would then call. I think, with this hook in place,
>>>>> you would be able to rewrite assert statements into a function call of your
>>>>> plugin, which would then be free to do whatever it wanted. If you are
>>>>> interested, I suggest writing up a proposal in the issue tracker so it can
>>>>> be discussed.
>>>>>
>>>>> Cheers,
>>>>> Bruno
>>>>>
>>>>>
>>>>>> Ref: a similar question I asked @okken
>>>>>> https://github.com/okken/pytest-check/issues/32
>>>>>>
>>>>>> Thank you,
>>>>>> Max
>>>>>> _______________________________________________
>>>>>> pytest-dev mailing list
>>>>>> pytest-dev at python.org
>>>>>> https://mail.python.org/mailman/listinfo/pytest-dev
>>>>>>
>>>>> _______________________________________________
>>>>> pytest-dev mailing list
>>>>> pytest-dev at python.org
>>>>> https://mail.python.org/mailman/listinfo/pytest-dev
>>>>>
>>>>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20200327/9aa64a3e/attachment-0001.html>

From cito at online.de  Fri Mar 27 14:38:46 2020
From: cito at online.de (Christoph Zwerschke)
Date: Fri, 27 Mar 2020 19:38:46 +0100
Subject: [pytest-dev] Grouping tests
Message-ID: <0104ca73-424a-a040-920e-156590225325@online.de>

Hi all, I hope this is the right place to ask the following.

I am currently using https://github.com/ropez/pytest-describe to group 
tests in a large test suite because it looks nicer than using classes 
and looks more like the tests in the JavaScript library that I am 
recreating in Python. Also, when using classes, tests methods will need 
an additional "self". And I'm not sure whether they can be nested.

Unfortunately, pytest-describe has gotten rusty, and there are  issues 
(e.g. https://github.com/ropez/pytest-describe/issues/26) which need 
help by some pytest experts.

Is someone here interested in working on this and keeping 
pytest-describe alive and compatible with newer pytest versions?

Otherwise, any alternative suggestions for grouping tests nicely?

-- Christoph