Experiment with using setuptools_scm for release management. This approach drastically simplifies the codebase, but imposes an initial dependency at install time, which could prove problemmatic in scenarios where connectivity is limited. This approach may not be viable for real-world consumption, but I'm committing it in this branch for consideration with no plans to release it without more testing and discussion.

1 files changed, 3 insertions, 7 deletions

diff --git a/docs/conf.py b/docs/conf.py
index c2a63873..846e4b3e 100644
--- a/docs/conf.py
+++ b/docs/conf.py
@@ -18,11 +18,7 @@
 # add these directories to sys.path here. If the directory is relative to the
 # documentation root, use os.path.abspath to make it absolute, like shown here.
 
-# Allow Sphinx to find the setup command that is imported below, as referenced above.
-import sys, os
-sys.path.append(os.path.abspath('..'))
-
-import setup as setup_script
+import setuptools_scm
 
 # -- General configuration -----------------------------------------------------
 
@@ -51,9 +47,9 @@ copyright = '2009-2014, The fellowship of the packaging'
 # built documents.
 #
 # The short X.Y version.
-version = setup_script.setup_params['version']
+version = setuptools_scm.get_version(root='..', relative_to=__file__)
 # The full version, including alpha/beta/rc tags.
-release = setup_script.setup_params['version']
+release = version
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.