From flub at devork.be  Thu Dec  8 08:17:52 2022
From: flub at devork.be (Floris Bruynooghe)
Date: Thu, 08 Dec 2022 14:17:52 +0100
Subject: [pytest-dev] github compromised account on organisation
Message-ID: <87o7seavb3.fsf@fredriksen.zt.devork.be>

Hi folks,

Github recently sent an email warning of a member of the pytest-dev org
(I'm purposefully not adding identifiable information here) likely
having a compromised API token that may have been abused.  The member in
question only has read access to all but one plugin repository so the
impact is limited.

Nevertheless we should probably contact them to ask for them to make
sure they revoke all API tokens, replace them with more limited-scopes
ones if possible and audit the plugin.  If they can't do this or don't
respond I guess we should (temporarily) restrict their access to the
plugin as well.

I'm happy to contact them, but also didn't do so yet just in case
multiple folks jump on this.  Probably one is enough.

Cheers,
Floris

From nicoddemus at gmail.com  Thu Dec  8 09:23:27 2022
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 8 Dec 2022 11:23:27 -0300
Subject: [pytest-dev] github compromised account on organisation
In-Reply-To: <87o7seavb3.fsf@fredriksen.zt.devork.be>
References: <87o7seavb3.fsf@fredriksen.zt.devork.be>
Message-ID: <CA+RQFfenzu5OwfyTjbmOFnqGGjO1Pb_y3_TcxkAOAAZTUpSCvg@mail.gmail.com>

Thanks Floris.

Yes, please go ahead and contact the user.

I've posted a thread about this for the Core team in the pytest-dev
Discussions, just for reference:

https://github.com/orgs/pytest-dev/teams/core/discussions/23

Cheers,
Bruno.

On Thu, Dec 8, 2022 at 10:18 AM Floris Bruynooghe <flub at devork.be> wrote:

> Hi folks,
>
> Github recently sent an email warning of a member of the pytest-dev org
> (I'm purposefully not adding identifiable information here) likely
> having a compromised API token that may have been abused.  The member in
> question only has read access to all but one plugin repository so the
> impact is limited.
>
> Nevertheless we should probably contact them to ask for them to make
> sure they revoke all API tokens, replace them with more limited-scopes
> ones if possible and audit the plugin.  If they can't do this or don't
> respond I guess we should (temporarily) restrict their access to the
> plugin as well.
>
> I'm happy to contact them, but also didn't do so yet just in case
> multiple folks jump on this.  Probably one is enough.
>
> Cheers,
> Floris
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pytest-dev/attachments/20221208/cd86ae24/attachment.html>

From nicoddemus at gmail.com  Thu Dec  8 11:17:04 2022
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 8 Dec 2022 13:17:04 -0300
Subject: [pytest-dev] Enabling 2FA for pytest-dev
Message-ID: <CA+RQFfezCRwreTY7BmB9VEkLDNvd2oHJDw5s=E3HpqM4zW8PPQ@mail.gmail.com>

Hi folks,

Given the recent incident of suspicious activity using a stolen credential
from a pytest-dev org member, it was suggested that pytest is high-enough
profile that we should require 2FA for all members.

I'm definitely +1 on this, sending this message here in case someone wants
to voice concerns.

Cheers,
Bruno.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pytest-dev/attachments/20221208/0a604d60/attachment.html>

From nicoddemus at gmail.com  Thu Dec  8 11:42:00 2022
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 8 Dec 2022 13:42:00 -0300
Subject: [pytest-dev] Enabling 2FA for pytest-dev
In-Reply-To: <CA+RQFfezCRwreTY7BmB9VEkLDNvd2oHJDw5s=E3HpqM4zW8PPQ@mail.gmail.com>
References: <CA+RQFfezCRwreTY7BmB9VEkLDNvd2oHJDw5s=E3HpqM4zW8PPQ@mail.gmail.com>
Message-ID: <CA+RQFfes316v4kPE4kbE2VLDHWbMyccn-=AxLE2CDr9+0S01rQ@mail.gmail.com>

Hi folks,

I intend to enable the requirement in a few hours, unless someone objects.

Cheers,
Bruno.

On Thu, Dec 8, 2022 at 1:17 PM Bruno Oliveira <nicoddemus at gmail.com> wrote:

> Hi folks,
>
> Given the recent incident of suspicious activity using a stolen credential
> from a pytest-dev org member, it was suggested that pytest is high-enough
> profile that we should require 2FA for all members.
>
> I'm definitely +1 on this, sending this message here in case someone wants
> to voice concerns.
>
> Cheers,
> Bruno.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pytest-dev/attachments/20221208/0922c7c9/attachment.html>

From flub at devork.be  Thu Dec  8 11:42:34 2022
From: flub at devork.be (Floris Bruynooghe)
Date: Thu, 08 Dec 2022 17:42:34 +0100
Subject: [pytest-dev] Enabling 2FA for pytest-dev
In-Reply-To: <CA+RQFfezCRwreTY7BmB9VEkLDNvd2oHJDw5s=E3HpqM4zW8PPQ@mail.gmail.com>
References: <CA+RQFfezCRwreTY7BmB9VEkLDNvd2oHJDw5s=E3HpqM4zW8PPQ@mail.gmail.com>
Message-ID: <87a63xc0ed.fsf@fredriksen.zt.devork.be>

I'd also be +1 on this.

Note however that the user in question did have 2FA enabled already and
indeed this doesn't help for compromised tokens.  I think we can force
some limits on what tokens are allowed, I'm not entirely sure here and
on how restricting this may turn out to be for people.

Anyway, requiring 2FA is a decent step I support.

Cheers,
Floris


On Thu 08 Dec 2022 at 13:17 -0300, Bruno Oliveira wrote:

> Hi folks,
>
> Given the recent incident of suspicious activity using a stolen credential
> from a pytest-dev org member, it was suggested that pytest is high-enough
> profile that we should require 2FA for all members.
>
> I'm definitely +1 on this, sending this message here in case someone wants
> to voice concerns.
>
> Cheers,
> Bruno.
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev

From oliver.schoenborn at gmail.com  Thu Dec  8 13:10:15 2022
From: oliver.schoenborn at gmail.com (oliver)
Date: Thu, 8 Dec 2022 13:10:15 -0500
Subject: [pytest-dev] Enabling 2FA for pytest-dev
In-Reply-To: <87a63xc0ed.fsf@fredriksen.zt.devork.be>
References: <CA+RQFfezCRwreTY7BmB9VEkLDNvd2oHJDw5s=E3HpqM4zW8PPQ@mail.gmail.com>
 <87a63xc0ed.fsf@fredriksen.zt.devork.be>
Message-ID: <CAMb+DaU2pDwzFPd7TEaUXeWm-CbZJRvXLP-xSPby2aX7F7sqPw@mail.gmail.com>

Makes sense to me.

On Thu, Dec 8, 2022 at 11:42 AM Floris Bruynooghe <flub at devork.be> wrote:

> I'd also be +1 on this.
>
> Note however that the user in question did have 2FA enabled already and
> indeed this doesn't help for compromised tokens.  I think we can force
> some limits on what tokens are allowed, I'm not entirely sure here and
> on how restricting this may turn out to be for people.
>
> Anyway, requiring 2FA is a decent step I support.
>
> Cheers,
> Floris
>
>
> On Thu 08 Dec 2022 at 13:17 -0300, Bruno Oliveira wrote:
>
> > Hi folks,
> >
> > Given the recent incident of suspicious activity using a stolen
> credential
> > from a pytest-dev org member, it was suggested that pytest is high-enough
> > profile that we should require 2FA for all members.
> >
> > I'm definitely +1 on this, sending this message here in case someone
> wants
> > to voice concerns.
> >
> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pytest-dev/attachments/20221208/d1123aaa/attachment.html>

From nicoddemus at gmail.com  Fri Dec  9 07:11:15 2022
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Fri, 9 Dec 2022 09:11:15 -0300
Subject: [pytest-dev] Enabling 2FA for pytest-dev
In-Reply-To: <CAMb+DaU2pDwzFPd7TEaUXeWm-CbZJRvXLP-xSPby2aX7F7sqPw@mail.gmail.com>
References: <CA+RQFfezCRwreTY7BmB9VEkLDNvd2oHJDw5s=E3HpqM4zW8PPQ@mail.gmail.com>
 <87a63xc0ed.fsf@fredriksen.zt.devork.be>
 <CAMb+DaU2pDwzFPd7TEaUXeWm-CbZJRvXLP-xSPby2aX7F7sqPw@mail.gmail.com>
Message-ID: <CA+RQFfcp9DbiQLkNYJ52ADJfGOmQ0A-aN97w-dT6M-vY3f0vsw@mail.gmail.com>

Enabled!

This removed 41 users from the organization, including Holger!

GitHub will contact those users mentioning the reason, hopefully people
will enable 2FA and ask us to rejoin.

Cheers,
Bruno.

On Thu, Dec 8, 2022 at 3:10 PM oliver <oliver.schoenborn at gmail.com> wrote:

> Makes sense to me.
>
> On Thu, Dec 8, 2022 at 11:42 AM Floris Bruynooghe <flub at devork.be> wrote:
>
>> I'd also be +1 on this.
>>
>> Note however that the user in question did have 2FA enabled already and
>> indeed this doesn't help for compromised tokens.  I think we can force
>> some limits on what tokens are allowed, I'm not entirely sure here and
>> on how restricting this may turn out to be for people.
>>
>> Anyway, requiring 2FA is a decent step I support.
>>
>> Cheers,
>> Floris
>>
>>
>> On Thu 08 Dec 2022 at 13:17 -0300, Bruno Oliveira wrote:
>>
>> > Hi folks,
>> >
>> > Given the recent incident of suspicious activity using a stolen
>> credential
>> > from a pytest-dev org member, it was suggested that pytest is
>> high-enough
>> > profile that we should require 2FA for all members.
>> >
>> > I'm definitely +1 on this, sending this message here in case someone
>> wants
>> > to voice concerns.
>> >
>> > 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
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pytest-dev/attachments/20221209/95fe51fa/attachment.html>

From jeremy.retailleau at gmail.com  Fri Dec 16 15:02:25 2022
From: jeremy.retailleau at gmail.com (Jeremy Retailleau)
Date: Fri, 16 Dec 2022 12:02:25 -0800
Subject: [pytest-dev] Pytest config for CMake
Message-ID: <CAM3nR9yrOP4_QWAcV0h8Su0TnOAW-qKE3rkTeCr=7QTBviSdAA@mail.gmail.com>

Hi everyone,

As I often work on C++ projects with Python bindings, I noticed that
integrating Pytest within CMake was mostly done in hacky ways that were
frequently bound to a specific platform or context. So I attempted to
release a standard configuration that would work on most platforms and
provide additional useful features:
https://github.com/buddly27/pytest-cmake

I chose not to use pytest-cpp as my project is primarily written in C++ and
could provide bindings in multiple languages. Therefore providing a
pip-installable CMake config seemed like the best way to create a bridge
between these two ecosystems.

I am bringing this project to your attention for feedback and possible
collaboration to improve it if you are interested!


Jeremy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pytest-dev/attachments/20221216/6b5e24c4/attachment.html>

From nicoddemus at gmail.com  Thu Dec 29 05:38:41 2022
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 29 Dec 2022 07:38:41 -0300
Subject: [pytest-dev] Submitting pytest-inline plugin
In-Reply-To: <CAKvgn7rE2ko19vygrXqWfxQcRJiS6zeZtFhfkqUbdHWqFCL00g@mail.gmail.com>
References: <CAKvgn7rE2ko19vygrXqWfxQcRJiS6zeZtFhfkqUbdHWqFCL00g@mail.gmail.com>
Message-ID: <CA+RQFfftNhY5-nr2KKg4Wwfx-JqsGK8X5cinKpHYaCncdYqgDQ@mail.gmail.com>

Hi Yuki,

Sorry for the late reply, I think this notification slipped through the
cracks.

We need two +1 votes from members before we can continue with the transfer.

I'm +1, the plugin definitely looks interesting, we need just one more vote
then.

Cheers,
Bruno.

On Wed, Nov 23, 2022 at 3:15 PM Yu Liu (Yuki) <yuki.liu at utexas.edu> wrote:

> Dear pytest developers,
>
> We would like to submit our plugin ?pytest-inline? to pytest-dev
> organization. pytest-inline is a plugin to help developers write
> inline tests at statement level. Inline testing is a new granularity
> of testing that make it easier to check individual program statements.
> An inline test is a statement that allows to provide arbitrary inputs
> and test oracles for checking the immediately preceding statement that
> is not an inline test. We have a paper about inline tests:
> https://arxiv.org/abs/2209.06315.
>
> Our current repo is at
> https://github.com/EngineeringSoftware/pytest-inline. We have followed
> the guidelines to prepare the repo. We have also uploaded the plugin
> to PyPI. All of our contributors agreed to transfer the repo. Please
> let us know if you need any further information. Look forward to your
> feedback.
>
> Thanks,
> Yuki (with Alan, Milos, Owolabi, Pengyu, Zach)
> _______________________________________________
> 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: <https://mail.python.org/pipermail/pytest-dev/attachments/20221229/aaf77e9f/attachment.html>

From oliver.schoenborn at gmail.com  Thu Dec 29 07:55:57 2022
From: oliver.schoenborn at gmail.com (oliver)
Date: Thu, 29 Dec 2022 06:55:57 -0600
Subject: [pytest-dev] Submitting pytest-inline plugin
In-Reply-To: <CA+RQFfftNhY5-nr2KKg4Wwfx-JqsGK8X5cinKpHYaCncdYqgDQ@mail.gmail.com>
References: <CAKvgn7rE2ko19vygrXqWfxQcRJiS6zeZtFhfkqUbdHWqFCL00g@mail.gmail.com>
 <CA+RQFfftNhY5-nr2KKg4Wwfx-JqsGK8X5cinKpHYaCncdYqgDQ@mail.gmail.com>
Message-ID: <CAMb+DaXxf7uan310rbWwj4rUGcgFi1f9XL73+vfM=A0VhXP8gg@mail.gmail.com>

I had a look. Interesting idea for sure. A few things though :

- the github page should clarify that these tests are intended to go in the
actual source code, rather than in the test code. Also, whether the inline
tests are merely empty functions when not hit via pytest.
- the github page should mention some important aspect like the performance
hit as discussed in the article that the page links to, and further clarify
how this is achieved (because for me, performance was one of my 2 primany
concerns). I'm a little skeptical that it is that low because function
calls in Python are relatively expensive.... but I'm happy to be proven
wrong. Eg should one be aware that the hit of the article is per test
line.... so putting an inline test in a small loop could result in a
measurable hit, etc?
- the top-level api, ie `Here()`, needs to be renamed to clarify to
would-be readers of the source code that this is inline test code that is
not run when not reached via pytest. Eg I recommend `itest`, short, easy to
write, explicit.

Cheers,
Oliver

On Thu., Dec. 29, 2022, 4:39 a.m. Bruno Oliveira, <nicoddemus at gmail.com>
wrote:

> Hi Yuki,
>
> Sorry for the late reply, I think this notification slipped through the
> cracks.
>
> We need two +1 votes from members before we can continue with the transfer.
>
> I'm +1, the plugin definitely looks interesting, we need just one more
> vote then.
>
> Cheers,
> Bruno.
>
> On Wed, Nov 23, 2022 at 3:15 PM Yu Liu (Yuki) <yuki.liu at utexas.edu> wrote:
>
>> Dear pytest developers,
>>
>> We would like to submit our plugin ?pytest-inline? to pytest-dev
>> organization. pytest-inline is a plugin to help developers write
>> inline tests at statement level. Inline testing is a new granularity
>> of testing that make it easier to check individual program statements.
>> An inline test is a statement that allows to provide arbitrary inputs
>> and test oracles for checking the immediately preceding statement that
>> is not an inline test. We have a paper about inline tests:
>> https://arxiv.org/abs/2209.06315.
>>
>> Our current repo is at
>> https://github.com/EngineeringSoftware/pytest-inline. We have followed
>> the guidelines to prepare the repo. We have also uploaded the plugin
>> to PyPI. All of our contributors agreed to transfer the repo. Please
>> let us know if you need any further information. Look forward to your
>> feedback.
>>
>> Thanks,
>> Yuki (with Alan, Milos, Owolabi, Pengyu, Zach)
>> _______________________________________________
>> 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: <https://mail.python.org/pipermail/pytest-dev/attachments/20221229/f62ce372/attachment.html>

From flub at devork.be  Thu Dec 29 15:56:49 2022
From: flub at devork.be (Floris Bruynooghe)
Date: Thu, 29 Dec 2022 21:56:49 +0100
Subject: [pytest-dev] Submitting pytest-inline plugin
In-Reply-To: <CAMb+DaXxf7uan310rbWwj4rUGcgFi1f9XL73+vfM=A0VhXP8gg@mail.gmail.com>
References: <CAKvgn7rE2ko19vygrXqWfxQcRJiS6zeZtFhfkqUbdHWqFCL00g@mail.gmail.com>
 <CA+RQFfftNhY5-nr2KKg4Wwfx-JqsGK8X5cinKpHYaCncdYqgDQ@mail.gmail.com>
 <CAMb+DaXxf7uan310rbWwj4rUGcgFi1f9XL73+vfM=A0VhXP8gg@mail.gmail.com>
Message-ID: <87cz82x71q.fsf@devork.be>

Hello,

I'm happy to +1 as well, seems nothing wrong from a plugin acceptance
perspective.  IIRC we're not vetting the plugins, merely allowing them
to be taken over if the bus factor becomes fatally low.

Not that I'm saying the feedback isn't useful either though, maybe file
it as an issue on the repo? (wait, do they get transferred by github as
well?)

Cheers,
Floris


On Thu 29 Dec 2022 at 06:55 -0600, oliver wrote:

> I had a look. Interesting idea for sure. A few things though :
>
> - the github page should clarify that these tests are intended to go in the
> actual source code, rather than in the test code. Also, whether the inline
> tests are merely empty functions when not hit via pytest.
> - the github page should mention some important aspect like the performance
> hit as discussed in the article that the page links to, and further clarify
> how this is achieved (because for me, performance was one of my 2 primany
> concerns). I'm a little skeptical that it is that low because function
> calls in Python are relatively expensive.... but I'm happy to be proven
> wrong. Eg should one be aware that the hit of the article is per test
> line.... so putting an inline test in a small loop could result in a
> measurable hit, etc?
> - the top-level api, ie `Here()`, needs to be renamed to clarify to
> would-be readers of the source code that this is inline test code that is
> not run when not reached via pytest. Eg I recommend `itest`, short, easy to
> write, explicit.
>
> Cheers,
> Oliver
>
> On Thu., Dec. 29, 2022, 4:39 a.m. Bruno Oliveira, <nicoddemus at gmail.com>
> wrote:
>
>> Hi Yuki,
>>
>> Sorry for the late reply, I think this notification slipped through the
>> cracks.
>>
>> We need two +1 votes from members before we can continue with the transfer.
>>
>> I'm +1, the plugin definitely looks interesting, we need just one more
>> vote then.
>>
>> Cheers,
>> Bruno.
>>
>> On Wed, Nov 23, 2022 at 3:15 PM Yu Liu (Yuki) <yuki.liu at utexas.edu> wrote:
>>
>>> Dear pytest developers,
>>>
>>> We would like to submit our plugin ?pytest-inline? to pytest-dev
>>> organization. pytest-inline is a plugin to help developers write
>>> inline tests at statement level. Inline testing is a new granularity
>>> of testing that make it easier to check individual program statements.
>>> An inline test is a statement that allows to provide arbitrary inputs
>>> and test oracles for checking the immediately preceding statement that
>>> is not an inline test. We have a paper about inline tests:
>>> https://arxiv.org/abs/2209.06315.
>>>
>>> Our current repo is at
>>> https://github.com/EngineeringSoftware/pytest-inline. We have followed
>>> the guidelines to prepare the repo. We have also uploaded the plugin
>>> to PyPI. All of our contributors agreed to transfer the repo. Please
>>> let us know if you need any further information. Look forward to your
>>> feedback.
>>>
>>> Thanks,
>>> Yuki (with Alan, Milos, Owolabi, Pengyu, Zach)
>>> _______________________________________________
>>> 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

From nicoddemus at gmail.com  Thu Dec 29 16:46:16 2022
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Thu, 29 Dec 2022 18:46:16 -0300
Subject: [pytest-dev] Submitting pytest-inline plugin
In-Reply-To: <87cz82x71q.fsf@devork.be>
References: <CAKvgn7rE2ko19vygrXqWfxQcRJiS6zeZtFhfkqUbdHWqFCL00g@mail.gmail.com>
 <CA+RQFfftNhY5-nr2KKg4Wwfx-JqsGK8X5cinKpHYaCncdYqgDQ@mail.gmail.com>
 <CAMb+DaXxf7uan310rbWwj4rUGcgFi1f9XL73+vfM=A0VhXP8gg@mail.gmail.com>
 <87cz82x71q.fsf@devork.be>
Message-ID: <CA+RQFfe+8GMs67KTjnN5zojmaw+QJX5LfQe+Pn+A5EhrXd+Zrw@mail.gmail.com>

On Thu, Dec 29, 2022 at 5:56 PM Floris Bruynooghe <flub at devork.be> wrote:

> I'm happy to +1 as well, seems nothing wrong from a plugin acceptance
> perspective.  IIRC we're not vetting the plugins, merely allowing them
> to be taken over if the bus factor becomes fatally low.
>

That was my understanding as well, the feedback is definitely nice, however
so far we never blocked any transfer due to requests/feedback like that
(not even sure that Oliver meant it in that manner anyway).

Not that I'm saying the feedback isn't useful either though, maybe file
> it as an issue on the repo? (wait, do they get transferred by github as
> well?)
>

Yes, everything is transferred accordingly.

If nobody objects by tomorrow, Yuki, could you please transfer the
repository to me, as well as send me the GitHub names that should become
admin of the repository once it is part of pytest-dev? Thanks.

Cheers,
Bruno.


> Cheers,
> Floris
>
>
> On Thu 29 Dec 2022 at 06:55 -0600, oliver wrote:
>
> > I had a look. Interesting idea for sure. A few things though :
> >
> > - the github page should clarify that these tests are intended to go in
> the
> > actual source code, rather than in the test code. Also, whether the
> inline
> > tests are merely empty functions when not hit via pytest.
> > - the github page should mention some important aspect like the
> performance
> > hit as discussed in the article that the page links to, and further
> clarify
> > how this is achieved (because for me, performance was one of my 2 primany
> > concerns). I'm a little skeptical that it is that low because function
> > calls in Python are relatively expensive.... but I'm happy to be proven
> > wrong. Eg should one be aware that the hit of the article is per test
> > line.... so putting an inline test in a small loop could result in a
> > measurable hit, etc?
> > - the top-level api, ie `Here()`, needs to be renamed to clarify to
> > would-be readers of the source code that this is inline test code that is
> > not run when not reached via pytest. Eg I recommend `itest`, short, easy
> to
> > write, explicit.
> >
> > Cheers,
> > Oliver
> >
> > On Thu., Dec. 29, 2022, 4:39 a.m. Bruno Oliveira, <nicoddemus at gmail.com>
> > wrote:
> >
> >> Hi Yuki,
> >>
> >> Sorry for the late reply, I think this notification slipped through the
> >> cracks.
> >>
> >> We need two +1 votes from members before we can continue with the
> transfer.
> >>
> >> I'm +1, the plugin definitely looks interesting, we need just one more
> >> vote then.
> >>
> >> Cheers,
> >> Bruno.
> >>
> >> On Wed, Nov 23, 2022 at 3:15 PM Yu Liu (Yuki) <yuki.liu at utexas.edu>
> wrote:
> >>
> >>> Dear pytest developers,
> >>>
> >>> We would like to submit our plugin ?pytest-inline? to pytest-dev
> >>> organization. pytest-inline is a plugin to help developers write
> >>> inline tests at statement level. Inline testing is a new granularity
> >>> of testing that make it easier to check individual program statements.
> >>> An inline test is a statement that allows to provide arbitrary inputs
> >>> and test oracles for checking the immediately preceding statement that
> >>> is not an inline test. We have a paper about inline tests:
> >>> https://arxiv.org/abs/2209.06315.
> >>>
> >>> Our current repo is at
> >>> https://github.com/EngineeringSoftware/pytest-inline. We have followed
> >>> the guidelines to prepare the repo. We have also uploaded the plugin
> >>> to PyPI. All of our contributors agreed to transfer the repo. Please
> >>> let us know if you need any further information. Look forward to your
> >>> feedback.
> >>>
> >>> Thanks,
> >>> Yuki (with Alan, Milos, Owolabi, Pengyu, Zach)
> >>> _______________________________________________
> >>> 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: <https://mail.python.org/pipermail/pytest-dev/attachments/20221229/fd824647/attachment.html>

From yuki.liu at utexas.edu  Fri Dec 30 10:52:57 2022
From: yuki.liu at utexas.edu (Yu Liu (Yuki))
Date: Fri, 30 Dec 2022 09:52:57 -0600
Subject: [pytest-dev] Submitting pytest-inline plugin
In-Reply-To: <CA+RQFfe+8GMs67KTjnN5zojmaw+QJX5LfQe+Pn+A5EhrXd+Zrw@mail.gmail.com>
References: <CAKvgn7rE2ko19vygrXqWfxQcRJiS6zeZtFhfkqUbdHWqFCL00g@mail.gmail.com>
 <CA+RQFfftNhY5-nr2KKg4Wwfx-JqsGK8X5cinKpHYaCncdYqgDQ@mail.gmail.com>
 <CAMb+DaXxf7uan310rbWwj4rUGcgFi1f9XL73+vfM=A0VhXP8gg@mail.gmail.com>
 <87cz82x71q.fsf@devork.be>
 <CA+RQFfe+8GMs67KTjnN5zojmaw+QJX5LfQe+Pn+A5EhrXd+Zrw@mail.gmail.com>
Message-ID: <CAKvgn7pkVTB5DbR6mnW=uDHAc5YPDNC9GDFdL-NY7v0aTm_yFw@mail.gmail.com>

Hi Bruno, Oliver, Floris,

Thank you for the feedback! We have updated the README in our repo. We
will also update the API from Here to itest, which may take some more
time.

If nobody objects by tomorrow, Yuki, could you please transfer the
> repository to me, as well as send me the GitHub names that should
> become admin of the repository once it is part of pytest-dev? Thanks.


Sounds good! I will transfer the repo to you later today. We would like
to add the following admins: sweetStreet, pengyunie, gliga, and
owolabileg.

Thanks,
Yuki

On Thu, Dec 29, 2022 at 3:46 PM Bruno Oliveira <nicoddemus at gmail.com> wrote:

>
>
> On Thu, Dec 29, 2022 at 5:56 PM Floris Bruynooghe <flub at devork.be> wrote:
>
>> I'm happy to +1 as well, seems nothing wrong from a plugin acceptance
>> perspective.  IIRC we're not vetting the plugins, merely allowing them
>> to be taken over if the bus factor becomes fatally low.
>>
>
> That was my understanding as well, the feedback is definitely
> nice, however so far we never blocked any transfer due to requests/feedback
> like that (not even sure that Oliver meant it in that manner anyway).
>
> Not that I'm saying the feedback isn't useful either though, maybe file
>> it as an issue on the repo? (wait, do they get transferred by github as
>> well?)
>>
>
> Yes, everything is transferred accordingly.
>
> If nobody objects by tomorrow, Yuki, could you please transfer the
> repository to me, as well as send me the GitHub names that should become
> admin of the repository once it is part of pytest-dev? Thanks.
>
> Cheers,
> Bruno.
>
>
>> Cheers,
>> Floris
>>
>>
>> On Thu 29 Dec 2022 at 06:55 -0600, oliver wrote:
>>
>> > I had a look. Interesting idea for sure. A few things though :
>> >
>> > - the github page should clarify that these tests are intended to go in
>> the
>> > actual source code, rather than in the test code. Also, whether the
>> inline
>> > tests are merely empty functions when not hit via pytest.
>> > - the github page should mention some important aspect like the
>> performance
>> > hit as discussed in the article that the page links to, and further
>> clarify
>> > how this is achieved (because for me, performance was one of my 2
>> primany
>> > concerns). I'm a little skeptical that it is that low because function
>> > calls in Python are relatively expensive.... but I'm happy to be proven
>> > wrong. Eg should one be aware that the hit of the article is per test
>> > line.... so putting an inline test in a small loop could result in a
>> > measurable hit, etc?
>> > - the top-level api, ie `Here()`, needs to be renamed to clarify to
>> > would-be readers of the source code that this is inline test code that
>> is
>> > not run when not reached via pytest. Eg I recommend `itest`, short,
>> easy to
>> > write, explicit.
>> >
>> > Cheers,
>> > Oliver
>> >
>> > On Thu., Dec. 29, 2022, 4:39 a.m. Bruno Oliveira, <nicoddemus at gmail.com
>> >
>> > wrote:
>> >
>> >> Hi Yuki,
>> >>
>> >> Sorry for the late reply, I think this notification slipped through the
>> >> cracks.
>> >>
>> >> We need two +1 votes from members before we can continue with the
>> transfer.
>> >>
>> >> I'm +1, the plugin definitely looks interesting, we need just one more
>> >> vote then.
>> >>
>> >> Cheers,
>> >> Bruno.
>> >>
>> >> On Wed, Nov 23, 2022 at 3:15 PM Yu Liu (Yuki) <yuki.liu at utexas.edu>
>> wrote:
>> >>
>> >>> Dear pytest developers,
>> >>>
>> >>> We would like to submit our plugin ?pytest-inline? to pytest-dev
>> >>> organization. pytest-inline is a plugin to help developers write
>> >>> inline tests at statement level. Inline testing is a new granularity
>> >>> of testing that make it easier to check individual program statements.
>> >>> An inline test is a statement that allows to provide arbitrary inputs
>> >>> and test oracles for checking the immediately preceding statement that
>> >>> is not an inline test. We have a paper about inline tests:
>> >>> https://arxiv.org/abs/2209.06315.
>> >>>
>> >>> Our current repo is at
>> >>> https://github.com/EngineeringSoftware/pytest-inline. We have
>> followed
>> >>> the guidelines to prepare the repo. We have also uploaded the plugin
>> >>> to PyPI. All of our contributors agreed to transfer the repo. Please
>> >>> let us know if you need any further information. Look forward to your
>> >>> feedback.
>> >>>
>> >>> Thanks,
>> >>> Yuki (with Alan, Milos, Owolabi, Pengyu, Zach)
>> >>> _______________________________________________
>> >>> pytest-dev mailing list
>> >>> pytest-dev at python.org
>> >>> https://mail.python.org/mailman/listinfo/pytest-dev
>> >>>
>> >> _______________________________________________
>> >> pytest-dev mailing list
>> >> pytest-dev at python.org
>> >> https://mail.python.org/mailman/listinfo/pytest-dev
>> >>
>> > _______________________________________________
>> > pytest-dev mailing list
>> > pytest-dev at python.org
>> > https://mail.python.org/mailman/listinfo/pytest-dev
>>
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pytest-dev/attachments/20221230/f67c74b2/attachment-0001.html>

From yuki.liu at utexas.edu  Fri Dec 30 23:50:03 2022
From: yuki.liu at utexas.edu (Yu Liu (Yuki))
Date: Fri, 30 Dec 2022 22:50:03 -0600
Subject: [pytest-dev] Submitting pytest-inline plugin
In-Reply-To: <CAKvgn7pkVTB5DbR6mnW=uDHAc5YPDNC9GDFdL-NY7v0aTm_yFw@mail.gmail.com>
References: <CAKvgn7rE2ko19vygrXqWfxQcRJiS6zeZtFhfkqUbdHWqFCL00g@mail.gmail.com>
 <CA+RQFfftNhY5-nr2KKg4Wwfx-JqsGK8X5cinKpHYaCncdYqgDQ@mail.gmail.com>
 <CAMb+DaXxf7uan310rbWwj4rUGcgFi1f9XL73+vfM=A0VhXP8gg@mail.gmail.com>
 <87cz82x71q.fsf@devork.be>
 <CA+RQFfe+8GMs67KTjnN5zojmaw+QJX5LfQe+Pn+A5EhrXd+Zrw@mail.gmail.com>
 <CAKvgn7pkVTB5DbR6mnW=uDHAc5YPDNC9GDFdL-NY7v0aTm_yFw@mail.gmail.com>
Message-ID: <CAKvgn7qD7Qgoi6TFmGKCWcM63_XCvH=-+pZedmLVzZo9=68H+w@mail.gmail.com>

Hi Bruno,

I have transferred the repo pytest-inline to you.

Thanks,
Yuki

On Fri, Dec 30, 2022 at 9:52 AM Yu Liu (Yuki) <yuki.liu at utexas.edu> wrote:

> Hi Bruno, Oliver, Floris,
>
> Thank you for the feedback! We have updated the README in our repo. We
> will also update the API from Here to itest, which may take some more
> time.
>
> If nobody objects by tomorrow, Yuki, could you please transfer the
>> repository to me, as well as send me the GitHub names that should
>> become admin of the repository once it is part of pytest-dev? Thanks.
>
>
> Sounds good! I will transfer the repo to you later today. We would like
> to add the following admins: sweetStreet, pengyunie, gliga, and
> owolabileg.
>
> Thanks,
> Yuki
>
> On Thu, Dec 29, 2022 at 3:46 PM Bruno Oliveira <nicoddemus at gmail.com>
> wrote:
>
>>
>>
>> On Thu, Dec 29, 2022 at 5:56 PM Floris Bruynooghe <flub at devork.be> wrote:
>>
>>> I'm happy to +1 as well, seems nothing wrong from a plugin acceptance
>>> perspective.  IIRC we're not vetting the plugins, merely allowing them
>>> to be taken over if the bus factor becomes fatally low.
>>>
>>
>> That was my understanding as well, the feedback is definitely
>> nice, however so far we never blocked any transfer due to requests/feedback
>> like that (not even sure that Oliver meant it in that manner anyway).
>>
>> Not that I'm saying the feedback isn't useful either though, maybe file
>>> it as an issue on the repo? (wait, do they get transferred by github as
>>> well?)
>>>
>>
>> Yes, everything is transferred accordingly.
>>
>> If nobody objects by tomorrow, Yuki, could you please transfer the
>> repository to me, as well as send me the GitHub names that should become
>> admin of the repository once it is part of pytest-dev? Thanks.
>>
>> Cheers,
>> Bruno.
>>
>>
>>> Cheers,
>>> Floris
>>>
>>>
>>> On Thu 29 Dec 2022 at 06:55 -0600, oliver wrote:
>>>
>>> > I had a look. Interesting idea for sure. A few things though :
>>> >
>>> > - the github page should clarify that these tests are intended to go
>>> in the
>>> > actual source code, rather than in the test code. Also, whether the
>>> inline
>>> > tests are merely empty functions when not hit via pytest.
>>> > - the github page should mention some important aspect like the
>>> performance
>>> > hit as discussed in the article that the page links to, and further
>>> clarify
>>> > how this is achieved (because for me, performance was one of my 2
>>> primany
>>> > concerns). I'm a little skeptical that it is that low because function
>>> > calls in Python are relatively expensive.... but I'm happy to be proven
>>> > wrong. Eg should one be aware that the hit of the article is per test
>>> > line.... so putting an inline test in a small loop could result in a
>>> > measurable hit, etc?
>>> > - the top-level api, ie `Here()`, needs to be renamed to clarify to
>>> > would-be readers of the source code that this is inline test code that
>>> is
>>> > not run when not reached via pytest. Eg I recommend `itest`, short,
>>> easy to
>>> > write, explicit.
>>> >
>>> > Cheers,
>>> > Oliver
>>> >
>>> > On Thu., Dec. 29, 2022, 4:39 a.m. Bruno Oliveira, <
>>> nicoddemus at gmail.com>
>>> > wrote:
>>> >
>>> >> Hi Yuki,
>>> >>
>>> >> Sorry for the late reply, I think this notification slipped through
>>> the
>>> >> cracks.
>>> >>
>>> >> We need two +1 votes from members before we can continue with the
>>> transfer.
>>> >>
>>> >> I'm +1, the plugin definitely looks interesting, we need just one more
>>> >> vote then.
>>> >>
>>> >> Cheers,
>>> >> Bruno.
>>> >>
>>> >> On Wed, Nov 23, 2022 at 3:15 PM Yu Liu (Yuki) <yuki.liu at utexas.edu>
>>> wrote:
>>> >>
>>> >>> Dear pytest developers,
>>> >>>
>>> >>> We would like to submit our plugin ?pytest-inline? to pytest-dev
>>> >>> organization. pytest-inline is a plugin to help developers write
>>> >>> inline tests at statement level. Inline testing is a new granularity
>>> >>> of testing that make it easier to check individual program
>>> statements.
>>> >>> An inline test is a statement that allows to provide arbitrary inputs
>>> >>> and test oracles for checking the immediately preceding statement
>>> that
>>> >>> is not an inline test. We have a paper about inline tests:
>>> >>> https://arxiv.org/abs/2209.06315.
>>> >>>
>>> >>> Our current repo is at
>>> >>> https://github.com/EngineeringSoftware/pytest-inline. We have
>>> followed
>>> >>> the guidelines to prepare the repo. We have also uploaded the plugin
>>> >>> to PyPI. All of our contributors agreed to transfer the repo. Please
>>> >>> let us know if you need any further information. Look forward to your
>>> >>> feedback.
>>> >>>
>>> >>> Thanks,
>>> >>> Yuki (with Alan, Milos, Owolabi, Pengyu, Zach)
>>> >>> _______________________________________________
>>> >>> pytest-dev mailing list
>>> >>> pytest-dev at python.org
>>> >>> https://mail.python.org/mailman/listinfo/pytest-dev
>>> >>>
>>> >> _______________________________________________
>>> >> pytest-dev mailing list
>>> >> pytest-dev at python.org
>>> >> https://mail.python.org/mailman/listinfo/pytest-dev
>>> >>
>>> > _______________________________________________
>>> > pytest-dev mailing list
>>> > pytest-dev at python.org
>>> > https://mail.python.org/mailman/listinfo/pytest-dev
>>>
>> _______________________________________________
>> pytest-dev mailing list
>> pytest-dev at python.org
>> https://mail.python.org/mailman/listinfo/pytest-dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pytest-dev/attachments/20221230/a54dc61c/attachment.html>

From nicoddemus at gmail.com  Sat Dec 31 06:42:47 2022
From: nicoddemus at gmail.com (Bruno Oliveira)
Date: Sat, 31 Dec 2022 08:42:47 -0300
Subject: [pytest-dev] Submitting pytest-inline plugin
In-Reply-To: <CAKvgn7qD7Qgoi6TFmGKCWcM63_XCvH=-+pZedmLVzZo9=68H+w@mail.gmail.com>
References: <CAKvgn7rE2ko19vygrXqWfxQcRJiS6zeZtFhfkqUbdHWqFCL00g@mail.gmail.com>
 <CA+RQFfftNhY5-nr2KKg4Wwfx-JqsGK8X5cinKpHYaCncdYqgDQ@mail.gmail.com>
 <CAMb+DaXxf7uan310rbWwj4rUGcgFi1f9XL73+vfM=A0VhXP8gg@mail.gmail.com>
 <87cz82x71q.fsf@devork.be>
 <CA+RQFfe+8GMs67KTjnN5zojmaw+QJX5LfQe+Pn+A5EhrXd+Zrw@mail.gmail.com>
 <CAKvgn7pkVTB5DbR6mnW=uDHAc5YPDNC9GDFdL-NY7v0aTm_yFw@mail.gmail.com>
 <CAKvgn7qD7Qgoi6TFmGKCWcM63_XCvH=-+pZedmLVzZo9=68H+w@mail.gmail.com>
Message-ID: <CA+RQFfdXELb1ZH2Jr8NAno2CNm2T2VC8WWJqU4CdYYZOfVNHzg@mail.gmail.com>

All done:

[image: image.png]

Let me know if anything else is missing.

Also, please add me as a maintainer in PyPI: nicoddemus.

Cheers,
Bruno.

On Sat, Dec 31, 2022 at 1:50 AM Yu Liu (Yuki) <yuki.liu at utexas.edu> wrote:

> Hi Bruno,
>
> I have transferred the repo pytest-inline to you.
>
> Thanks,
> Yuki
>
> On Fri, Dec 30, 2022 at 9:52 AM Yu Liu (Yuki) <yuki.liu at utexas.edu> wrote:
>
>> Hi Bruno, Oliver, Floris,
>>
>> Thank you for the feedback! We have updated the README in our repo. We
>> will also update the API from Here to itest, which may take some more
>> time.
>>
>> If nobody objects by tomorrow, Yuki, could you please transfer the
>>> repository to me, as well as send me the GitHub names that should
>>> become admin of the repository once it is part of pytest-dev? Thanks.
>>
>>
>> Sounds good! I will transfer the repo to you later today. We would like
>> to add the following admins: sweetStreet, pengyunie, gliga, and
>> owolabileg.
>>
>> Thanks,
>> Yuki
>>
>> On Thu, Dec 29, 2022 at 3:46 PM Bruno Oliveira <nicoddemus at gmail.com>
>> wrote:
>>
>>>
>>>
>>> On Thu, Dec 29, 2022 at 5:56 PM Floris Bruynooghe <flub at devork.be>
>>> wrote:
>>>
>>>> I'm happy to +1 as well, seems nothing wrong from a plugin acceptance
>>>> perspective.  IIRC we're not vetting the plugins, merely allowing them
>>>> to be taken over if the bus factor becomes fatally low.
>>>>
>>>
>>> That was my understanding as well, the feedback is definitely
>>> nice, however so far we never blocked any transfer due to requests/feedback
>>> like that (not even sure that Oliver meant it in that manner anyway).
>>>
>>> Not that I'm saying the feedback isn't useful either though, maybe file
>>>> it as an issue on the repo? (wait, do they get transferred by github as
>>>> well?)
>>>>
>>>
>>> Yes, everything is transferred accordingly.
>>>
>>> If nobody objects by tomorrow, Yuki, could you please transfer the
>>> repository to me, as well as send me the GitHub names that should become
>>> admin of the repository once it is part of pytest-dev? Thanks.
>>>
>>> Cheers,
>>> Bruno.
>>>
>>>
>>>> Cheers,
>>>> Floris
>>>>
>>>>
>>>> On Thu 29 Dec 2022 at 06:55 -0600, oliver wrote:
>>>>
>>>> > I had a look. Interesting idea for sure. A few things though :
>>>> >
>>>> > - the github page should clarify that these tests are intended to go
>>>> in the
>>>> > actual source code, rather than in the test code. Also, whether the
>>>> inline
>>>> > tests are merely empty functions when not hit via pytest.
>>>> > - the github page should mention some important aspect like the
>>>> performance
>>>> > hit as discussed in the article that the page links to, and further
>>>> clarify
>>>> > how this is achieved (because for me, performance was one of my 2
>>>> primany
>>>> > concerns). I'm a little skeptical that it is that low because function
>>>> > calls in Python are relatively expensive.... but I'm happy to be
>>>> proven
>>>> > wrong. Eg should one be aware that the hit of the article is per test
>>>> > line.... so putting an inline test in a small loop could result in a
>>>> > measurable hit, etc?
>>>> > - the top-level api, ie `Here()`, needs to be renamed to clarify to
>>>> > would-be readers of the source code that this is inline test code
>>>> that is
>>>> > not run when not reached via pytest. Eg I recommend `itest`, short,
>>>> easy to
>>>> > write, explicit.
>>>> >
>>>> > Cheers,
>>>> > Oliver
>>>> >
>>>> > On Thu., Dec. 29, 2022, 4:39 a.m. Bruno Oliveira, <
>>>> nicoddemus at gmail.com>
>>>> > wrote:
>>>> >
>>>> >> Hi Yuki,
>>>> >>
>>>> >> Sorry for the late reply, I think this notification slipped through
>>>> the
>>>> >> cracks.
>>>> >>
>>>> >> We need two +1 votes from members before we can continue with the
>>>> transfer.
>>>> >>
>>>> >> I'm +1, the plugin definitely looks interesting, we need just one
>>>> more
>>>> >> vote then.
>>>> >>
>>>> >> Cheers,
>>>> >> Bruno.
>>>> >>
>>>> >> On Wed, Nov 23, 2022 at 3:15 PM Yu Liu (Yuki) <yuki.liu at utexas.edu>
>>>> wrote:
>>>> >>
>>>> >>> Dear pytest developers,
>>>> >>>
>>>> >>> We would like to submit our plugin ?pytest-inline? to pytest-dev
>>>> >>> organization. pytest-inline is a plugin to help developers write
>>>> >>> inline tests at statement level. Inline testing is a new granularity
>>>> >>> of testing that make it easier to check individual program
>>>> statements.
>>>> >>> An inline test is a statement that allows to provide arbitrary
>>>> inputs
>>>> >>> and test oracles for checking the immediately preceding statement
>>>> that
>>>> >>> is not an inline test. We have a paper about inline tests:
>>>> >>> https://arxiv.org/abs/2209.06315.
>>>> >>>
>>>> >>> Our current repo is at
>>>> >>> https://github.com/EngineeringSoftware/pytest-inline. We have
>>>> followed
>>>> >>> the guidelines to prepare the repo. We have also uploaded the plugin
>>>> >>> to PyPI. All of our contributors agreed to transfer the repo. Please
>>>> >>> let us know if you need any further information. Look forward to
>>>> your
>>>> >>> feedback.
>>>> >>>
>>>> >>> Thanks,
>>>> >>> Yuki (with Alan, Milos, Owolabi, Pengyu, Zach)
>>>> >>> _______________________________________________
>>>> >>> pytest-dev mailing list
>>>> >>> pytest-dev at python.org
>>>> >>> https://mail.python.org/mailman/listinfo/pytest-dev
>>>> >>>
>>>> >> _______________________________________________
>>>> >> pytest-dev mailing list
>>>> >> pytest-dev at python.org
>>>> >> https://mail.python.org/mailman/listinfo/pytest-dev
>>>> >>
>>>> > _______________________________________________
>>>> > pytest-dev mailing list
>>>> > pytest-dev at python.org
>>>> > https://mail.python.org/mailman/listinfo/pytest-dev
>>>>
>>> _______________________________________________
>>> pytest-dev mailing list
>>> pytest-dev at python.org
>>> https://mail.python.org/mailman/listinfo/pytest-dev
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pytest-dev/attachments/20221231/e2d11919/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 33988 bytes
Desc: not available
URL: <https://mail.python.org/pipermail/pytest-dev/attachments/20221231/e2d11919/attachment-0001.png>

From yuki.liu at utexas.edu  Sat Dec 31 15:36:23 2022
From: yuki.liu at utexas.edu (Yu Liu (Yuki))
Date: Sat, 31 Dec 2022 14:36:23 -0600
Subject: [pytest-dev] Submitting pytest-inline plugin
In-Reply-To: <CA+RQFfdXELb1ZH2Jr8NAno2CNm2T2VC8WWJqU4CdYYZOfVNHzg@mail.gmail.com>
References: <CAKvgn7rE2ko19vygrXqWfxQcRJiS6zeZtFhfkqUbdHWqFCL00g@mail.gmail.com>
 <CA+RQFfftNhY5-nr2KKg4Wwfx-JqsGK8X5cinKpHYaCncdYqgDQ@mail.gmail.com>
 <CAMb+DaXxf7uan310rbWwj4rUGcgFi1f9XL73+vfM=A0VhXP8gg@mail.gmail.com>
 <87cz82x71q.fsf@devork.be>
 <CA+RQFfe+8GMs67KTjnN5zojmaw+QJX5LfQe+Pn+A5EhrXd+Zrw@mail.gmail.com>
 <CAKvgn7pkVTB5DbR6mnW=uDHAc5YPDNC9GDFdL-NY7v0aTm_yFw@mail.gmail.com>
 <CAKvgn7qD7Qgoi6TFmGKCWcM63_XCvH=-+pZedmLVzZo9=68H+w@mail.gmail.com>
 <CA+RQFfdXELb1ZH2Jr8NAno2CNm2T2VC8WWJqU4CdYYZOfVNHzg@mail.gmail.com>
Message-ID: <CAKvgn7r_0U8+_eS_Z9HWe8AoCpzDZB1buy99uXBDWdaBgO1zNg@mail.gmail.com>

Hi Bruno,

Thank you! I have added you as a maintainer in PyPI.

Thanks,
Yuki

On Sat, Dec 31, 2022 at 5:43 AM Bruno Oliveira <nicoddemus at gmail.com> wrote:

> All done:
>
> [image: image.png]
>
> Let me know if anything else is missing.
>
> Also, please add me as a maintainer in PyPI: nicoddemus.
>
> Cheers,
> Bruno.
>
> On Sat, Dec 31, 2022 at 1:50 AM Yu Liu (Yuki) <yuki.liu at utexas.edu> wrote:
>
>> Hi Bruno,
>>
>> I have transferred the repo pytest-inline to you.
>>
>> Thanks,
>> Yuki
>>
>> On Fri, Dec 30, 2022 at 9:52 AM Yu Liu (Yuki) <yuki.liu at utexas.edu>
>> wrote:
>>
>>> Hi Bruno, Oliver, Floris,
>>>
>>> Thank you for the feedback! We have updated the README in our repo. We
>>> will also update the API from Here to itest, which may take some more
>>> time.
>>>
>>> If nobody objects by tomorrow, Yuki, could you please transfer the
>>>> repository to me, as well as send me the GitHub names that should
>>>> become admin of the repository once it is part of pytest-dev? Thanks.
>>>
>>>
>>> Sounds good! I will transfer the repo to you later today. We would like
>>> to add the following admins: sweetStreet, pengyunie, gliga, and
>>> owolabileg.
>>>
>>> Thanks,
>>> Yuki
>>>
>>> On Thu, Dec 29, 2022 at 3:46 PM Bruno Oliveira <nicoddemus at gmail.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Thu, Dec 29, 2022 at 5:56 PM Floris Bruynooghe <flub at devork.be>
>>>> wrote:
>>>>
>>>>> I'm happy to +1 as well, seems nothing wrong from a plugin acceptance
>>>>> perspective.  IIRC we're not vetting the plugins, merely allowing them
>>>>> to be taken over if the bus factor becomes fatally low.
>>>>>
>>>>
>>>> That was my understanding as well, the feedback is definitely
>>>> nice, however so far we never blocked any transfer due to requests/feedback
>>>> like that (not even sure that Oliver meant it in that manner anyway).
>>>>
>>>> Not that I'm saying the feedback isn't useful either though, maybe file
>>>>> it as an issue on the repo? (wait, do they get transferred by github as
>>>>> well?)
>>>>>
>>>>
>>>> Yes, everything is transferred accordingly.
>>>>
>>>> If nobody objects by tomorrow, Yuki, could you please transfer the
>>>> repository to me, as well as send me the GitHub names that should become
>>>> admin of the repository once it is part of pytest-dev? Thanks.
>>>>
>>>> Cheers,
>>>> Bruno.
>>>>
>>>>
>>>>> Cheers,
>>>>> Floris
>>>>>
>>>>>
>>>>> On Thu 29 Dec 2022 at 06:55 -0600, oliver wrote:
>>>>>
>>>>> > I had a look. Interesting idea for sure. A few things though :
>>>>> >
>>>>> > - the github page should clarify that these tests are intended to go
>>>>> in the
>>>>> > actual source code, rather than in the test code. Also, whether the
>>>>> inline
>>>>> > tests are merely empty functions when not hit via pytest.
>>>>> > - the github page should mention some important aspect like the
>>>>> performance
>>>>> > hit as discussed in the article that the page links to, and further
>>>>> clarify
>>>>> > how this is achieved (because for me, performance was one of my 2
>>>>> primany
>>>>> > concerns). I'm a little skeptical that it is that low because
>>>>> function
>>>>> > calls in Python are relatively expensive.... but I'm happy to be
>>>>> proven
>>>>> > wrong. Eg should one be aware that the hit of the article is per test
>>>>> > line.... so putting an inline test in a small loop could result in a
>>>>> > measurable hit, etc?
>>>>> > - the top-level api, ie `Here()`, needs to be renamed to clarify to
>>>>> > would-be readers of the source code that this is inline test code
>>>>> that is
>>>>> > not run when not reached via pytest. Eg I recommend `itest`, short,
>>>>> easy to
>>>>> > write, explicit.
>>>>> >
>>>>> > Cheers,
>>>>> > Oliver
>>>>> >
>>>>> > On Thu., Dec. 29, 2022, 4:39 a.m. Bruno Oliveira, <
>>>>> nicoddemus at gmail.com>
>>>>> > wrote:
>>>>> >
>>>>> >> Hi Yuki,
>>>>> >>
>>>>> >> Sorry for the late reply, I think this notification slipped through
>>>>> the
>>>>> >> cracks.
>>>>> >>
>>>>> >> We need two +1 votes from members before we can continue with the
>>>>> transfer.
>>>>> >>
>>>>> >> I'm +1, the plugin definitely looks interesting, we need just one
>>>>> more
>>>>> >> vote then.
>>>>> >>
>>>>> >> Cheers,
>>>>> >> Bruno.
>>>>> >>
>>>>> >> On Wed, Nov 23, 2022 at 3:15 PM Yu Liu (Yuki) <yuki.liu at utexas.edu>
>>>>> wrote:
>>>>> >>
>>>>> >>> Dear pytest developers,
>>>>> >>>
>>>>> >>> We would like to submit our plugin ?pytest-inline? to pytest-dev
>>>>> >>> organization. pytest-inline is a plugin to help developers write
>>>>> >>> inline tests at statement level. Inline testing is a new
>>>>> granularity
>>>>> >>> of testing that make it easier to check individual program
>>>>> statements.
>>>>> >>> An inline test is a statement that allows to provide arbitrary
>>>>> inputs
>>>>> >>> and test oracles for checking the immediately preceding statement
>>>>> that
>>>>> >>> is not an inline test. We have a paper about inline tests:
>>>>> >>> https://arxiv.org/abs/2209.06315.
>>>>> >>>
>>>>> >>> Our current repo is at
>>>>> >>> https://github.com/EngineeringSoftware/pytest-inline. We have
>>>>> followed
>>>>> >>> the guidelines to prepare the repo. We have also uploaded the
>>>>> plugin
>>>>> >>> to PyPI. All of our contributors agreed to transfer the repo.
>>>>> Please
>>>>> >>> let us know if you need any further information. Look forward to
>>>>> your
>>>>> >>> feedback.
>>>>> >>>
>>>>> >>> Thanks,
>>>>> >>> Yuki (with Alan, Milos, Owolabi, Pengyu, Zach)
>>>>> >>> _______________________________________________
>>>>> >>> pytest-dev mailing list
>>>>> >>> pytest-dev at python.org
>>>>> >>> https://mail.python.org/mailman/listinfo/pytest-dev
>>>>> >>>
>>>>> >> _______________________________________________
>>>>> >> pytest-dev mailing list
>>>>> >> pytest-dev at python.org
>>>>> >> https://mail.python.org/mailman/listinfo/pytest-dev
>>>>> >>
>>>>> > _______________________________________________
>>>>> > pytest-dev mailing list
>>>>> > pytest-dev at python.org
>>>>> > https://mail.python.org/mailman/listinfo/pytest-dev
>>>>>
>>>> _______________________________________________
>>>> pytest-dev mailing list
>>>> pytest-dev at python.org
>>>> https://mail.python.org/mailman/listinfo/pytest-dev
>>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/pytest-dev/attachments/20221231/f960c056/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 33988 bytes
Desc: not available
URL: <https://mail.python.org/pipermail/pytest-dev/attachments/20221231/f960c056/attachment-0001.png>