Add a profile decorator to profile and cProfile

Open
#53,531 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start by reviewing the referenced profile.patch and profile3.patch files, then inspect the profile and cProfile entry points in CPython. The issue depends on moving PEP 362 function signature objects into inspect and already lists PRs 287 and 1212, so check their status before proceeding. Done means profile and cProfile both support the requested decorator behavior.

Written by the indexing model from the issue text.

Description

3.7 (EOL) extension-modules stdlib type-feature
BPO 9285
Nosy @tim-one, @arigo, @birkenfeld, @rhettinger, @pitrou, @giampaolo, @benjaminp, @ezio-melotti, @merwok, @mlouielu
PRs
  • python/cpython#287
  • python/cpython#1212
    		•
    Dependencies
  • bpo-8916: Move PEP 362 (function signature objects) into inspect
    		•
    Files
  • profile.patch
  • profile.patch: provide new runcall() and runblock() functions
  • profile3.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 2010-07-17.14:01:10.668>
labels = ['extension-modules', 'type-feature', 'library', '3.7']
title = 'Add a profile decorator to profile and cProfile'
updated_at = <Date 2017-04-23.04:44:07.704>
user = 'https://github.com/giampaolo'

    bugs.python.org fields:

    activity = <Date 2017-04-23.04:44:07.704>
actor = 'louielu'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Extension Modules', 'Library (Lib)']
creation = <Date 2010-07-17.14:01:10.668>
creator = 'giampaolo.rodola'
dependencies = ['8916']
files = ['18039', '29050', '29242']
hgrepos = []
issue_num = 9285
keywords = ['patch', 'needs review']
message_count = 13.0
messages = ['110555', '124464', '132576', '140269', '181917', '181918', '181962', '182986', '288522', '288530', '288546', '292148', '292150']
nosy_count = 15.0
nosy_names = ['tim.peters', 'arigo', 'georg.brandl', 'rhettinger', 'nbastin', 'pitrou', 'giampaolo.rodola', 'benjamin.peterson', 'ezio.melotti', 'eric.araujo', 'tleeuwenburg@gmail.com', 'debatem1', 'ubershmekel', 'bjorns', 'louielu']
pr_nums = ['287', '1212']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue9285'
versions = ['Python 3.7']

    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.