Use setuptools entry_points for command line scripts

spacetelescope · Jan 22, 2015 · e7c624a · e7c624a
1 parent b060744
commit e7c624a
Show file tree

Hide file tree

Showing 5 changed files with 11 additions and 13 deletions.
diff --git a/.gitignore b/.gitignore
@@ -25,6 +25,9 @@ docs/_build
 .pydevproject
 .settings
 
+# Pycharm editor project files
+.idea
+
 # Packages/installer info
 *.egg
 *.egg-info

diff --git a/TEMPLATE_CHANGES.md b/TEMPLATE_CHANGES.md
@@ -5,7 +5,7 @@ be removed in affiliated packages.
 0.4.2 (untagged)
 ----------------
 
-- No changes yet
+- Use setuptools entry_points for command line scripts
 
 0.4.1 (2014-10-22)
 ------------------

diff --git a/scripts/README.rst b/scripts/README.rst
diff --git a/scripts/script_example b/scripts/script_example
diff --git a/setup.py b/setup.py
@@ -78,6 +78,12 @@
 package_info['package_data'].setdefault(PACKAGENAME, [])
 package_info['package_data'][PACKAGENAME].append('data/*')
 
+# Define entry points for command-line scripts
+entry_points = {}
+entry_points['console_scripts'] = [
+    'astropy-package-template-example = packagename.example_mod:main',
+]
+
 # Include all .c files, recursively, including those generated by
 # Cython, since we can not do this in MANIFEST.in with a "dynamic"
 # directory name.
@@ -105,5 +111,6 @@
       cmdclass=cmdclassd,
       zip_safe=False,
       use_2to3=True,
+      entry_points=entry_points,
       **package_info
 )