[Python-Dev] CRLF problems in repo

[Stephen J. Turnbull]

Rustom Mody writes:

 > Can submit a bug-report if it looks ok

Thanks for the post.  IMO this should have gone directly to the
tracker because (1) you have some support for the idea that at least
some of these are unintentional, and therefore candidates for
alignment with the rest of the code, (2) the nature of the issue is
that it's a mixed bag that is going to need to be addressed line by
line, and the tracker is much better at doing that (you can piece each
file out to a separate issue, and have a "master issue" that blocks on
each individual issue), and (3) these are "easy bugs", so that new
contributors (eg, your students) could do the actual patches while
discussion of the need is ongoing.

YMMV, of course, but (2) and (3) are generic criteria for deciding
whether to post or to use the tracker, so I decided to mention them.