[issue7262] codecs.open() + eol (windows)

analyst added the comment: Hi, I am new to Python Development. I would like to propose a patch for this issue. -- keywords: +patch nosy: +analyst Added file: http://bugs.python.org/file34309/7262.patch ___ Python tracker

[issue7262] codecs.open() + eol (windows)

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue7262] codecs.open() + eol (windows)

Changes by Serhiy Storchaka : -- components: +Documentation -Library (Lib) keywords: +easy stage: -> needs patch versions: +Python 2.7, Python 3.3, Python 3.4 -Python 2.6 ___ Python tracker

[issue7262] codecs.open() + eol (windows)

Mark Lawrence added the comment: The docs still read the same. Would someone in the know like to propose a doc patch please. -- nosy: +BreamoreBoy ___ Python tracker ___ ___

[issue7262] codecs.open() + eol (windows)

Marc-Andre Lemburg added the comment: Amaury Forgeot d'Arc wrote: > > Amaury Forgeot d'Arc added the comment: > > The docs say:: > Files are always opened in binary mode, even if no binary mode was > specified. This is done to avoid data loss due to encodings using > 8-bit values. This

[issue7262] codecs.open() + eol (windows)

Amaury Forgeot d'Arc added the comment: The docs say:: Files are always opened in binary mode, even if no binary mode was specified. This is done to avoid data loss due to encodings using 8-bit values. This means that no automatic conversion of '\n' is done on reading and writing. But t

[issue7262] codecs.open() + eol (windows)

New submission from shamilbi : different eol when writing to fp = codecs.open(.., 'w', 'cp866') (windows, python-2.6.4) def write(fp): fp.write("""\ a """) # eol=0d0a (windows, python-2.6.4) with open('0d0a.tmp', 'w') as fp: write(fp) # eol=0d0a (windows, python-2.6.4) with codecs.open