This project is a fork from the original python-patch project.
As any other project, bugs are common during the development process, the combination of issues + pull requests are able to keep the constant improvement of a project. However, both community and author need to be aligned. When users, developers, the community, needs a fix which are important for their projects, but there is no answer from the author, or the time for response is not enough, then the most plausible way is forking and continuing a parallel development.
That's way we forked the original and accepted most of PRs waiting for review since jun/2019 (5 months from now).
Things that don't work out of the box:
Download patch_ng.py and run it with Python. It is a self-contained module without external dependencies.
patch_ng.py diff.patch
You can also run the .zip file.
python patch-ng-1.17.zip diff.patch
patch_ng.py is self sufficient. You can copy it into your repository
and use it from here. This setup will always be repeatable. But if
you need to add patch module as a dependency, make sure to use strict
specifiers to avoid hitting an API break when version 2 is released:
pip install "patch-ng"
FAQs
Library to parse and apply unified diffs.
We found that patch-ng demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PyPI confirms no security flaws were exploited in the Ultralytics supply chain attack and highlights improvements for safer package publishing.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.