pstats - allow stats sorting by cumulative time per call and total time per call

Open
#62,995 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start with pstats.py and review the historical patch files pstats.py and pstats-diff-issue18795.txt. Trace how statistics sort keys are handled, then verify that cumulative time per call and total time per call are available as sorting options and that existing sorting behavior remains intact.

Written by the indexing model from the issue text.

Description

stdlib type-feature
BPO 18795
Nosy @birkenfeld, @bitdancer, @jstasiak, @DanielNoord
PRs
  • python/cpython#31919
    		•
    Files
  • pstats.py: pstats source code with patch added
  • pstats-diff-issue18795.txt: Diff of patch against current version of pstats (Aug 21 2013)
    		•

    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 2013-08-20.23:48:11.951>
labels = ['type-feature', 'library']
title = 'pstats - allow stats sorting by cumulative time per call and total time per call'
updated_at = <Date 2022-03-15.23:29:12.822>
user = 'https://bugs.python.org/alexnvdias'

    bugs.python.org fields:

    activity = <Date 2022-03-15.23:29:12.822>
actor = 'danielnoord'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2013-08-20.23:48:11.951>
creator = 'alexnvdias'
dependencies = []
files = ['31391', '31396']
hgrepos = []
issue_num = 18795
keywords = ['patch']
message_count = 9.0
messages = ['195731', '195762', '195763', '195767', '195819', '195821', '196753', '209544', '415305']
nosy_count = 7.0
nosy_names = ['georg.brandl', 'r.david.murray', 'python-dev', 'alexnvdias', 'jstasiak', 'ramnes', 'danielnoord']
pr_nums = ['31919']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue18795'
versions = ['Python 3.4']

    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.