Facundo Batista <[EMAIL PROTECTED]> added the comment: I took a look at it...
It's not as not-complicated as I original thought. The way would be to adapt the Py_UniversalNewlineFread() function to *not* process the normal separators (like \n or \r), but the passed one. A critical point would be to handle more-than-1-byte characters... I concur with Nick that this would better suited for Py3k. So, I'm stepping down from this, and flagging it for that version. ---------- assignee: facundobatista -> versions: +Python 3.0 _____________________________________ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1152248> _____________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
