.python_history file causes considerable slowdown
Open
Nobody has claimed this yet.
3.12
build
performance
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 41563 |
|---|---|
| Nosy | @stevendaprano |
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 2020-08-16.11:42:32.757>
labels = ['build', '3.8', 'performance']
title = '.python_history file causes considerable slowdown'
updated_at = <Date 2020-08-17.10:33:46.799>
user = 'https://bugs.python.org/bytecookie'
bugs.python.org fields:
activity = <Date 2020-08-17.10:33:46.799>
actor = 'bytecookie'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Build']
creation = <Date 2020-08-16.11:42:32.757>
creator = 'bytecookie'
dependencies = []
files = []
hgrepos = []
issue_num = 41563
keywords = []
message_count = 5.0
messages = ['375505', '375506', '375538', '375539', '375540']
nosy_count = 2.0
nosy_names = ['steven.daprano', 'bytecookie']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'performance'
url = 'https://bugs.python.org/issue41563'
versions = ['Python 3.8']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names only the .python_history file and BPO 41563; start by reviewing that report and reproducing the reported slowdown. Done means identifying the cause and verifying an improvement, but the payload does not specify a target file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100