codecs.open interprets FS, RS, GS as line ends

Abierto
#62,491 21 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
python
Área
backend

Línea de trabajo

Start by reviewing the codecs.open implementation and the linked PR #9711, then compare the provided codecs_splitlines.txt and str_splitlines.txt files with the reported behavior. Check the relevant Unicode and IO tests before changing anything; done means the line-ending behavior is covered by tests and matches the agreed interpretation without regressing codecs.open.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

docs stdlib topic-IO topic-unicode
BPO 18291
Nosy @malemburg, @doerwalter, @nascheme, @abalkin, @vstinner, @ezio-melotti, @bitdancer, @serhiy-storchaka, @tirkarthi
PRs
  • python/cpython#9711
    		•
    Files
  • codecs-io-example.py: Compare UTF-8 file reading time between io.open and codecs.open.
  • codecs_splitlines.txt
  • str_splitlines.txt: change str.splitlines to use only \r and \n
    		•

    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 = None
closed_at = None
created_at = <Date 2013-06-24.13:11:12.690>
labels = ['3.8', 'type-bug', '3.7', 'expert-unicode', 'expert-IO']
title = 'codecs.open interprets FS, RS, GS as line ends'
updated_at = <Date 2018-10-05.12:28:09.232>
user = 'https://bugs.python.org/wpk'

    bugs.python.org fields:

    activity = <Date 2018-10-05.12:28:09.232>
actor = 'lemburg'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Unicode', 'IO']
creation = <Date 2013-06-24.13:11:12.690>
creator = 'wpk'
dependencies = []
files = ['30688', '47851', '47852']
hgrepos = []
issue_num = 18291
keywords = []
message_count = 21.0
messages = ['191758', '191769', '191778', '191784', '191848', '191849', '191853', '192118', '192123', '192280', '327095', '327096', '327098', '327100', '327101', '327104', '327112', '327125', '327127', '327129', '327134']
nosy_count = 10.0
nosy_names = ['lemburg', 'doerwalter', 'nascheme', 'belopolsky', 'vstinner', 'ezio.melotti', 'r.david.murray', 'serhiy.storchaka', 'wpk', 'xtreak']
pr_nums = ['9711']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue18291'
versions = ['Python 2.7', 'Python 3.6', 'Python 3.7', 'Python 3.8']

    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.