Usage

pypatch apply [libarary.package] custom_diff.patch

As a part of the work flow:

c:\project\pip install django

c:\project\pip install pypatch

c:\project\pypatch apply django.contrib.auth c:\project\patches\my_auth_fix.patch

How it works

PyPatch applies patches to files relative to the root directory of the named package. So it does have to be installed into the target environment.

For example, if the django package was installed to “C:Python27Libsite-packagesdjango” and you needed to patch the auth contrib package (django.contrib.auth), your command might look like

pypatch apply django.contrib.auth c:\project\patches\my_auth_fix.patch"

and the files named in my_auth_fix.patch would use relative pathing from the package directory:

--- models.py 2013-05-06 15:12:14.212220100 -0700

+++ models.py 2013-05-06 14:36:20.535220100 -0700

If you used

`pypatch apply django.contrib c:\project\patches\my_auth_fix.patch`

instead, your diff patch would read

--- auth/models.py 2013-05-06 15:12:14.212220100 -0700

+++ auth/models.py 2013-05-06 14:36:20.535220100 -0700

Build

To build the distributable python package, run ‘sdist’ from the Project Root Directory. Recommended: setting the output directory to our Libraries folder

sdist --dist-dir="C:\outputdir"

This will build the zipped python package that can be installed via pip or easy_install

Other

Information on the Unified Diff format can be found at https://www.gnu.org/software/diffutils/manual/html_node/Unified-Format.html#Unified-Format

The MIT License (MIT)

Copyright (c) 2013 sitkatech

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.