A suggestion about jishaku HOT 2 CLOSED

Jishaku doesn't redirect stdout automatically for reasons discussed in #39.

A flag to enable such capturing behavior might be possible, but having it on the command seems like a clunky approach that would have parsing complications, and I don't really want it as an env flag or a switch (like retain) because it would apply to all evaluations, making it easy for the issues described to manifest if you don't make due consideration for it.

I also fear people would turn it on without understanding the implications.

As mentioned in #39, you can do this behavior of your own accord if it is truly necessary like so:

with io!.StringIO() as f, contextlib!.redirect_stdout(f):
    print("hi")

    await _author.send(f.getvalue())  # send stdout contents to author

Otherwise, I recommend adjusting your code to not require capturing of stdout at all. It is more often than not possible to retrieve the data you need programmatically, rather than sifting the output stream.

For instance, if you're just printing to retrieve feedback on intermediate values, you can do so with yield:

x = 1 + 2
yield f"1 + 2 = {x}"

Even print-heavy stdlib functions like dis.dis offer workarounds that allow you to print into a buffer you can report from instead, without touching stdout:

with io!.StringIO() as f:  # no redirect_stdout here!
    dis!.dis(lambda x: x ** 2, file=f)
    yield f.getvalue()

from jishaku.

believe this is answered in #38

from jishaku.