Using Windows doc should list service packs needed to install

Open
#69,518 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python

Research direction

The issue points to the Windows installation documentation but names no file or service-pack list. Locate the relevant Windows installation guide, verify which service packs are required, and consider the work done when those requirements are clearly documented.

Written by the indexing model from the issue text.

Description

docs OS-windows type-feature
BPO 25331
Nosy @pfmoore, @tjguk, @zware, @zooba

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 2015-10-07.10:36:38.071>
labels = ['type-feature', 'OS-windows', 'docs']
title = 'Using Windows doc should list service packs needed to install'
updated_at = <Date 2015-10-09.18:55:55.408>
user = 'https://bugs.python.org/lac'

bugs.python.org fields:

activity = <Date 2015-10-09.18:55:55.408>
actor = 'terry.reedy'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Windows']
creation = <Date 2015-10-07.10:36:38.071>
creator = 'lac'
dependencies = []
files = []
hgrepos = []
issue_num = 25331
keywords = []
message_count = 1.0
messages = ['252460']
nosy_count = 6.0
nosy_names = ['paul.moore', 'tim.golden', 'docs@python', 'zach.ware', 'steve.dower', 'lac']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue25331'
versions = ['Python 3.5', 'Python 3.6']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.