Skip to content
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

Change logging to include datetime and loglevel #1023

Merged
merged 2 commits into from
May 4, 2024

Conversation

ix5
Copy link
Member

@ix5 ix5 commented Apr 29, 2024

Checklist

  • All new and existing tests are passing
  • (If adding features:) I have added tests to cover my changes
  • (If docs changes needed:) I have updated the documentation accordingly.
  • I have added an entry to CHANGES.rst because this is a user-facing change or an important bugfix
  • I have written proper commit message(s)

What changes does this Pull Request introduce?

This change propagates the log format formerly only for werkzeug to all isso logs.

Why is this necessary?

Having date and time information as well as the loglevel should satisfy most users instead of the more complicated solution in #976

ix5 added 2 commits April 29, 2024 23:29
This change propagates the log format formerly only for
werkzeug to all isso logs.

Having date and time information as well as the loglevel
should satisfy most users instead of the more complicated
solution in isso-comments#976
@ix5 ix5 added server (Python) server code improvement Not a new feature, but makes Isso more pleasant to use labels Apr 29, 2024
@ix5 ix5 added this to the 0.14 milestone Apr 29, 2024
@ix5 ix5 merged commit 6c6d5d2 into isso-comments:master May 4, 2024
15 checks passed
@ix5 ix5 deleted the log-format-default branch May 4, 2024 18:43
@ix5 ix5 modified the milestones: 0.14, 0.13.1 May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement Not a new feature, but makes Isso more pleasant to use server (Python) server code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants