setup.py 3.0KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102
  1. # coding: utf-8
  2. # Always prefer setuptools over distutils
  3. from setuptools import setup
  4. from setuptools import find_packages
  5. from os import path
  6. import sys
  7. here = path.abspath(path.dirname(__file__))
  8. install_requires = [
  9. 'marshmallow >2.0.0,<3.0.0a1',
  10. 'apispec',
  11. 'multidict'
  12. ]
  13. tests_require = [
  14. 'pytest',
  15. 'pytest-cov',
  16. 'bottle',
  17. 'flask',
  18. 'pyramid',
  19. 'webtest',
  20. ]
  21. dev_require = [
  22. 'requests',
  23. ] + tests_require
  24. # Python 3.4 require
  25. if sys.version_info.major == 3 and sys.version_info.minor == 4:
  26. install_requires.append('typing')
  27. setup(
  28. name='hapic',
  29. # Versions should comply with PEP440. For a discussion on single-sourcing
  30. # the version across setup.py and the project code, see
  31. # https://packaging.python.org/en/latest/single_source_version.html
  32. version='0.33',
  33. description='HTTP api input/output manager',
  34. # long_description=long_description,
  35. long_description='',
  36. # The project's main homepage.
  37. url='https://github.com/algoo/hapic',
  38. # Author details
  39. author='Algoo Development Team',
  40. author_email='contact@algoo.fr',
  41. # Choose your license
  42. license='',
  43. # What does your project relate to?
  44. keywords='http api validation',
  45. # You can just specify the packages manually here if your project is
  46. # simple. Or you can use find_packages().
  47. packages=find_packages(exclude=['contrib', 'docs', 'tests']),
  48. # Alternatively, if you want to distribute just a my_module.py, uncomment
  49. # this:
  50. # py_modules=["my_module"],
  51. # List run-time dependencies here. These will be installed by pip when
  52. # your project is installed. For an analysis of "install_requires" vs pip's
  53. # requirements files see:
  54. # https://packaging.python.org/en/latest/requirements.html
  55. install_requires=install_requires,
  56. # List additional groups of dependencies here (e.g. development
  57. # dependencies). You can install these using the following syntax,
  58. # for example:
  59. # $ pip install -e ".[test]"
  60. extras_require={
  61. 'test': tests_require,
  62. 'dev': dev_require,
  63. },
  64. # If there are data files included in your packages that need to be
  65. # installed, specify them here. If using Python 2.6 or less, then these
  66. # have to be included in MANIFEST.in as well.
  67. # package_data={
  68. # 'sample': ['package_data.dat'],
  69. # },
  70. # Although 'package_data' is the preferred approach, in some case you may
  71. # need to place data files outside of your packages. See:
  72. # http://docs.python.org/3.4/distutils/setupscript.html#installing-additional-files # noqa
  73. # In this case, 'data_file' will be installed into '<sys.prefix>/my_data'
  74. # data_files=[('my_data', ['data/data_file'])],
  75. # To provide executable scripts, use entry points in preference to the
  76. # "scripts" keyword. Entry points provide cross-platform support and allow
  77. # pip to create the appropriate form of executable for the target platform.
  78. entry_points={},
  79. setup_requires=[],
  80. tests_require=tests_require,
  81. include_package_data=True,
  82. )