pattern=None when following documentation for load_tests and unittest.main()

Abierto
#55,427 10 comentarios 0 reacciones 1 asignado Ver en GitHub

@voidspace 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 11218
Nosy @mdickinson, @ezio-melotti, @merwok, @voidspace
Files
  • tester.py: demonstrating issue
  • issue11218_patternNone.patch: Treat pattern=None like ommitted pattern
    		•

    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/voidspace'
closed_at = None
created_at = <Date 2011-02-15.08:33:26.840>
labels = ['type-bug', 'library']
title = 'pattern=None when following documentation for load_tests and unittest.main()'
updated_at = <Date 2020-03-24.09:43:01.752>
user = 'https://bugs.python.org/gagern'

    bugs.python.org fields:

    activity = <Date 2020-03-24.09:43:01.752>
actor = 'Zbynek.Winkler'
assignee = 'michael.foord'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2011-02-15.08:33:26.840>
creator = 'gagern'
dependencies = []
files = ['20763', '25208']
hgrepos = []
issue_num = 11218
keywords = ['patch']
message_count = 10.0
messages = ['128579', '157891', '157935', '158219', '158232', '158234', '158235', '158236', '172463', '348881']
nosy_count = 9.0
nosy_names = ['mark.dickinson', 'gagern', 'vila', 'ezio.melotti', 'eric.araujo', 'michael.foord', 'Zbynek.Winkler', 'rik.poggi', 'Stefan Sullivan']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue11218'
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.