From 67013ae17af0436b930dce450a813239be969601 Mon Sep 17 00:00:00 2001 From: Trygve Laugstøl Date: Tue, 27 Dec 2016 01:14:37 +0100 Subject: o Initial import of some tools for working with KiCAD BOM files and Digi-key. --- setup.py | 106 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 106 insertions(+) create mode 100644 setup.py (limited to 'setup.py') diff --git a/setup.py b/setup.py new file mode 100644 index 0000000..6fcf812 --- /dev/null +++ b/setup.py @@ -0,0 +1,106 @@ +# 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.md'), encoding='utf-8') as f: + long_description = f.read() + +setup( + name='eda-rds', + + version='1.0.0', + + description='RDF-oriented for for EDA (electronic design automation)', + long_description=long_description, + + # The project's main homepage. + url='https://trygvis.io/git/2016/12/eda-rdf', + + author='Trygve Laugstøl', + author_email='trygvis@inamo.no', + + # Choose your license + license='MIT', + + # See https://pypi.python.org/pypi?%3Aaction=list_classifiers + classifiers=[ + 'Development Status :: 3 - Alpha', + + 'Intended Audience :: Developers', + 'Intended Audience :: Manufacturing', + 'Topic :: Software Development :: Build Tools', + 'Topic :: Database', + 'Topic :: Internet', + 'Topic :: Scientific/Engineering :: Electronic Design Automation (EDA)', + 'Topic :: Software Development :: Quality Assurance', + 'Environment :: Console', + + 'License :: OSI Approved :: MIT License', + + 'Programming Language :: Python :: 3', + 'Programming Language :: Python :: 3.4', + 'Programming Language :: Python :: 3.5', + 'Programming Language :: Python :: 3.6', + 'Operating System :: OS Independent', + ], + + keywords='EDA KiCAD RDF Digi-Key', + + packages=find_packages(exclude=['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=[ + "bsddb3>=6.2.1", + "CacheControl>=0.11.7", + "html5lib>=0.999999999", + "isodate>=0.5.4", + "lockfile>=0.12.2", + "lxml>=3.7.0", + "mechanize>=0.2.5", + "pyparsing>=2.1.10", + "rdflib>=4.2.1", + "requests>=2.12.4", + "six>=1.10.0", + "SPARQLWrapper>=1.8.0", + "webencodings>=0.5", + ], + + # 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={ + # '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 '/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': [ + 'eda-rdf=trygvis.eda.cli.eda_rdf:main', + ], + }, +) -- cgit v1.2.3