sysconfig variables introduced by PEP-3149 are currently undocumented

Open
#63,716 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
30/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Start by reading PEP-3149 and the Python sysconfig documentation to identify the variables introduced there. Locate the relevant sysconfig documentation section, document the missing variables and their purpose, and verify that the documentation describes all PEP-3149 additions accurately.

Written by the indexing model from the issue text.

Description

docs topic-sysconfig type-feature
BPO 19517
Nosy @warsaw, @doko42

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 2013-11-07.09:42:49.996>
labels = ['type-feature', 'docs']
title = 'sysconfig variables introduced by PEP-3149 are currently undocumented'
updated_at = <Date 2013-11-07.09:42:49.996>
user = 'https://bugs.python.org/zaytsev'

bugs.python.org fields:

activity = <Date 2013-11-07.09:42:49.996>
actor = 'zaytsev'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2013-11-07.09:42:49.996>
creator = 'zaytsev'
dependencies = []
files = []
hgrepos = []
issue_num = 19517
keywords = []
message_count = 1.0
messages = ['202321']
nosy_count = 4.0
nosy_names = ['barry', 'doko', 'docs@python', 'zaytsev']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue19517'
versions = ['Python 3.3']

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.