setup.py 2.8KB

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