In Python 3.6, it takes longer to read a file if there are line breaks. If I have two files, one with line breaks and one without lines breaks (but otherwise they have the same
When you open a file in Python in text mode (the default), it uses what it calls "universal newlines" (introduced with PEP 278, but somewhat changed later with the release of Python 3). What universal newlines means is that regardless of what kind of newline characters are used in the file, you'll see only \n
in Python. So a file containing foo\nbar
would appear the same as a file containing foo\r\nbar
or foo\rbar
(since \n
, \r\n
and \r
are all line ending conventions used on some operating systems at some time).
The logic that provides that support is probably what causes your performance differences. Even if the \n
characters in the file are not being transformed, the code needs to examine them more carefully than it does non-newline characters.
I suspect the performance difference you see will disappear if you opened your files in binary mode where no such newline support is provided. You can also pass a newline
parameter to open
in Python 3, which can have various meanings depending on exactly what value you give. I have no idea what impact any specific value would have on performance, but it might be worth testing if the performance difference you're seeing actually matters to your program. I'd try passing newline=""
and newline="\n"
(or whatever your platform's conventional line ending is).