Documentation for PowerShell instructions
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- powershell, python
- Domain
- documentation, operating-systems
Research direction
The issue does not name a documentation file, section, or test. Start by locating the PowerShell instructions in CPython's Windows documentation and clarify the intended coverage from linked issue 33345. Done means the requested instructions are documented in the appropriate section.
Written by the indexing model from the issue text.
Description
| BPO | 33345 |
|---|---|
| Nosy | @pfmoore, @tjguk, @zware, @zooba, @stevepiercy |
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 2018-04-24.07:44:04.024>
labels = ['3.8', 'type-feature', '3.7', 'OS-windows', 'docs']
title = 'Documentation for PowerShell instructions'
updated_at = <Date 2018-04-25.11:05:07.981>
user = 'https://github.com/stevepiercy'
bugs.python.org fields:
activity = <Date 2018-04-25.11:05:07.981>
actor = 'stevepiercy'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Windows']
creation = <Date 2018-04-24.07:44:04.024>
creator = 'stevepiercy'
dependencies = []
files = []
hgrepos = []
issue_num = 33345
keywords = []
message_count = 2.0
messages = ['315690', '315722']
nosy_count = 6.0
nosy_names = ['paul.moore', 'tim.golden', 'docs@python', 'zach.ware', 'steve.dower', 'stevepiercy']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue33345'
versions = ['Python 3.6', 'Python 3.7', 'Python 3.8']
- 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 65/100
qgis/QGIS-Documentation#11275 ·
-
bug priority:normal ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
OpenHands/extensions#626 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
CSCfi/sd-search-api#39 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
StevenBlack/hosts#3255 ·