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

Ouverte
#62,491 21 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
25/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
python
Domaine
backend

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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']

    Langage dominant
    Python
    Étoiles
    77.2k
    Forks
    36k
    Merge moyen
    1 j 9 h
    PR mergées (30 j)
    558

    Guide de contribution

    Ouvrir le guide de contribution

    Par où commencer

    1. Lisez l'issue en entier, puis le guide de contribution du projet.
    2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
    3. Forkez le dépôt et travaillez sur une branche.
    4. Ouvrez une pull request qui référence le numéro de l'issue.

    Autres issues de python/cpython

    Toutes les issues de python/cpython

    Issues similaires

    Plus d'issues Python

    Recevez les nouvelles issues par e-mail

    Un résumé court des issues GitHub adaptées aux débutants.