-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] timefmt #3225
Comments
(I tried to create a patch, but failed -- not familiar enough with the internal flow handling of the date formatting) |
Hey, my university software engineering group are willing to tackle this issue. Would it be possible to assign us? Here are our git usernames @albinkempe @lolindgr @ollisco @SihamShahoud and me @selmaozdere |
Hello @hardaker. I have found a few solutions to this issue 1. using a lambdalogging.basicConfig(format="%(message)s",
handlers=[RichHandler(rich_tracebacks=True)],
datefmt=lambda x: "", # since we can provide a Callable
) 2. Using a escape charlogging.basicConfig(format="%(message)s",
handlers=[RichHandler(rich_tracebacks=True)],
datefmt="\0",
) 3. Using the RichHandlers
|
Describe the bug
It is impossible to use a blank datefmt ("").
The above forces a date:
Changing the datefmt to be a single space instead works, but adds a space to the front of the line:
Platform
platform="Linux"
enrich==1.2.7
rich==12.5.1
rich-cli==1.8.0
rich-logging==0.0.1
rich-rst==1.1.7
The text was updated successfully, but these errors were encountered: