setup.py

#!/usr/bin/env python
# -*- coding: utf-8 -*-


# Always prefer setuptools over distutils
from setuptools import setup, find_packages
# To use a consistent encoding
from codecs import open
from os import path

here = path.abspath(path.dirname(__file__))

# Get the long description from the README file
# with open(path.join(here, 'README.rst'), encoding='utf-8') as f:
#     long_description = f.read()
long_description = "Raml to deconst converter"

# TODO: implement changelog
# with open('HISTORY.rst') as history_file:
#    history = history_file.read().replace('.. :changelog:', '')

setup(
    name='ramlpreparer',

    # Versions should comply with PEP440.  For a discussion on single-sourcing
    # the version across setup.py and the project code, see
    # https://packaging.python.org/en/latest/single_source_version.html
    version='0.1.0',
    description="Build RAML-based documentation to JSON and jam it in the cloud",
    long_description=long_description,
    # Author details
    author="Laura Santamaria",
    author_email='laura.santamaria@rackspace.com',
    # The project's main homepage.
    url='https://github.com/nimbinatus/deconst-raml-preparer',
    # You can just specify the packages manually here if your project is
    # simple. Or you can use find_packages().
    packages=[
        'ramlpreparer', 'ramlpreparer.builders'
    ],
#    package_dir={'ramlpreparer':
#                 'deconst-raml-preparer'},
    include_package_data=True,
    # List run-time dependencies here.  These will be installed by pip when
    # your project is installed. For an analysis of "install_requires" vs pip's
    # requirements files see:
    # https://packaging.python.org/en/latest/requirements.html
    # install_requires=['peppercorn'],
#    install_requires=requirements, #TODO: Figure out if this is still used...
    # List additional groups of dependencies here (e.g. development
    # dependencies). You can install these using the following syntax,
    # for example:
    # $ pip install -e .[dev,test]
    # extras_require={
    #     'dev': ['check-manifest'],
    #     'test': ['coverage'],
    # },


    # Choose your license
    license="Apache",

#    zip_safe=False,
    # What does your project relate to?
    keywords=[
        'deconst',
        'deconst-raml-preparer',
        'ramlpreparer'
    ],

    # See https://pypi.python.org/pypi?%3Aaction=list_classifiers
    classifiers=[
        # How mature is this project? Common values are
        #   3 - Alpha
        #   4 - Beta
        #   5 - Production/Stable
        'Development Status :: 2 - Pre-Alpha',
        # Indicate who your project is intended for
        'Intended Audience :: Developers',
        'Topic :: Information Development :: Build Tools'
        # Pick your license as you wish (should match "license" above)
        'License :: OSI Approved :: Apache',
        'Natural Language :: English',
        # Specify the Python versions you support here. In particular, ensure
        # that you indicate whether you support Python 2, Python 3 or both.
        'Programming Language :: Python :: 3',
        'Programming Language :: Python :: 3.5',
        'Programming Language :: Python :: 3.6',
    ],
#    test_suite='tests',  #TODO: Figure out if this is still used...
#    tests_require=test_requirements #TODO: Figure out if this is still used...
#)
    # # If there are data files included in your packages that need to be
    # # installed, specify them here.  If using Python 2.6 or less, then these
    # # have to be included in MANIFEST.in as well.
    # package_data={
    #     'sample': ['package_data.dat'],
    # },
    #
    # # Although 'package_data' is the preferred approach, in some case you may
    # # need to place data files outside of your packages. See:
    # # http://docs.python.org/3.4/distutils/setupscript.html#installing-additional-files # noqa
    # # In this case, 'data_file' will be installed into '<sys.prefix>/my_data'
    # data_files=[('my_data', ['data/data_file'])],
    #
    # # To provide executable scripts, use entry points in preference to the
    # # "scripts" keyword. Entry points provide cross-platform support and allow
    # # pip to create the appropriate form of executable for the target platform.
    # entry_points={
    #     'console_scripts': [
    #         'sample=sample:main',
    #     ],
    # },
)