[issue7720] Errors in tests and C implementation of raw FileIO

R. David Murray added the comment: Looks to me like this issue is out of date. -- nosy: +r.david.murray resolution: -> out of date stage: test needed -> committed/rejected status: open -> closed ___ Python tracker

[issue7720] Errors in tests and C implementation of raw FileIO

STINNER Victor added the comment: IOTest.test_destructor() is already fixed in Python trunk (future 2.7) by r73394 (Issue #6215: backport the 3.1 io lib). I don't think that it would be possible to backport the 3.1 io lib in Python 2.6. Would it possible to backport only the io tests? --

[issue7720] Errors in tests and C implementation of raw FileIO

Changes by Ezio Melotti : -- nosy: +benjamin.peterson, pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue7720] Errors in tests and C implementation of raw FileIO

Changes by Brian Curtin : -- components: +Tests priority: -> normal stage: -> test needed type: -> behavior ___ Python tracker ___ _

[issue7720] Errors in tests and C implementation of raw FileIO

Pascal Chambon added the comment: Hum, it seems that in python2.6, the C API for PyArg_ParseTuple isn't yet ready for bytes and bytearrays, is it ? "y"-like argument parsers don't exist, so I guess we can't easily patch the C api on this, only tests (replacing "xxx" by b"xxx")... --

[issue7720] Errors in tests and C implementation of raw FileIO

New submission from Pascal Chambon : My own fileio implementation fails against the latests versions of the io test suite, under python2.6, because these now require FileIO objects to accept unicode strings in their write methods, whereas the doc mentions raw streams only deal with bytes/bytea