PR summary

This would slow down the typing at a command prompt while waiting for stdin from the programs because each character would bounce for 0.01 seconds adding up to a noticeable slowdown when piping in characters from an external source. Ithought this was needed while I was testing which is why I added that comment, but I just went through a few interactive test cases including the one from#26869 which all still worked interactively, and updated the display as expected. So I think we can safely remove it, but I'm not 100% on that.

The only way I could get this to fail was to interactively from my IDE "shift+enter" on the code blocks so that input was piped in. Is there a way to get that same effect in the interactive tests so we could add it there? Some quick tests withp.communicate() didn't slow it down for me in a script.

closes#27515

PR checklist

• "closes #0000" is in the body of the PR description tolink the related issue
• [open to suggestions] new and changed code istested
• [n/a]Plotting related features are demonstrated in anexample
• [n/a]New Features andAPI Changes are noted with adirective and release note
• [n/a] Documentation complies withgeneral anddocstring guidelines