setup.py 3.1KB

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