From oliver.schoenborn at gmail.com Sun Jan 1 00:55:31 2023 From: oliver.schoenborn at gmail.com (oliver) Date: Sat, 31 Dec 2022 23:55:31 -0600 Subject: [pytest-dev] Submitting pytest-inline plugin In-Reply-To: References:

<87cz82x71q.fsf@devork.be>

Message-ID: On Fri., Dec. 30, 2022, 9:53 a.m. Yu Liu (Yuki), 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 > Thank you Yu Liu and congratulations! > 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 > wrote: > >> >> >> On Thu, Dec 29, 2022 at 5:56 PM Floris Bruynooghe 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) >>> 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 >> > _______________________________________________ > 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: From nicoddemus at gmail.com Sat Jan 14 07:23:12 2023 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Sat, 14 Jan 2023 09:23:12 -0300 Subject: [pytest-dev] pytest 7.2.1 Message-ID: pytest 7.2.1 has just been released to PyPI. This is a bug-fix release, being a drop-in replacement. To upgrade:: pip install --upgrade pytest The full changelog is available at https://docs.pytest.org/en/stable/changelog.html. Thanks to all of the contributors to this release: * Anthony Sottile * Bruno Oliveira * Daniel Valenzuela * Kadino * Prerak Patel * Ronny Pfannschmidt * Santiago Castro * s-padmanaban Happy testing, The pytest Development Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Fri Jan 20 08:44:59 2023 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Fri, 20 Jan 2023 10:44:59 -0300 Subject: [pytest-dev] Enabling 2FA for pytest-dev on PyPI Message-ID: Hi folks, In https://mail.python.org/pipermail/pytest-dev/2022-December/005139.html we agreed on enabling 2FA for pytest-dev on GitHub, which we did. How about we do the same for the pytest project in PyPI? Cheers, Bruno. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Fri Jan 20 08:47:18 2023 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Fri, 20 Jan 2023 10:47:18 -0300 Subject: [pytest-dev] Enabling 2FA for pytest-dev on PyPI In-Reply-To: References: Message-ID: Sorry for the noise folks, pytest is a critical project and 2FA will be mandatory anyway: 2FA requirement Requiring 2FA for this project will require all collaborators to have 2FA enabled for their individual account. Any collaborator who does not have 2FA enabled will not be able to manage the project until they enable 2FA. This project will be part of PyPI's two-factor authentication mandate for critical projects. As a result, this setting cannot be disabled for this project. So no action is required. Cheers, Bruno. On Fri, Jan 20, 2023 at 10:44 AM Bruno Oliveira wrote: > Hi folks, > > In https://mail.python.org/pipermail/pytest-dev/2022-December/005139.html > we agreed on enabling 2FA for pytest-dev on GitHub, which we did. > > How about we do the same for the pytest project in PyPI? > > Cheers, > Bruno. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From flub at devork.be Sun Jan 22 04:47:29 2023 From: flub at devork.be (Floris Bruynooghe) Date: Sun, 22 Jan 2023 10:47:29 +0100 Subject: [pytest-dev] Enabling 2FA for pytest-dev on PyPI In-Reply-To: References:

Message-ID: <87mt6asxxq.fsf@devork.be> So why does tidelift keep telling us every week this isn't completed? On Fri 20 Jan 2023 at 10:47 -0300, Bruno Oliveira wrote: > Sorry for the noise folks, pytest is a critical project and 2FA will be > mandatory anyway: > > 2FA requirement > > Requiring 2FA for this project will require all collaborators to have 2FA > enabled for their individual account. Any collaborator who does not have > 2FA enabled will not be able to manage the project until they enable 2FA. > This project will be part of PyPI's two-factor authentication mandate for > critical projects. As a result, this setting cannot be disabled for this > project. > > So no action is required. > > Cheers, > Bruno. > > On Fri, Jan 20, 2023 at 10:44 AM Bruno Oliveira > wrote: > >> Hi folks, >> >> In https://mail.python.org/pipermail/pytest-dev/2022-December/005139.html >> we agreed on enabling 2FA for pytest-dev on GitHub, which we did. >> >> How about we do the same for the pytest project in PyPI? >> >> Cheers, >> Bruno. >> > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev From nicoddemus at gmail.com Sun Jan 22 08:00:09 2023 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Sun, 22 Jan 2023 10:00:09 -0300 Subject: [pytest-dev] Enabling 2FA for pytest-dev on PyPI In-Reply-To: <87mt6asxxq.fsf@devork.be> References:

