123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116 |
- # coding: utf-8
- # Always prefer setuptools over distutils
- from setuptools import setup
- from setuptools import find_packages
- from os import path
- import sys
-
- # INFO - G.M - 29-05-2018 - exec info.py file in order to obtain version
- # without any dependencies trouble.
- # see https://milkr.io/kfei/5-common-patterns-to-version-your-Python-package
- # section "Exec/execfile" for other example and "Import from the package" for
- # information about import strategy problem.
- infos_dict = {}
- with open("hapic/infos.py") as fp:
- exec(fp.read(), infos_dict)
- version = infos_dict['__version__']
-
- here = path.abspath(path.dirname(__file__))
-
- install_requires = [
- 'marshmallow >2.0.0,<3.0.0a1',
- 'hapic_apispec==0.37.0',
- 'multidict'
- ]
- tests_require = [
- 'pytest',
- 'pytest-cov',
- 'bottle',
- 'flask',
- 'pyramid',
- 'webtest',
- ]
- dev_require = [
- 'requests',
- ] + tests_require
-
-
- # Python 3.4 require
- if sys.version_info.major == 3 and sys.version_info.minor == 4:
- install_requires.append('typing')
-
- with open('README.md', 'r') as readme_file:
- long_description = readme_file.read()
-
- setup(
- name='hapic',
-
- # 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=version,
- description='HTTP api input/output manager',
- long_description=long_description,
- long_description_content_type='text/markdown',
-
- # The project's main homepage.
- url='https://github.com/algoo/hapic',
-
- # Author details
- author='Algoo Development Team',
- author_email='contact@algoo.fr',
-
- # Choose your license
- license='MIT',
-
- # What does your project relate to?
- keywords='http api validation',
-
- # You can just specify the packages manually here if your project is
- # simple. Or you can use find_packages().
- 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
- install_requires=install_requires,
-
- # List additional groups of dependencies here (e.g. development
- # dependencies). You can install these using the following syntax,
- # for example:
- # $ pip install -e ".[test]"
- extras_require={
- 'test': tests_require,
- 'dev': dev_require,
- },
-
- # 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={},
- setup_requires=[],
- dependency_links=[
- 'git+https://github.com/algoo/apispec.git@hapic_apispec#egg=apispec-0.35.0-algoo'
- ],
- tests_require=tests_require,
- include_package_data=True,
- )
|