Rename module to patch_ng

Signed-off-by: Uilian Ries <uilianries@gmail.com>

Author: uilianries

README.md

@@ -39,18 +39,18 @@ Things that don't work out of the box:
 
 ### Usage
 
-Download **patch.py** and run it with Python. It is a self-contained
+Download **patch_ng.py** and run it with Python. It is a self-contained
 module without external dependencies.
 
-    patch.py diff.patch
+    patch_ng.py diff.patch
 
 You can also run the .zip file.
 
-    python patch-1.17.zip diff.patch
+    python patch-ng-1.17.zip diff.patch
 
 ### Installation
 
-**patch.py** is self sufficient. You can copy it into your repository
+**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:

patch.py renamed to patch_ng.py

@@ -31,7 +31,7 @@ def get_requires(filename):
 def load_version():
     """Loads a file content"""
     filename = os.path.abspath(os.path.join(os.path.dirname(os.path.abspath(__file__)),
-                                            "patch.py"))
+                                            "patch_ng.py"))
     with open(filename, "rt") as version_file:
         content = version_file.read()
         version = re.search('__version__ = "([0-9a-z.-]+)"', content).group(1)
@@ -86,7 +86,7 @@ def load_version():
 
     # Alternatively, if you want to distribute just a my_module.py, uncomment
     # this:
-    py_modules=["patch"],
+    py_modules=["patch_ng"],
 
     # List run-time dependencies here.  These will be installed by pip when
     # your project is installed. For an analysis of "install_requires" vs pip's