<87mt6asxxq.fsf@devork.be> Message-ID: Yes that's why the message came to be hehehe. It will eventually be mandatory, from my understanding. Cheers On Sun, Jan 22, 2023 at 6:47 AM Floris Bruynooghe wrote: > So why does tidelift keep telling us every week this isn't completed? > > On Fri 20 Jan 2023 at 10:47 -0300, Bruno Oliveira wrote: > > > Sorry for the noise folks, pytest is a critical project and 2FA will be > > mandatory anyway: > > > > 2FA requirement > > > > Requiring 2FA for this project will require all collaborators to have 2FA > > enabled for their individual account. Any collaborator who does not have > > 2FA enabled will not be able to manage the project until they enable 2FA. > > This project will be part of PyPI's two-factor authentication mandate for > > critical projects. As a result, this setting cannot be disabled for this > > project. > > > > So no action is required. > > > > Cheers, > > Bruno. > > > > On Fri, Jan 20, 2023 at 10:44 AM Bruno Oliveira > > wrote: > > > >> Hi folks, > >> > >> In > https://mail.python.org/pipermail/pytest-dev/2022-December/005139.html > >> we agreed on enabling 2FA for pytest-dev on GitHub, which we did. > >> > >> How about we do the same for the pytest project in PyPI? > >> > >> 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: From flub at devork.be Mon Jan 23 15:56:14 2023 From: flub at devork.be (Floris Bruynooghe) Date: Mon, 23 Jan 2023 21:56:14 +0100 Subject: [pytest-dev] Enabling 2FA for pytest-dev on PyPI In-Reply-To: References:

<87mt6asxxq.fsf@devork.be> Message-ID: <87r0vlrmvl.fsf@devork.be> So I think it already is mandatory, logging into pypi it is enabled and can not be disabled. Everyone but pfcdayelise have 2FA enabled, I assume this means they can no longer manage pytest on pypi as long as they don't enable 2FA. That's probably fine, that's why we have multiple people. The tidelift message seems to be because they don't have the information from pypi, which is fair enough. So they require you to login to tidelift and tick a box saying "I've enabled 2FA on PyPI". Which TheCompiler has not yet done. Could you do that please? It would make tidelift happier. Finally - and this is a little bit off-topic for this email I guess - I notice that on PyPI not too many of the currently active people have access. Would it be good to extend this to a few more people if they wish? Hum, logging into tidelift it seems that On Sun 22 Jan 2023 at 10:00 -0300, Bruno Oliveira wrote: > Yes that's why the message came to be hehehe. > > It will eventually be mandatory, from my understanding. > > Cheers > > On Sun, Jan 22, 2023 at 6:47 AM Floris Bruynooghe wrote: > >> So why does tidelift keep telling us every week this isn't completed? >> >> On Fri 20 Jan 2023 at 10:47 -0300, Bruno Oliveira wrote: >> >> > Sorry for the noise folks, pytest is a critical project and 2FA will be >> > mandatory anyway: >> > >> > 2FA requirement >> > >> > Requiring 2FA for this project will require all collaborators to have 2FA >> > enabled for their individual account. Any collaborator who does not have >> > 2FA enabled will not be able to manage the project until they enable 2FA. >> > This project will be part of PyPI's two-factor authentication mandate for >> > critical projects. As a result, this setting cannot be disabled for this >> > project. >> > >> > So no action is required. >> > >> > Cheers, >> > Bruno. >> > >> > On Fri, Jan 20, 2023 at 10:44 AM Bruno Oliveira >> > wrote: >> > >> >> Hi folks, >> >> >> >> In >> https://mail.python.org/pipermail/pytest-dev/2022-December/005139.html >> >> we agreed on enabling 2FA for pytest-dev on GitHub, which we did. >> >> >> >> How about we do the same for the pytest project in PyPI? >> >> >> >> 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 Mon Jan 23 16:16:47 2023 From: me at the-compiler.org (Florian Bruhin) Date: Mon, 23 Jan 2023 22:16:47 +0100 Subject: [pytest-dev] Enabling 2FA for pytest-dev on PyPI In-Reply-To: <87r0vlrmvl.fsf@devork.be> References:

<87mt6asxxq.fsf@devork.be> <87r0vlrmvl.fsf@devork.be> Message-ID: <20230123211647.lwp6tw6smjw7wgub@aragog> Hey, On Mon, Jan 23, 2023 at 09:56:14PM +0100, Floris Bruynooghe wrote: > The tidelift message seems to be because they don't have the information > from pypi, which is fair enough. So they require you to login to > tidelift and tick a box saying "I've enabled 2FA on PyPI". Which > TheCompiler has not yet done. Could you do that please? It would make > tidelift happier. Whoops, I must have missed that - thanks for the explanation, done! > Finally - and this is a little bit off-topic for this email I guess - I > notice that on PyPI not too many of the currently active people have > access. Would it be good to extend this to a few more people if they > wish? +0 from my side. I think we should keep PyPI access to a reasonably small circle of people, and there's no immediate need IMHO to make that bigger (given that we have multiple people who are at least reachable). But I'm also not generally against adding more people who are active and in e.g. pytest-dev/core on GitHub. Florian -- me at the-compiler.org | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: