This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author susurrus
Recipients r.david.murray, susurrus, v+python
Date 2013-02-01.19:39:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1359747596.25.0.977820241499.issue17083@psf.upfronthosting.co.za>
In-reply-to
Content
While my original description of this issue discussed arbitrary strings, I'd like to limit the scope of this issue down to just supporting the newline parameter to builtin.open() for binary files, just as it's supported for regular files. This adds no real new functionality, just makes the treatment of the concept of a "line" consistent between binary files and regular text files, since that concept *does* exist in many cases in binary files.

Given that everyone here seems to think this is at least reasonable at this point, what would the next step be given this is somewhere between a library fix and a feature addition? I haven't contributed to Python before, but the developer FAQ mentions either python-ideas or a PEP, or should this move right towards a patch?
History
Date User Action Args
2013-02-01 19:39:56susurrussetrecipients: + susurrus, v+python, r.david.murray
2013-02-01 19:39:56susurrussetmessageid: <1359747596.25.0.977820241499.issue17083@psf.upfronthosting.co.za>
2013-02-01 19:39:56susurruslinkissue17083 messages
2013-02-01 19:39:56susurruscreate