@@ -0,0 +1,3099 @@
+%0Afrom setuptools import setup, find_packages%0A%0Asetup(%0A    name='testWrt',%0A%0A    # Versions should comply with PEP440.  For a discussion on single-sourcing%0A    # the version across setup.py and the project code, see%0A    # https://packaging.python.org/en/latest/single_source_version.html%0A    version='0.1.0',%0A%0A    description='A small testing library to test OpenWrt devices',%0A    long_description=%22%22,%0A%0A    # The project's main homepage.%0A    url='https://github.com/lynxis/testWrt',%0A%0A    # Author details%0A    author='Alexander Couzens',%0A    author_email='lynxis@fe80.eu',%0A%0A    # Choose your license%0A    license='BSD',%0A%0A    # See https://pypi.python.org/pypi?%253Aaction=list_classifiers%0A    classifiers=%5B%0A        # How mature is this project? Common values are%0A        #   3 - Alpha%0A        #   4 - Beta%0A        #   5 - Production/Stable%0A        'Development Status :: 3 - Alpha',%0A%0A        # Indicate who your project is intended for%0A        'Intended Audience :: Developers',%0A        'Topic :: Software Development :: Testing',%0A%0A        # Pick your license as you wish (should match %22license%22 above)%0A        'License :: OSI Approved :: BSD License',%0A%0A        # Specify the Python versions you support here. In particular, ensure%0A        # that you indicate whether you support Python 2, Python 3 or both.%0A        'Programming Language :: Python :: 3',%0A        'Programming Language :: Python :: 3.2',%0A        'Programming Language :: Python :: 3.3',%0A        'Programming Language :: Python :: 3.4',%0A    %5D,%0A%0A    # What does your project relate to?%0A    keywords='openwrt testing',%0A%0A    # You can just specify the packages manually here if your project is%0A    # simple. Or you can use find_packages().%0A    packages=find_packages(exclude=%5B'contrib', 'docs', 'tests*'%5D),%0A%0A    # List run-time dependencies here.  These will be installed by pip when%0A    # your project is installed. For an analysis of %22install_requires%22 vs pip's%0A    # requirements files see:%0A    # https://packaging.python.org/en/latest/requirements.html%0A    install_requires=%5B'nose', 'paramiko'%5D,%0A%0A    # List additional groups of dependencies here (e.g. development%0A    # dependencies). You can install these using the following syntax,%0A    # for example:%0A    # $ pip install -e .%5Bdev,test%5D%0A    extras_require=%7B%0A    %7D,%0A%0A    # If there are data files included in your packages that need to be%0A    # installed, specify them here.  If using Python 2.6 or less, then these%0A    # have to be included in MANIFEST.in as well.%0A    package_data=%7B%0A    %7D,%0A%0A    # Although 'package_data' is the preferred approach, in some case you may%0A    # need to place data files outside of your packages. See:%0A    # http://docs.python.org/3.4/distutils/setupscript.html#installing-additional-files # noqa%0A    # In this case, 'data_file' will be installed into '%3Csys.prefix%3E/my_data'%0A    data_files=%5B%5D,%0A%0A    # To provide executable scripts, use entry points in preference to the%0A    # %22scripts%22 keyword. Entry points provide cross-platform support and allow%0A    # pip to create the appropriate form of executable for the target platform.%0A    entry_points=%7B%0A    %7D,%0A)%0A

add setup.py