IO libary have some error

[kaka]

BPO	7235
Nosy	@pitrou
Files	unnamed unnamed

^{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 = <Date 2009-10-29.13:18:26.960>
created_at = <Date 2009-10-29.13:15:49.545>
labels = ['invalid', 'library']
title = 'IO libary have some error'
updated_at = <Date 2009-10-29.13:38:19.688>
user = 'https://bugs.python.org/kaka'

bugs.python.org fields:

activity = <Date 2009-10-29.13:38:19.688>
actor = 'kaka'
assignee = 'none'
closed = True
closed_date = <Date 2009-10-29.13:18:26.960>
closer = 'pitrou'
components = ['Library (Lib)']
creation = <Date 2009-10-29.13:15:49.545>
creator = 'kaka'
dependencies = []
files = ['15226', '15227']
hgrepos = []
issue_num = 7235
keywords = []
message_count = 3.0
messages = ['94663', '94664', '94668']
nosy_count = 2.0
nosy_names = ['pitrou', 'kaka']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue7235'
versions = []

[kaka]

The parameter 'newline' in os.open() functiion in the condition of
input could ought to be set to any character.But if I set anythin
else '','\n','\r\n',and '\r',there will be a error raise.This is maybe
a bug in this libary.

[pitrou]

It's by design. If you want to split on arbitrary characters, use the
split() method on string and bytes objects.

[kaka]

But sometimes the content of file in too large to put into memory,So I need a tool to solve this problem.Just only modify a subclass in Io could solve this problem.To me ,it is difficult,but simple to your team!

2009-10-29

李澎鹏

发件人： Antoine Pitrou
发送时间： 2009-10-29 21:18:31
收件人： lpp1985
抄送：
主题： [bpo-7235] IO libary have some error

Antoine Pitrou <pitrou@free.fr> added the comment:
It's by design. If you want to split on arbitrary characters, use the
split() method on string and bytes objects.
----------
nosy: +pitrou
resolution: -> invalid
status: open -> closed

---

Python tracker <report@bugs.python.org>
<http://bugs.python.org/issue7235\>

---