-
|
Hi all, Quick question, is there a nice way to use I'm veering towards setting up a console, printing to it with Cheers, Phil |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
|
I guess I could create a console object, run inspect using that and capture the output to a string, and then print that string to the log file (x-ref #2374 (comment) ) A bit roundabout, but should work.. Any nicer ways? 🤔 |
Beta Was this translation helpful? Give feedback.
-
|
That may be your only option. The logging API is designed to work with strings, and other loggers wouldn't know how render Rich objects. If you don't mind that the inspect data only working with the RichHandler you could do something like this: handler.console.log(Inspect(foo)) |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for this - having another go now I'm back after holidays.
Ideally I want this for verbose logging which in this tool can get written to a file, so if possible I'd like it to play nicely with I had a go with the inspect_console = Console(no_color=True)
with inspect_console.capture() as capture:
inspect(
subprocess.run(
self.before_command,
cwd=self.working_dir,
shell=True,
env=command_env,
capture_output=True,
),
title="'before_command' results",
docs=False,
console=inspect_console,
)
log.debug(capture.get())Setting Am I missing something? Is there no way to disable colour from |
Beta Was this translation helpful? Give feedback.
-
|
ok, it's grim but manually removing the double ansi-codes works: log.debug(re.sub(r"(\x9B|\x1B\[)[0-?]*[ -\/]*[@-~]", "", capture.get()))Plain text logging handler: |
Beta Was this translation helpful? Give feedback.
-
|
Ah. Since you're generating the output in another process, any changes to the Try setting Alternatively, to strip ansi codes you can do |
Beta Was this translation helpful? Give feedback.
-
|
Ah, I knew there was a nice way to remove ansi codes with rich and without resorting to a regex - just couldn't find the name. I think the subprocess is a bit of a red herring - the output isn't coming from another process, it just happens to be a subprocess object that I'm inspecting in the main code. I'm could swap that for any other object and it would do the same: Exampleinspect_console = Console()
with inspect_console.capture() as capture:
inspect(
inspect_console,
title="'before_command' results",
docs=False,
console=inspect_console,
)
log.debug(capture.get())With ANSI codes manually stripped and a plain console, everything's fine: inspect_console = Console(no_color=True)
with inspect_console.capture() as capture:
inspect(
inspect_console,
title="'before_command' results",
docs=False,
console=inspect_console,
)
log.debug(Text.from_ansi(capture.get()).plain) |
Beta Was this translation helpful? Give feedback.
-
|
Saya tidak paham tolong bantuannya
Pada tanggal Jum, 19 Agu 2022 15.58, Phil Ewels ***@***.***>
menulis:
… Thanks for this - having another go now I'm back after holidays.
If you don't mind that the inspect data only working with the RichHandler
Ideally I want this for verbose logging which in this tool can get written
to a file, so if possible I'd like it to play nicely with
logging.FileHandler (though refactoring this could be another option)
I had a go with the capture() output approach and it half works, but I
get all of the ANSI codes. Even if I tell the console not to use colour, I
still get them in the inspect() output:
inspect_console = Console(no_color=True)with inspect_console.capture() as capture:
inspect(
subprocess.run(
self.before_command,
cwd=self.working_dir,
shell=True,
env=command_env,
capture_output=True,
),
title="'before_command' results",
docs=False,
console=inspect_console,
)log.debug(capture.get())
DEBUG ╭────────────────────────────────────────────────────────── 'before_command' results ──────────────────────────────────────────────────────────╮
│ ╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮ │
│ │ [1mCompletedProcess[0m[1m([0margs='echo "This is a very simple example" > before_after_command_example.txt\n', returncode=[1m0[0m, stdout=b'',
stderr=b''[1m)[0m │ │
│ ╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯ │
│ │
│ [3margs[0m = 'echo "This is a very simple example" > before_after_command_example.txt\n' │
│ [3mreturncode[0m = [1m0[0m
│
│ [3mstderr[0m = b'' │
│ [3mstdout[0m = b'' │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
Am I missing something? Is there no way to disable colour from inspect()?
🤔
—
Reply to this email directly, view it on GitHub
<#2378 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZMOCWZKXMIPVGVHEUMHQQLVZ45BZANCNFSM52VQRNGA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
I guess I could create a console object, run inspect using that and capture the output to a string, and then print that string to the log file (x-ref #2374 (comment) )
A bit roundabout, but should work.. Any nicer ways? 🤔