setup.py 3.0KB

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