|
| 1 | +"""A setuptools based setup module. |
| 2 | +See: |
| 3 | +https://packaging.python.org/en/latest/distributing.html |
| 4 | +https://github.com/pypa/sampleproject |
| 5 | +""" |
| 6 | + |
| 7 | +# Always prefer setuptools over distutils |
| 8 | +import re |
| 9 | +import os |
| 10 | +from setuptools import setup, find_packages |
| 11 | +# To use a consistent encoding |
| 12 | +from codecs import open |
| 13 | + |
| 14 | + |
| 15 | +here = os.path.abspath(os.path.dirname(__file__)) |
| 16 | + |
| 17 | +# Get the long description from the README file |
| 18 | +with open(os.path.join(here, 'README.md'), encoding='utf-8') as f: |
| 19 | + long_description = f.read() |
| 20 | + |
| 21 | + |
| 22 | +def get_requires(filename): |
| 23 | + requirements = [] |
| 24 | + with open(filename) as req_file: |
| 25 | + for line in req_file.read().splitlines(): |
| 26 | + if not line.strip().startswith("#"): |
| 27 | + requirements.append(line) |
| 28 | + return requirements |
| 29 | + |
| 30 | + |
| 31 | +def load_version(): |
| 32 | + """Loads a file content""" |
| 33 | + filename = os.path.abspath(os.path.join(os.path.dirname(os.path.abspath(__file__)), |
| 34 | + "patch.py")) |
| 35 | + with open(filename, "rt") as version_file: |
| 36 | + content = version_file.read() |
| 37 | + version = re.search('__version__ = "([0-9a-z.-]+)"', content).group(1) |
| 38 | + return version |
| 39 | + |
| 40 | +setup( |
| 41 | + name='patch-ng', |
| 42 | + # Versions should comply with PEP440. For a discussion on single-sourcing |
| 43 | + # the version across setup.py and the project code, see |
| 44 | + # https://packaging.python.org/en/latest/single_source_version.html |
| 45 | + version=load_version(), |
| 46 | + |
| 47 | + # This is an optional longer description of your project that represents |
| 48 | + # the body of text which users will see when they visit PyPI. |
| 49 | + # |
| 50 | + # Often, this is the same as your README, so you can just read it in from |
| 51 | + # that file directly (as we have already done above) |
| 52 | + # |
| 53 | + # This field corresponds to the "Description" metadata field: |
| 54 | + # https://packaging.python.org/specifications/core-metadata/#description-optional |
| 55 | + long_description=long_description, # Optional |
| 56 | + |
| 57 | + description='Library to parse and apply unified diffs.', |
| 58 | + |
| 59 | + # The project's main homepage. |
| 60 | + url='https://github.com/conan-io/python-patch', |
| 61 | + |
| 62 | + # Author details |
| 63 | + author='Conan.io', |
| 64 | + author_email='info@conan.io', |
| 65 | + |
| 66 | + # Choose your license |
| 67 | + license='MIT', |
| 68 | + |
| 69 | + # See https://pypi.python.org/pypi?%3Aaction=list_classifiers |
| 70 | + classifiers=[ |
| 71 | + 'Development Status :: 5 - Production/Stable', |
| 72 | + 'Intended Audience :: Developers', |
| 73 | + 'Topic :: Software Development :: Build Tools', |
| 74 | + 'License :: OSI Approved :: MIT License', |
| 75 | + 'Programming Language :: Python :: 2', |
| 76 | + 'Programming Language :: Python :: 2.7', |
| 77 | + 'Programming Language :: Python :: 3', |
| 78 | + ], |
| 79 | + |
| 80 | + # What does your project relate to? |
| 81 | + keywords=['patch', 'parse', 'diff', 'strip', 'diffstat'], |
| 82 | + |
| 83 | + # You can just specify the packages manually here if your project is |
| 84 | + # simple. Or you can use find_packages(). |
| 85 | + # packages=find_packages(exclude=['tests']), |
| 86 | + |
| 87 | + # Alternatively, if you want to distribute just a my_module.py, uncomment |
| 88 | + # this: |
| 89 | + py_modules=["patch"], |
| 90 | + |
| 91 | + # List run-time dependencies here. These will be installed by pip when |
| 92 | + # your project is installed. For an analysis of "install_requires" vs pip's |
| 93 | + # requirements files see: |
| 94 | + # https://packaging.python.org/en/latest/requirements.html |
| 95 | + # install_requires=get_requires('requirements.txt'), |
| 96 | + |
| 97 | + # List additional groups of dependencies here (e.g. development |
| 98 | + # dependencies). You can install these using the following syntax, |
| 99 | + # for example: |
| 100 | + # $ pip install -e .[dev,test] |
| 101 | + #extras_require={ |
| 102 | + # 'test': get_requires(os.path.join('tests', 'requirements_test.txt')) |
| 103 | + #}, |
| 104 | + |
| 105 | + # If there are data files included in your packages that need to be |
| 106 | + # installed, specify them here. If using Python 2.6 or less, then these |
| 107 | + # have to be included in MANIFEST.in as well. |
| 108 | + package_data={ |
| 109 | + '': ['*.md'], |
| 110 | + }, |
| 111 | + |
| 112 | + # Although 'package_data' is the preferred approach, in some case you may |
| 113 | + # need to place data files outside of your packages. See: |
| 114 | + # http://docs.python.org/3.4/distutils/setupscript.html#installing-additional-files # noqa |
| 115 | + # In this case, 'data_file' will be installed into '<sys.prefix>/my_data' |
| 116 | + # data_files=[('my_data', ['data/data_file'])], |
| 117 | + |
| 118 | + # To provide executable scripts, use entry points in preference to the |
| 119 | + # "scripts" keyword. Entry points provide cross-platform support and allow |
| 120 | + # pip to create the appropriate form of executable for the target platform. |
| 121 | + #entry_points={ |
| 122 | + # 'console_scripts': [ |
| 123 | + # 'patch.py=patch', |
| 124 | + # ], |
| 125 | + #}, |
| 126 | +) |
0 commit comments