Improve IDLE's "subprocess didn't make connection" message

Abierto
#69,700 20 comentarios 0 reacciones 1 asignado Ver en GitHub

@terryjreedy ya está trabajando en esto.

Desde el 13/6/2017.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

docs topic-IDLE type-feature
BPO 25514
Nosy @terryjreedy, @kbkaiser, @serwy, @roseman, @willingc
PRs
  • python/cpython#2177
  • python/cpython#2178
    		•

    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/terryjreedy'
closed_at = None
created_at = <Date 2015-10-29.20:47:20.690>
labels = ['easy', 'expert-IDLE', 'type-feature', '3.7', 'docs']
title = 'Improve IDLE\'s  "subprocess didn\'t make connection" message'
updated_at = <Date 2018-09-07.21:42:46.760>
user = 'https://github.com/roseman'

    bugs.python.org fields:

    activity = <Date 2018-09-07.21:42:46.760>
actor = 'terry.reedy'
assignee = 'terry.reedy'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'IDLE']
creation = <Date 2015-10-29.20:47:20.690>
creator = 'markroseman'
dependencies = []
files = []
hgrepos = []
issue_num = 25514
keywords = ['easy']
message_count = 17.0
messages = ['253693', '253694', '253695', '253704', '253705', '253706', '253745', '253833', '255578', '258498', '295369', '295937', '295950', '295972', '295975', '295977', '324800']
nosy_count = 7.0
nosy_names = ['terry.reedy', 'kbk', 'roger.serwy', 'markroseman', 'docs@python', 'willingc', 'lac']
pr_nums = ['2177', '2178']
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue25514'
versions = ['Python 3.6', 'Python 3.7']

    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.