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....@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....@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 <nicodde...@gmail.com> >> wrote: >> >>> >>> >>> On Thu, Dec 29, 2022 at 5:56 PM Floris Bruynooghe <f...@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, < >>>> nicodde...@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....@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@python.org >>>> >>> https://mail.python.org/mailman/listinfo/pytest-dev >>>> >>> >>>> >> _______________________________________________ >>>> >> pytest-dev mailing list >>>> >> pytest-dev@python.org >>>> >> https://mail.python.org/mailman/listinfo/pytest-dev >>>> >> >>>> > _______________________________________________ >>>> > pytest-dev mailing list >>>> > pytest-dev@python.org >>>> > https://mail.python.org/mailman/listinfo/pytest-dev >>>> >>> _______________________________________________ >>> pytest-dev mailing list >>> pytest-dev@python.org >>> https://mail.python.org/mailman/listinfo/pytest-dev >>> >>
_______________________________________________ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
