TwistedDevelopment instructions are broken
Open
Nobody has claimed this yet.
bug
core
new
priority-normal
- Dominant language
- Python
- Stars
- 6k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Description
 |
@twm reported |
|---|---|
| Trac ID | trac#10101 |
| Type | defect |
| Created | 2021-02-27 05:41:09Z |
The [[TwistedDevelopment]] wiki page outlines Twisted development. It has not been updated as the Tox configuration has churned, and is consequently giving bad advice, such as advising use of tox -e black to check code style.
Searchable metadata
trac-id__10101 10101
type__defect defect
reporter__twm twm
priority__normal normal
milestone__None None
branch__
branch_author__
status__new new
resolution__None None
component__core core
keywords__None None
time__1614404469481363 1614404469481363
changetime__1614404469481363 1614404469481363
version__None None
owner__None None
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 TwistedDevelopment wiki page and comparing its instructions with the current Tox configuration. Update the page so its development and code-style guidance matches the current configuration, including the outdated tox -e black advice; done means the instructions no longer recommend obsolete commands.
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
- 42/100