Add microseconds to logging.LogRecord

Open
#90,450 6 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start at the logging.LogRecord entry point and read the linked usecs.patch to understand the proposed microsecond support. Confirm the logging behavior and tests relevant to LogRecord, then verify that records expose microseconds as requested.

Written by the indexing model from the issue text.

Description

stdlib type-feature
BPO 46292
Nosy @vsajip, @jamescasbon
Files
  • usecs.patch
    		•

    Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
closed_at = None
created_at = <Date 2022-01-07.14:11:50.738>
labels = ['type-feature', 'library', '3.11']
title = 'Add microseconds to logging.LogRecord'
updated_at = <Date 2022-01-12.15:23:32.019>
user = 'https://github.com/jamescasbon'

    bugs.python.org fields:

    activity = <Date 2022-01-12.15:23:32.019>
actor = 'arwade'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2022-01-07.14:11:50.738>
creator = 'jamescasbon'
dependencies = []
files = ['50546']
hgrepos = []
issue_num = 46292
keywords = ['patch']
message_count = 2.0
messages = ['409963', '410011']
nosy_count = 3.0
nosy_names = ['vinay.sajip', 'arwade', 'jamescasbon']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue46292'
versions = ['Python 3.11']

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    Contributor guide

    Open the contributing guide

    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 python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.