This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jaraco
Recipients eric.araujo, jaraco, orsenthil, pitrou
Date 2011-01-29.20:04:40
SpamBayes Score 4.3252883e-05
Marked as misclassified No
Message-id <A2A66F57550F50449EC38E10458E27FF059BC989BC@VA3DIAXVS381.RED001.local>
In-reply-to <1296322692.45.0.712653390955.issue10639@psf.upfronthosting.co.za>
Content
That's great that reindent works in your environment, but that's no help in my environment.

Here's the use case: We have a software package developed in Unix and with Unix LF line endings. The code base may also contain files with CRLF line endings (I can't be certain).

I'm developing in Windows (which includes reindent.py installed by default). I'd like to use that tool to reindent the code base without munging the line endings. I can't do this without first modifying reindent.py or using another tool to convert the line endings afterword (at which point I don't know if the Windows line endings were created by reindent.py or were there natively).

If someone wants the line endings normalized on their code base, they should use another tool (or possibly an option to reindent.py), but there's definitely a case for using reindent.py without altering the line endings.
History
Date User Action Args
2011-01-29 20:04:41jaracosetrecipients: + jaraco, orsenthil, pitrou, eric.araujo
2011-01-29 20:04:40jaracolinkissue10639 messages
2011-01-29 20:04:40jaracocreate