838da66e2f
There is quite a bit going on in this commit. Here is a high level description of all of the changes: * Improved the README to include information for running the integrations tests now that we have subcommand management support. * Change the clean script to also delete the build directory. * Removed requirement on the DCOS_PATH environment variable. We now assume the DCOS CLI installation directory based on the location of the dcos cli binary * Adds support for installing subcommand from python wheels. The packages are install under the 'subcommands' directory. * Extended the `dcos help` to look into the 'subcommands' directory for the excutables that extend the cli. * Fix the root `dcos` executable to not use the DCOS_PATH environment variable to discover subcommand. It now discovers subcommand based on the location of the root (`dcos`) executable. * Adds `dcos subcommand` for managing the installation, listing and the removal of subcommands. * Adds dependencies on pkginfo and virtualenv. We need pkginfo to query information about the package. We need virtualenv to create virtual environment for each subcommand installed.
125 lines
4.1 KiB
Python
125 lines
4.1 KiB
Python
from setuptools import setup, find_packages
|
|
from codecs import open
|
|
from os import path
|
|
|
|
from dcos.api import constants
|
|
|
|
# TODO: what license should we use?
|
|
|
|
here = path.abspath(path.dirname(__file__))
|
|
|
|
# Get the long description from the relevant file
|
|
with open(path.join(here, 'README.rst'), encoding='utf-8') as f:
|
|
long_description = f.read()
|
|
|
|
setup(
|
|
name='dcos',
|
|
|
|
# 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=constants.version,
|
|
|
|
description='DCOS Command Line Interface',
|
|
long_description=long_description,
|
|
|
|
# The project's main homepage.
|
|
url='https://github.com/mesosphere/CLI-poc',
|
|
|
|
# Author details
|
|
author='Mesosphere, Inc.',
|
|
author_email='team@mesosphere.io',
|
|
|
|
|
|
# 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 :: 3 - Alpha',
|
|
|
|
# Indicate who your project is intended for
|
|
'Intended Audience :: Developers',
|
|
'Intended Audience :: Information Technology',
|
|
'Topic :: Software Development :: User Interfaces',
|
|
|
|
# Pick your license as you wish (should match "license" above)
|
|
'License :: OSI Approved :: TODO License',
|
|
|
|
# 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 :: 2',
|
|
'Programming Language :: Python :: 2.6',
|
|
'Programming Language :: Python :: 2.7',
|
|
'Programming Language :: Python :: 3',
|
|
'Programming Language :: Python :: 3.2',
|
|
'Programming Language :: Python :: 3.3',
|
|
'Programming Language :: Python :: 3.4',
|
|
],
|
|
|
|
# What does your project relate to?
|
|
keywords='mesos apache marathon mesosphere command datacenter',
|
|
|
|
# You can just specify the packages manually here if your project is
|
|
# simple. Or you can use find_packages().
|
|
packages=find_packages(exclude=['contrib', 'docs', 'tests*']),
|
|
|
|
# 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=[
|
|
'docopt',
|
|
'gitpython',
|
|
'jsonschema',
|
|
'pkginfo',
|
|
'portalocker',
|
|
'pygments',
|
|
'pystache',
|
|
'requests',
|
|
'toml',
|
|
'virtualenv',
|
|
],
|
|
|
|
# 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'],
|
|
},
|
|
|
|
# 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={
|
|
'dcos': ['data/*'],
|
|
},
|
|
|
|
# Although 'package_data' is the preferred approach, in some case you may
|
|
# need to place data files outside of your packages.
|
|
# In this case, 'data_file' will be installed into '<sys.prefix>/my_data'
|
|
# data_files=[('my_data', ['data/data_file'])],
|
|
data_files=[],
|
|
|
|
# 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': [
|
|
'dcos=dcos.cli.main:main',
|
|
'dcos-help=dcos.cli.help.main:main',
|
|
'dcos-config=dcos.cli.config.main:main',
|
|
'dcos-marathon=dcos.cli.marathon.main:main',
|
|
'dcos-package=dcos.cli.package.main:main',
|
|
'dcos-subcommand=dcos.cli.subcommand.main:main',
|
|
],
|
|
},
|
|
|
|
scripts=[
|
|
'bin/env-setup',
|
|
]
|
|
)
|