Éric Araujo <mer...@netwok.org> added the comment: > I found the problem - it's in packaging.util.write_record_file. We have two functions that write RECORD files; I’ve opened a report to kill one.
> The file passed to csv.writer should be opened with newline=''. How will we port this to 2.x? > I don't expect the test will catch the issue except on Windows... Do you mean that the test will fail or be a no-op on other OSes? We can mark it as Windows-specific (@unittest.skipIf(sys.platform != 'win32', 'test only relevant on win32')) or just let it run if it’s harmless. The important point is: does it fail before the fix, does it pass after? ---------- assignee: tarek -> eric.araujo dependencies: +Remove duplicate definition of write_record_file versions: +3rd party _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13175> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
