To put in an argument each way -- I now recognize that the PEP one
gets when looking up "universal newline python" has the necessary
info. I saw but did not recognize over the weekend. So one argument is
that there's no good reason to risk breaking old defaults, mostly
users will be able to solve it themselves.
...*but*, on the other hand:
I've checked that more than one Office 2008 install writes files
csv2rec can't open without the 'U' flag,
and I'm trying to persuade various colleagues that they can move
from Excel calculations to Python gradually,
and they aren't going to expect line-ending problems.
So I guess I see a backwards compatibility problem balanced against a
forward evangelizing problem.
&C
On Jan 29, 2009, at 8:18 AM, Jeff Whitaker wrote:
> John Hunter wrote:
>> On Wed, Jan 28, 2009 at 2:11 PM, Christopher Barker
>> <chris.bar...@noaa.gov> wrote:
>>
>>
>>> But why the heck not? and according to the OP, Excel does create
>>> such files.
>>>
>>> Personally, I try to ALWAYS use 'U' when opening text files -- it
>>> can
>>> save headaches, and I see no downside. It really should be the
>>> default
>>> -- it's not, because the default was always text, but that was the
>>> same
>>> as binary on *nix -- so there is a lot of *nix code out there
>>> opening
>>> binary files without the 'b' flag. So we couldn't change the default
>>> back in 2002, it would have broken a LOT of code.
>>>
>>
>> Fair enough -- changed on the trunk in r6845
>>
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users
