Expose RegUnLoadKey in winreg

Abierto
#65,717 17 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
python
Área
operating-systems

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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']

    Lenguaje dominante
    Python
    Estrellas
    77.2k
    Forks
    36k
    Merge medio
    1 d 9 h
    PR fusionados (30 d)
    558

    Guía de contribución

    Abrir la guía de contribución

    Primeros pasos

    1. Lee el issue completo y luego la guía de contribución del proyecto.
    2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
    3. Haz un fork del repositorio y trabaja en una rama.
    4. Abre un pull request que haga referencia al número del issue.

    Más de python/cpython

    Todos los issues de python/cpython

    Issues similares

    Más issues de Python

    Recibe los nuevos issues en tu correo

    Un resumen breve de issues de GitHub para principiantes.