shutil.copytree error handling non-standard and partially broken

Abierto
#52,217 8 comentarios 0 reacciones 1 asignado Ver en GitHub

@merwok ya está trabajando en esto.

Desde el 14/6/2011.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

stdlib type-bug
BPO 7969
Nosy @terryjreedy, @tarekziade, @merwok, @dhduvall
Files
  • shutil_copytree_doc.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 = 'https://github.com/merwok'
    closed_at = None
    created_at = <Date 2010-02-19.22:04:16.853>
    labels = ['type-bug', 'library']
    title = 'shutil.copytree error handling non-standard and partially broken'
    updated_at = <Date 2011-06-15.13:40:35.619>
    user = 'https://bugs.python.org/swalker'
    

    bugs.python.org fields:

    activity = <Date 2011-06-15.13:40:35.619>
    actor = 'eric.araujo'
    assignee = 'eric.araujo'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2010-02-19.22:04:16.853>
    creator = 'swalker'
    dependencies = []
    files = ['22026']
    hgrepos = []
    issue_num = 7969
    keywords = ['patch']
    message_count = 8.0
    messages = ['99597', '103685', '136061', '136268', '138083', '138225', '138325', '138367']
    nosy_count = 6.0
    nosy_names = ['terry.reedy', 'tarek', 'eric.araujo', 'dhduvall', 'swalker', 'lokare.ameya']
    pr_nums = []
    priority = 'normal'
    resolution = 'accepted'
    stage = None
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue7969'
    versions = ['Python 2.7', 'Python 3.2', 'Python 3.3']
    

    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.