From jeff.washcloth at gmail.com Thu Jul 1 05:20:09 2021 From: jeff.washcloth at gmail.com (Jeff Wright) Date: Thu, 1 Jul 2021 05:20:09 -0400 Subject: [pytest-dev] Console folding Message-ID: Hello, I am doing some investigation into the possibility of implementing a 'folding' capability for Pytest's console output, and wanted to ask here about the feasibility of this idea. My main motivator is the fact that, in the face of multiple test failures, and with the default console behavior in place, the output can span many pages, requiring the tester to scroll back and hunt for the first failed test in the run. It is easy to get lost, and hard to pinpoint precisely where things started to go wrong. So I thought it would be helpful to have a capability that implements some sort of console 'folding', such that all the detailed Pytest console content is still available, just hidden by default - yet still able to be expanded in some way with operator interaction. [I don't know yet if "operator interaction" would be done with keyboard, mouse, or what.] I do know that Pytest already allows changing the level of verbosity, traceback info, etc. I am also aware of the pytest-html plugin, which is pretty much exactly what I am looking for, just in-console. Would appreciate some comments/advice...is this even do-able? I can't be the first person to dream of such a thing! Thanks, Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Thu Jul 1 06:34:03 2021 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Thu, 1 Jul 2021 07:34:03 -0300 Subject: [pytest-dev] Console folding In-Reply-To: References: Message-ID: Hi Jeff, That seems really useful, however it would require pytest's output to become interactive, which would be a separate application I believe. This certainly seems possible to implement as a plugin, perhaps using Rich? Anyway that is a neat idea. Cheers, Bruno. On Thu, Jul 1, 2021 at 6:20 AM Jeff Wright wrote: > Hello, > > I am doing some investigation into the possibility of implementing a > 'folding' capability for Pytest's console output, and wanted to ask here > about the feasibility of this idea. My main motivator is the fact that, in > the face of multiple test failures, and with the default console behavior > in place, the output can span many pages, requiring the tester to scroll > back and hunt for the first failed test in the run. It is easy to get lost, > and hard to pinpoint precisely where things started to go wrong. > > So I thought it would be helpful to have a capability that implements some > sort of console 'folding', such that all the detailed Pytest console > content is still available, just hidden by default - yet still able to be > expanded in some way with operator interaction. [I don't know yet if > "operator interaction" would be done with keyboard, mouse, or what.] I do > know that Pytest already allows changing the level of verbosity, traceback > info, etc. I am also aware of the pytest-html plugin, which is pretty much > exactly what I am looking for, just in-console. > > Would appreciate some comments/advice...is this even do-able? I can't be > the first person to dream of such a thing! > > Thanks, Jeff > _______________________________________________ > 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 jeff.washcloth at gmail.com Thu Jul 1 06:57:09 2021 From: jeff.washcloth at gmail.com (Jeff Wright) Date: Thu, 1 Jul 2021 06:57:09 -0400 Subject: [pytest-dev] Console folding In-Reply-To: References: Message-ID: Thanks for the feedback, Bruno. Just an FYI for anyone following this thread in the mail list - I also posed the same question on the Github discussions list: https://github.com/pytest-dev/pytest/discussions/8843. Was not sure if this mail list was even used anymore! Regards, Jeff On Thu, Jul 1, 2021 at 6:34 AM Bruno Oliveira wrote: > Hi Jeff, > > That seems really useful, however it would require pytest's output to > become interactive, which would be a separate application I believe. This > certainly seems possible to implement as a plugin, perhaps using Rich? > Anyway that is a neat idea. > > Cheers, > Bruno. > > On Thu, Jul 1, 2021 at 6:20 AM Jeff Wright > wrote: > >> Hello, >> >> I am doing some investigation into the possibility of implementing a >> 'folding' capability for Pytest's console output, and wanted to ask here >> about the feasibility of this idea. My main motivator is the fact that, in >> the face of multiple test failures, and with the default console behavior >> in place, the output can span many pages, requiring the tester to scroll >> back and hunt for the first failed test in the run. It is easy to get lost, >> and hard to pinpoint precisely where things started to go wrong. >> >> So I thought it would be helpful to have a capability that implements >> some sort of console 'folding', such that all the detailed Pytest console >> content is still available, just hidden by default - yet still able to be >> expanded in some way with operator interaction. [I don't know yet if >> "operator interaction" would be done with keyboard, mouse, or what.] I do >> know that Pytest already allows changing the level of verbosity, traceback >> info, etc. I am also aware of the pytest-html plugin, which is pretty much >> exactly what I am looking for, just in-console. >> >> Would appreciate some comments/advice...is this even do-able? I can't be >> the first person to dream of such a thing! >> >> Thanks, Jeff >> _______________________________________________ >> 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 Sun Jul 18 13:25:45 2021 From: flub at devork.be (Floris Bruynooghe) Date: Sun, 18 Jul 2021 19:25:45 +0200 Subject: [pytest-dev] pytest-timeout maintaintenance Message-ID: <874kcr4jqe.fsf@powell.devork.be> Hi all, As you might be aware I've been doing extremely little with respect to pytest-timeout maintenance. This is mostly fine as it's a very low maintenance package at this point in its lifecycle, but it does give people who do try to contribute valuable things a very suboptimal experience of me reviewing things about once a month or less. And there hasn't been anyone regularly contributing that I can just give permissions. So this is a call to see if anyone thinks they could do a better job at maintaining pytest-timeout. If so let me know, go guide people through PRs and I'll happily give the right maintainer bits on github and PyPI. It's not that I don't want to touch it anymore or entirely disappear, and I will remain happy to answer the occasional question. Though my time is certainly not spent on it anymore and my response times will probably remain in O(weeks) as they are currently. If no one would like to do this it's also not the worst, but contributors will keep having to put up with the current sub-optimal level of maintainer interaction. Cheers, Floris