Expose RegUnLoadKey in winreg

Open
#65,717 17 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
python
Domain
operating-systems

Research direction

Start by reviewing the linked winreg_unload_key.patch and the later issue21518*.patch files, along with the dependency on bpo-22080. Confirm how RegUnLoadKey should be exposed in winreg and what Windows-specific behavior the existing patches cover; done means the API is available through winreg with the required validation.

Written by the indexing model from the issue text.

Description

3.10 3.8 (EOL) 3.9 (EOL) OS-windows stdlib type-feature
BPO 21518
Nosy @loewis, @pfmoore, @tjguk, @PCManticore, @zware, @eryksun, @zooba
Dependencies
  • bpo-22080: Add windows_helper module helper
    		•
    Files
  • winreg_unload_key.patch
  • issue21518.patch
  • issue21518_1.patch
  • issue21518_2.patch
  • winreg_unload_key.patch
  • issue21518_2.patch
  • issue21518_3.patch
  • issue21518_4.patch: use context manager
  • issue21518_5.patch: Fix import error
  • issue21518_6.patch
    		•

    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 2014-05-17.17:12:40.482>
labels = ['3.8', '3.9', '3.10', 'type-feature', 'library', 'OS-windows']
title = 'Expose RegUnLoadKey in winreg'
updated_at = <Date 2021-03-12.17:38:28.317>
user = 'https://github.com/PCManticore'

    bugs.python.org fields:

    activity = <Date 2021-03-12.17:38:28.317>
actor = 'eryksun'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)', 'Windows']
creation = <Date 2014-05-17.17:12:40.482>
creator = 'Claudiu.Popa'
dependencies = ['22080']
files = ['35271', '35285', '35288', '35618', '35907', '37742', '37819', '37820', '38382', '38481']
hgrepos = []
issue_num = 21518
keywords = ['patch']
message_count = 17.0
messages = ['218708', '218709', '218757', '218758', '218764', '220463', '222433', '222471', '222472', '222583', '227580', '234180', '234487', '238052', '238078', '242266', '388542']
nosy_count = 7.0
nosy_names = ['loewis', 'paul.moore', 'tim.golden', 'Claudiu.Popa', 'zach.ware', 'eryksun', 'steve.dower']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue21518'
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.