EOL fixer script
What the script does
The script goes through a directory structure and fixes non-native EOL endings in non-binary files. So the windows line endings are gone if you work on linux (and probably vice versa, though I didn’t try).
Numerous people forget to set native EOL line endings by default in their main svn config file (see zope’s svn explanation why this is something you need to do).
The script sets the related svn property eol-style to native when not set yet.
History and origin
Original script (and thus 99% of the functionality) is from Holger Krekel from the pypy project.
A couple of years ago I got a script from Guido Wesdorp for cleaning up EOL styles in svn. I’ve long kept a private (modified) copy of that file and only later found out that it was from the pypy project: http://codespeak.net/pypy/dist/pypy/tool/fixeol .
Some changes to the original script:
Couple of extra file extensions that are checked (like .zcml and .ini files and also _tmpl files like in paster skeletons).
Some code cleanup and optimisation.
Added a setup.py and a console_scripts entry point to make it easy_installable.
Changelog
1.1 (2010-05-18)
Also treating html, rst, dtml, css and js as textual files.
1.0.2 (2009-11-25)
Fixed setup.py so that python script is found.
Added MANIFEST.in to fix source distribution on pypi.
Updated readme, acknowledging Holger Krekel as original author after asking around on #pypy in irc.
0.1 (2009-11-25)
Cleaned up my copy of the original fixeol script and made it easy_installable.
Metadata
Release files for eolfixer 1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| eolfixer-1.1.tar.gz | 3.7 kB | Without provenance | Details for eolfixer-1.1.tar.gz |
Release files / eolfixer-1.1.tar.gz
| Download URL | eolfixer-1.1.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e27a16e58248c8cda59b30f026e3cdac4191b914c96d60ac33f1b3664a1f7f0f
|
|
BLAKE2b-256 checksum How to use checksums |
d15b2261a261b3c9f6a5904c1106bdce913716f2b954692cb75bd3e73f96cd20
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for eolfixer 1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.