[doc] sys.setprofile / sys.getprofile asymetry

Open
#69,912 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Start by reviewing BPO issue 25726 and linked PR gh-143338, then compare the documentation for sys.setprofile and sys.getprofile. Confirm what asymmetry remains and ensure the documented behavior is consistent; the existing pull request indicates this work may already be underway.

Written by the indexing model from the issue text.

Description

3.11 3.12 3.13 docs easy type-bug
BPO 25726
Nosy @birkenfeld, @stefanseefeld

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-11-24.23:04:27.109>
labels = ['3.11', 'type-bug', '3.9', '3.10', 'docs']
title = '[doc] sys.setprofile / sys.getprofile asymetry'
updated_at = <Date 2021-12-07.15:35:18.401>
user = 'https://github.com/stefanseefeld'

bugs.python.org fields:

activity = <Date 2021-12-07.15:35:18.401>
actor = 'iritkatriel'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2015-11-24.23:04:27.109>
creator = 'stefan'
dependencies = []
files = []
hgrepos = []
issue_num = 25726
keywords = []
message_count = 2.0
messages = ['255301', '260234']
nosy_count = 3.0
nosy_names = ['georg.brandl', 'stefan', 'docs@python']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue25726'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']

Linked PRs
  • gh-143338
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.