_thread: acquire_lock,release_lock still in use while declared to be "gone" in Documentation
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 37608 |
|---|---|
| Nosy | @brettcannon, @shiyuchong |
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 2019-07-17.10:23:49.505>
labels = ['3.7', 'type-feature', 'library']
title = '_thread: acquire_lock,release_lock still in use while declared to be "gone" in Documentation'
updated_at = <Date 2019-07-18.02:18:54.151>
user = 'https://github.com/shiyuchong'
bugs.python.org fields:
activity = <Date 2019-07-18.02:18:54.151>
actor = 'shiyuchong'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-07-17.10:23:49.505>
creator = 'shiyuchong'
dependencies = []
files = []
hgrepos = []
issue_num = 37608
keywords = []
message_count = 3.0
messages = ['348053', '348083', '348094']
nosy_count = 3.0
nosy_names = ['brett.cannon', 'docs@python', 'shiyuchong']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue37608'
versions = ['Python 3.7']
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
Start by reading the documentation for the _thread module and locating the entries for acquire_lock and release_lock. Compare the documented status with their actual continued use, then update the documentation so it accurately describes these functions and verify the relevant documentation build or checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100