delete misleading faq entry about atomic operations
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- documentation
Research direction
Start by locating the Python documentation FAQ entry about atomic operations and review why it is considered misleading. Remove that entry, then verify the documentation no longer contains it; the issue references existing PR python/cpython#28886 for context.
Written by the indexing model from the issue text.
Description
| BPO | 45435 |
|---|---|
| Nosy | @pitrou, @stevendaprano, @serhiy-storchaka, @jeff5, @graingert, @pablogsal, @bensimner |
| PRs |
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 2021-10-11.20:25:32.309>
labels = ['3.11', 'type-bug', '3.9', '3.10', 'docs']
title = 'delete misleading faq entry about atomic operations'
updated_at = <Date 2021-10-12.23:09:38.937>
user = 'https://github.com/graingert'
bugs.python.org fields:
activity = <Date 2021-10-12.23:09:38.937>
actor = 'bjs'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2021-10-11.20:25:32.309>
creator = 'graingert'
dependencies = []
files = []
hgrepos = []
issue_num = 45435
keywords = ['patch']
message_count = 8.0
messages = ['403700', '403714', '403715', '403716', '403725', '403729', '403754', '403765']
nosy_count = 8.0
nosy_names = ['pitrou', 'steven.daprano', 'docs@python', 'serhiy.storchaka', 'jeff.allen', 'graingert', 'pablogsal', 'bjs']
pr_nums = ['28886']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue45435'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100