winreg SetValue(Ex) should mention integer as an acceptable value

Open
#86,184 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Locate the winreg documentation for SetValue and SetValueEx; the issue identifies the needed wording change but names no file or test. Done means the documentation explicitly mentions integer values as acceptable, with the existing pull requests indicating that work is already underway.

Written by the indexing model from the issue text.

Description

3.10 3.8 (EOL) 3.9 (EOL) docs OS-windows type-feature
BPO 42018
Nosy @pfmoore, @tjguk, @zware, @serhiy-storchaka, @zooba, @kainjow
PRs
  • python/cpython#22671
  • 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 2020-10-12.16:21:08.662>
    labels = ['3.8', '3.9', '3.10', 'type-feature', 'OS-windows', 'docs']
    title = 'winreg SetValue(Ex) should mention integer as an acceptable value'
    updated_at = <Date 2020-10-12.18:08:05.560>
    user = 'https://github.com/kainjow'
    

    bugs.python.org fields:

    activity = <Date 2020-10-12.18:08:05.560>
    actor = 'serhiy.storchaka'
    assignee = 'docs@python'
    closed = False
    closed_date = None
    closer = None
    components = ['Documentation', 'Windows']
    creation = <Date 2020-10-12.16:21:08.662>
    creator = 'kwojniak_box'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 42018
    keywords = ['patch']
    message_count = 1.0
    messages = ['378508']
    nosy_count = 8.0
    nosy_names = ['paul.moore', 'tim.golden', 'docs@python', 'python-dev', 'zach.ware', 'serhiy.storchaka', 'steve.dower', 'kwojniak_box']
    pr_nums = ['22671']
    priority = 'normal'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue42018'
    versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']
    

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