Use the _functools module to speed up functools.total_ordering

Open
#66,268 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
performance

Research direction

The issue names functools.total_ordering and the _functools module but identifies no files, tests, or entry points. Start by locating both implementations and tracing how total_ordering is exercised; clarify the expected compatibility and performance criteria before deciding what completion requires.

Written by the indexing model from the issue text.

Description

3.12 performance stdlib
BPO 22070
Nosy @rhettinger, @ncoghlan, @alex

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 2014-07-25.16:46:19.760>
labels = ['performance']
title = 'Use the _functools module to speed up functools.total_ordering'
updated_at = <Date 2014-07-25.17:01:30.863>
user = 'https://github.com/ncoghlan'

bugs.python.org fields:

activity = <Date 2014-07-25.17:01:30.863>
actor = 'ncoghlan'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2014-07-25.16:46:19.760>
creator = 'ncoghlan'
dependencies = []
files = []
hgrepos = []
issue_num = 22070
keywords = []
message_count = 3.0
messages = ['223967', '223968', '223970']
nosy_count = 3.0
nosy_names = ['rhettinger', 'ncoghlan', 'alex']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'performance'
url = 'https://bugs.python.org/issue22070'
versions = ['Python 3.5']

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.