setup.py 3.1KB

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