Patchit
Patchit is an MIT Licensed unified diff parsing and merge tool written in Python for anyone who needs a finer grain of control over unified diff content and to merge the diff with an arbitrary stream of lines.
Motivation
The motivation for this package arose from the
overwhelming complexity of other patching tools written in Python,
their absence from the PyPI,
their inability to inspect the unified diff content and
missing support to merge the patch with an arbitrary stream of lines.
Installation
To install patchit just run from the root of the project:
$ python setup.py installTesting
Tests are located at the tests.py file. In order to test your new contribution to patchit just run from your shell
$ python setup.py testContribute
Unfortunately, I wasn’t able to make it much better myself. Therefore I’m asking anyone who is interested in a patch functionality for Python to improve this package and hand in patches by mail or pull requests.
The preferred method of development is a test driven approach and following the nvie git flow branching model. Please be so kind to bear these things in mind when handing in improvements. Thank you very much.
1 maintainer
Metadata
1 maintainer
Release files for patchit 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 |
|---|---|---|---|---|
| patchit-1.1.tar.gz | 6.1 kB | Without provenance | Details for patchit-1.1.tar.gz |
Release files / patchit-1.1.tar.gz
| Download URL | patchit-1.1.tar.gz |
|---|---|
| Size | 6.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8d226d21fb81eb060cde376139b8cdd1c248f69eee22def749fb1c0ebae0440e
|
|
BLAKE2b-256 checksum How to use checksums |
6436f1b43d833af7087ce6e5c25f63ed0db936e82c77cd24692529bc786624f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for patchit 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.
