Do not rely on AC_RUN_IFELSE tests in the configury

Abierto
#58,532 8 comentarios 0 reacciones 1 asignado Ver en GitHub

@doko42 ya está trabajando en esto.

Desde el 15/3/2012.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

build
BPO 14324
Nosy @doko42
Files
  • long-long-format.diff: long-long-format.diff
  • computed-gotos.diff: computed-gotos.diff
  • buggy-getaddrinfo.diff: buggy-getaddrinfo.diff
  • profiling.diff
  • 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/doko42'
    closed_at = None
    created_at = <Date 2012-03-15.17:23:09.115>
    labels = ['build']
    title = 'Do not rely on AC_RUN_IFELSE tests in the configury'
    updated_at = <Date 2012-06-30.14:54:48.587>
    user = 'https://github.com/doko42'
    

    bugs.python.org fields:

    activity = <Date 2012-06-30.14:54:48.587>
    actor = 'python-dev'
    assignee = 'doko'
    closed = False
    closed_date = None
    closer = None
    components = ['Cross-Build']
    creation = <Date 2012-03-15.17:23:09.115>
    creator = 'doko'
    dependencies = []
    files = ['24869', '24871', '24876', '26218']
    hgrepos = []
    issue_num = 14324
    keywords = ['patch']
    message_count = 8.0
    messages = ['155918', '155928', '155934', '155935', '155945', '155947', '164383', '164384']
    nosy_count = 3.0
    nosy_names = ['doko', 'Arfrever', 'python-dev']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = None
    url = 'https://bugs.python.org/issue14324'
    versions = ['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.