-
-
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
Option to disable the RichHandler log handler? #3292
Labels
Comments
cpitclaudel
pushed a commit
to cpitclaudel/pelican
that referenced
this issue
Mar 12, 2024
* pelican/__init__.py (parse_arguments): Declare new --logs-handler argument. Uses a string instead of a `type=` argument to get better error messages when passed an incorrect choice. (main): Pass `args.logs_handler` to `init_logging` * pelican/log.py: Expose default log handler as `DEFAULT_LOG_HANDLER`. (init): Pass handler to `logging.basicConfig`. Closes getpelicanGH-3292.
cpitclaudel
pushed a commit
to cpitclaudel/pelican
that referenced
this issue
Mar 12, 2024
* pelican/__init__.py (parse_arguments): Declare new --logs-handler argument. Uses a string instead of a `type=` argument to get better error messages when passed an incorrect choice. (main): Pass `args.logs_handler` to `init_logging` * pelican/log.py: Expose default log handler as `DEFAULT_LOG_HANDLER`. (init): Pass handler to `logging.basicConfig`. Closes getpelicanGH-3292.
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request
The default logging format introduces aggressive line wraps. For example:
Unfortunately, my editor is not smart enough to undo the line breaks, so it offers to open
s/xxxxx/xxxxxxxxxxx/xxxxxxxxxxx.rst:74
instead.I would love an option to just print the error using a less-fancy log handler. The default format is pretty OK:
The text was updated successfully, but these errors were encountered: