[issue2491] io.open() handles errors differently on different platforms

Changes by Amaury Forgeot d'Arc [EMAIL PROTECTED]: -- resolution: - fixed status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2491 ___

[issue2491] io.open() handles errors differently on different platforms

Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment: Committed r65343: os.fdopen accepts the same parameters as io.open(). ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2491 ___

[issue2491] io.open() handles errors differently on different platforms

Antoine Pitrou [EMAIL PROTECTED] added the comment: I think the proposal to deprecate os.fdopen should be brought on python-3000. -- nosy: +pitrou ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2491

[issue2491] io.open() handles errors differently on different platforms

Benjamin Peterson [EMAIL PROTECTED] added the comment: What's the status of this? -- nosy: +benjamin.peterson ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2491 ___

[issue2491] io.open() handles errors differently on different platforms

Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment: With python3.0, os.fdopen() is a simple call to io.open(), which has these missing options. Maybe os.fdopen should be deprecated or removed, and replaced by io.open. Moreover, the comment in os.py is wrong: subprocess does not use fdopen

[issue2491] io.open() handles errors differently on different platforms

New submission from Neal Norwitz [EMAIL PROTECTED]: The attached file has a snapshot of the python.org homepage that was causing test_urllibnet to fail on some platforms (2 sparc, and ia64 at least), but not other platforms. This should be handled consistently. I don't know if there are really