We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
GitHub fields:
assignee = None closed_at = <Date 2019-04-11.10:12:13.367> created_at = <Date 2019-04-09.13:35:46.376> labels = ['3.8', 'library'] title = 'Use _PyTime_GetPerfCounter() in lsprof' updated_at = <Date 2019-04-11.10:12:13.366> user = 'https://github.com/methane'
bugs.python.org fields:
activity = <Date 2019-04-11.10:12:13.366> actor = 'methane' assignee = 'none' closed = True closed_date = <Date 2019-04-11.10:12:13.367> closer = 'methane' components = ['Library (Lib)'] creation = <Date 2019-04-09.13:35:46.376> creator = 'methane' dependencies = [] files = [] hgrepos = [] issue_num = 36575 keywords = ['patch'] message_count = 2.0 messages = ['339747', '339953'] nosy_count = 2.0 nosy_names = ['vstinner', 'methane'] pr_nums = ['8378'] priority = 'normal' resolution = 'fixed' stage = 'resolved' status = 'closed' superseder = None type = None url = 'https://bugs.python.org/issue36575' versions = ['Python 3.8']
The text was updated successfully, but these errors were encountered:
Current lsprof uses gettimeofday on non-Windows. _PyTime_GetPerfCounter() is better time for profiling.
gettimeofday
Sorry, something went wrong.
New changeset 536a35b by Inada Naoki in branch 'master': bpo-36575: lsprof: Use _PyTime_GetPerfCounter() (GH-8378) 536a35b
No branches or pull requests
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:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: