GeezerVison is showing github.com — python-patch-ng/setup.py at master · conan-io/python-patch-ng

Expand file tree

setup.py

Copy path

More file actions

Latest commit

History

128 lines (105 loc) · 4.54 KB

setup.py

Copy path

File metadata and controls

128 lines (105 loc) · 4.54 KB

Raw

Copy raw file

Download raw file

Open symbols panel

Edit and raw actions

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

"""A setuptools based setup module.

See:

https://packaging.python.org/en/latest/distributing.html

https://github.com/pypa/sampleproject

"""

# Always prefer setuptools over distutils

import re

import os

from setuptools import setup

# To use a consistent encoding

from codecs import open

here = os.path.abspath(os.path.dirname(__file__))

# Get the long description from the README file

with open(os.path.join(here, 'README.md'), encoding='utf-8') as f:

long_description = f.read()

def get_requires(filename):

requirements = []

with open(filename) as req_file:

for line in req_file.read().splitlines():

if not line.strip().startswith("#"):

requirements.append(line)

return requirements

def load_version():

"""Loads a file content"""

filename = os.path.abspath(os.path.join(os.path.dirname(os.path.abspath(__file__)),

"patch_ng.py"))

with open(filename, "rt") as version_file:

content = version_file.read()

version = re.search('__version__ = "([0-9a-z.-]+)"', content).group(1)

return version

setup(

name='patch-ng',

python_requires='>=3.6',

# Versions should comply with PEP440. For a discussion on single-sourcing

# the version across setup.py and the project code, see

# https://packaging.python.org/en/latest/single_source_version.html

version=load_version(),

# This is an optional longer description of your project that represents

# the body of text which users will see when they visit PyPI.

# Often, this is the same as your README, so you can just read it in from

# that file directly (as we have already done above)

# This field corresponds to the "Description" metadata field:

# https://packaging.python.org/specifications/core-metadata/#description-optional

long_description=long_description, # Optional

description='Library to parse and apply unified diffs.',

# The project's main homepage.

url='https://github.com/conan-io/python-patch',

# Author details

author='Conan.io',

author_email='[email protected]',

# Choose your license

license='MIT',

# See https://pypi.python.org/pypi?%3Aaction=list_classifiers

classifiers=[

'Development Status :: 5 - Production/Stable',

'Intended Audience :: Developers',

'Topic :: Software Development :: Build Tools',

'License :: OSI Approved :: MIT License',

'Programming Language :: Python :: 3',

'Programming Language :: Python :: 3.6',

'Programming Language :: Python :: 3.7',

'Programming Language :: Python :: 3.8'

# What does your project relate to?

keywords=['patch', 'parse', 'diff', 'strip', 'diffstat'],

# You can just specify the packages manually here if your project is

# simple. Or you can use find_packages().

# packages=find_packages(exclude=['tests']),

# Alternatively, if you want to distribute just a my_module.py, uncomment

# this:

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

# requirements files see:

# https://packaging.python.org/en/latest/requirements.html

# install_requires=get_requires('requirements.txt'),

# List additional groups of dependencies here (e.g. development

# dependencies). You can install these using the following syntax,

# for example:

# $ pip install -e .[dev,test]

#extras_require={

# 'test': get_requires(os.path.join('tests', 'requirements_test.txt'))

#},

# If there are data files included in your packages that need to be

# installed, specify them here. If using Python 2.6 or less, then these

# have to be included in MANIFEST.in as well.

package_data={

'': ['*.md', 'LICENSE'],

# Although 'package_data' is the preferred approach, in some case you may

# need to place data files outside of your packages. See:

# http://docs.python.org/3.4/distutils/setupscript.html#installing-additional-files # noqa

# In this case, 'data_file' will be installed into '<sys.prefix>/my_data'

# data_files=[('my_data', ['data/data_file'])],

# To provide executable scripts, use entry points in preference to the

# "scripts" keyword. Entry points provide cross-platform support and allow

# pip to create the appropriate form of executable for the target platform.

#entry_points={

# 'console_scripts': [

# 'patch_ng.py=patch',

# ],

#},

)