From 9b7c86f6d8c003c9f5db2aa29c93c2f8b61c8583 Mon Sep 17 00:00:00 2001 From: Roger Labbe Date: Mon, 1 Sep 2014 10:42:37 -0700 Subject: [PATCH] Added setup for inclusion on PyPI --- .gitignore | 2 ++ setup.py | 34 ++++++++++++++++++++-------------- 2 files changed, 22 insertions(+), 14 deletions(-) diff --git a/.gitignore b/.gitignore index 0d20b64..41c498e 100644 --- a/.gitignore +++ b/.gitignore @@ -1 +1,3 @@ *.pyc +dist/ +*egg-info* diff --git a/setup.py b/setup.py index 89b3af2..a5475a1 100644 --- a/setup.py +++ b/setup.py @@ -9,7 +9,7 @@ long_description = f.read() setup( - name='sample', + name='filterpy', # Versions should comply with PEP440. For a discussion on single-sourcing # the version across setup.py and the project code, see @@ -38,8 +38,14 @@ 'Development Status :: 3 - Alpha', # Indicate who your project is intended for - 'Intended Audience :: Developers, Engineers', - 'Topic :: Software Development :: Build Tools', + 'Intended Audience :: Developers', + 'Intended Audience :: Education', + 'Intended Audience :: Science/Research', + 'Topic :: Scientific/Engineering', + 'Topic :: Scientific/Engineering :: Mathematics', + 'Topic :: Scientific/Engineering :: Physics', + 'Topic :: Utilities', + # Pick your license as you wish (should match "license" above) 'License :: OSI Approved :: MIT License', @@ -56,7 +62,7 @@ ], # What does your project relate to? - keywords='Kalman filters filtering optimal estimation tracking', + keywords='Kalman filters filtering optimal estimation tracking', # You can just specify the packages manually here if your project is # simple. Or you can use find_packages(). @@ -66,27 +72,27 @@ # project is installed. For an analysis of "install_requires" vs pip's # requirements files see: # https://packaging.python.org/en/latest/technical.html#install-requires-vs-requirements-files - install_requires=['peppercorn'], + install_requires=['numpy', 'scipy', 'matplotlib'], # 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'], - }, + #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 # In this case, 'data_file' will be installed into '/my_data' - data_files=[('my_data', ['data/data_file'])], + #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', - ], - }, + #entry_points={ + # 'console_scripts': [ + # 'sample=sample:main', + # ], + #}, )