Document DeferredSemaphore in "Using Deferreds"
Open
Nobody has claimed this yet.
assigned
bug
core
documentation
priority-high
- Dominant language
- Python
- Stars
- 6k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Description
 |
moof reported |
|---|---|
| Trac ID | trac#1432 |
| Type | defect |
| Created | 2006-01-22 17:51:27Z |
Searchable metadata
trac-id__1432 1432
type__defect defect
reporter__moof moof
priority__high high
milestone__
branch__
branch_author__
status__assigned assigned
resolution__
component__core core
keywords__documentation documentation
time__1137952287000000 1137952287000000
changetime__1375218067000000 1375218067000000
version__
owner__zintinio zintinio
cc__glyph cc__moof cc__thijs
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 locating the “Using Deferreds” documentation and the existing DeferredSemaphore API or reference material. Compare the current coverage with the DeferredSemaphore behavior and document the missing usage details. Done means the guide explains DeferredSemaphore clearly and the documentation builds successfully.
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