[Zope3-dev] Failure to load functional test -test_datetimewidget.py

[Tim Peters]

[Dave Harris]
> ...
> The problem is not MS-DOS line endings.
>
> The problem is that each line ends with _two_ carriage returns
> followed by a newline.
>
> And I _know_ that's not normal.

That's usually a symptom of someone working on multiple platforms being
careless with their checkins.

Text files in the CVS repository should have plain \n line endings.

The CVS client on each platform is responsible for translating to (on
checkout) and from (on checkin) the native text file line end convention.

Seeing \r\r\n line ends usually happens like this:

1. The CVS repository contains plain \n line ends.
2. Someone checks out on Windows, and gets \r\n line ends locally.
3. They modify the files, and check them in *from* Linux.
4. The Linux CVS client doesn't do any translation, so the \r\n
   line endings end up in the CVS repository.
5. The next time someone checks out the file from Windows again,
   the \n is again translated to \r\n locally, leaving the
   local files with \r\r\n line ends.

This can be fixed from either Windows or Linux, but the proper fix varies by
platfom:  on Linux the files should be edited back to have plain \n line
ends again, or on Windows to \r\n again, and then checked in.