Windows launcher version lookup flawed

Open
#78,323 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
documentation, operating-systems

Research direction

Start by reading the original BPO issue 34142 and the Windows launcher documentation; no specific file or test is named in the issue. Determine what version lookup behavior is considered flawed and which documentation needs correction, then verify that the resulting text accurately explains the intended lookup behavior.

Written by the indexing model from the issue text.

Description

docs OS-windows type-feature
BPO 34142
Nosy @pfmoore, @tjguk, @zware, @eryksun, @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 2018-07-18.02:09:34.963>
labels = ['3.8', '3.9', '3.10', 'type-feature', 'OS-windows', 'docs']
title = 'Windows launcher version lookup flawed'
updated_at = <Date 2021-03-27.04:50:19.776>
user = 'https://bugs.python.org/LarryZA'

bugs.python.org fields:

activity = <Date 2021-03-27.04:50:19.776>
actor = 'eryksun'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Windows']
creation = <Date 2018-07-18.02:09:34.963>
creator = 'LarryZA'
dependencies = []
files = []
hgrepos = []
issue_num = 34142
keywords = []
message_count = 4.0
messages = ['321855', '321858', '321859', '321861']
nosy_count = 7.0
nosy_names = ['paul.moore', 'tim.golden', 'docs@python', 'zach.ware', 'eryksun', 'steve.dower', 'LarryZA']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue34142'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']

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.