http://bugs.grommit.com/show_bug.cgi?id=349
------- Comment #3 from steve at borho.org 2007-10-08 20:13 PDT ------- (In reply to comment #2) > (In reply to comment #1) > > This would be good to fix for generality, but it's not important for the > > Solaris SCM migration work that gpyfm was created for. Dropping to P4. > > > > Mike, did you verify that this *only* happens on windows? > > If gpyfm transforms line-endings to \n on any platform, from a certain point > of > view it is making undesirable (and hard to notice) change to its data, and is, > in effect, corrupting its output. > I did verify that the behavior on Linux is correct, the EOL style of the output file matches that of the input files (at least for unix and dos style end of lines). I suspect that python on windows is somehow "hiding" the EOL style of the input files and gpyfm is unaware of the implicit change. -- Configure bugmail: http://bugs.grommit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
