Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

No support for LOG_NOTICE or LOG_EMERG

Open
#141 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python

Research direction

Start at the JournalHandler.map_priority entry point mentioned in the issue and read the surrounding logging documentation to understand the current priority mapping. Determine the intended behavior for LOG_NOTICE and LOG_EMERG, then add coverage and make the supported mapping explicit in the documentation.

Written by the indexing model from the issue text.

Description

There does not seem to be support for LOG_NOTICE or LOG_EMERG. Any level higher than logging.CRITICAL is mapped to LOG_ALERT. I presume there is a reason for this but could not discern that from the docs.

If one wished to support these levels I suppose they could subclass JournalHandler and override map_priority. Is that right?

Dominant language
C
Stars
522
Forks
79
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from systemd/python-systemd

All issues in systemd/python-systemd

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.