python / python/cpython

IDLE: Don't touch .idlerc when testing.

Abierto
#75,052 7 comentarios 0 reacciones 1 asignado Ver en GitHub

@terryjreedy ya está trabajando en esto.

Desde el 20/3/2019.

tests topic-IDLE type-bug
Lenguaje dominante
Python
Estrellas
77.2k
Forks
36k
Métricas de merge de PR
Métricas de PR pendientes

Descripción

BPO 30869
Nosy @terryjreedy, @vstinner, @mlouielu
PRs
  • python/cpython#2614
  • Dependencies
  • bpo-8231: Unable to run IDLE without write-access to home directory
  • bpo-15862: IDLE: startup problem when HOME does not exist
  • 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 2017-07-07.03:21:06.107>
    labels = ['3.8', 'expert-IDLE', 'type-bug', '3.7']
    title = "IDLE: Don't touch .idlerc when testing."
    updated_at = <Date 2019-03-20.19:35:54.948>
    user = 'https://github.com/mlouielu'
    

    bugs.python.org fields:

    activity = <Date 2019-03-20.19:35:54.948>
    actor = 'terry.reedy'
    assignee = 'terry.reedy'
    closed = False
    closed_date = None
    closer = None
    components = ['IDLE']
    creation = <Date 2017-07-07.03:21:06.107>
    creator = 'louielu'
    dependencies = ['8231', '15862']
    files = []
    hgrepos = []
    issue_num = 30869
    keywords = []
    message_count = 7.0
    messages = ['297856', '297858', '297874', '297875', '297917', '297985', '338506']
    nosy_count = 3.0
    nosy_names = ['terry.reedy', 'vstinner', 'louielu']
    pr_nums = ['2614']
    priority = 'normal'
    resolution = None
    stage = 'needs patch'
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue30869'
    versions = ['Python 3.7', 'Python 3.8']
    

    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.

    Evaluación

    Este issue todavía no se ha evaluado.

    Recibe los nuevos issues en tu correo

    Un resumen breve de issues de GitHub para principiantes.