pyModeS/setup.py

107 lines
4.3 KiB
Python
Raw Normal View History

"""A setuptools based setup module.
See:
https://packaging.python.org/en/latest/distributing.html
https://github.com/pypa/sampleproject
2017-03-22 01:14:30 +08:00
Steps for deploying a new verison:
1. Increase the version number
2. remove the old deployment under [dist] folder
3. run: python setup.py sdist
run: python setup.py bdist_wheel --universal
4. twine upload dist/*
"""
# Always prefer setuptools over distutils
from setuptools import setup, find_packages
2019-08-05 22:37:30 +08:00
# To use a consistent encoding
from codecs import open
from os import path
here = path.abspath(path.dirname(__file__))
# Get the long description from the README file
2019-08-05 22:37:30 +08:00
with open(path.join(here, "README.rst"), encoding="utf-8") as f:
long_description = f.read()
setup(
2019-08-05 22:37:30 +08:00
name="pyModeS",
# 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
2019-08-05 22:37:30 +08:00
version="2.2",
description="Python Mode-S and ADS-B Decoder",
long_description=long_description,
# The project's main homepage.
2019-08-05 22:37:30 +08:00
url="https://github.com/junzis/pyModeS",
# Author details
2019-08-05 22:37:30 +08:00
author="Junzi Sun",
author_email="j.sun-1@tudelft.nl",
# Choose your license
2019-08-05 22:37:30 +08:00
license="GNU GPL v3",
# See https://pypi.python.org/pypi?%3Aaction=list_classifiers
classifiers=[
# How mature is this project? Common values are
# 3 - Alpha
# 4 - Beta
# 5 - Production/Stable
2019-08-05 22:37:30 +08:00
"Development Status :: 4 - Beta",
# Indicate who your project is intended for
2019-08-05 22:37:30 +08:00
"Intended Audience :: Developers",
"Topic :: Software Development :: Build Tools",
# Pick your license as you wish (should match "license" above)
2019-08-05 22:37:30 +08:00
"License :: OSI Approved :: GNU General Public License v3 (GPLv3)",
# Specify the Python versions you support here. In particular, ensure
# that you indicate whether you support Python 2, Python 3 or both.
2019-08-05 22:37:30 +08:00
"Programming Language :: Python :: 2",
"Programming Language :: Python :: 2.7",
"Programming Language :: Python :: 3",
"Programming Language :: Python :: 3.3",
"Programming Language :: Python :: 3.4",
"Programming Language :: Python :: 3.5",
"Programming Language :: Python :: 3.6",
],
# What does your project relate to?
2019-08-05 22:37:30 +08:00
keywords="Mode-S ADS-B EHS decoding",
# You can just specify the packages manually here if your project is
# simple. Or you can use find_packages().
2019-08-05 22:37:30 +08:00
packages=find_packages(exclude=["contrib", "docs", "tests"]),
# Alternatively, if you want to distribute just a my_module.py, uncomment
# this:
# py_modules=["my_module"],
# 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
2019-08-23 20:59:50 +08:00
install_requires=["numpy", "argparse", "pyzmq", "pyrtlsdr"],
# 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={
# 'dev': ['check-manifest'],
# 'test': ['coverage'],
# },
# 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={
# 'sample': ['package_data.dat'],
# },
# 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': [
# 'sample=sample:main',
# ],
# },
2019-08-05 22:37:30 +08:00
scripts=["pyModeS/streamer/modeslive"],
)