From 1bf92e3a3cc1e246b1ecc05c63287bb177939efa Mon Sep 17 00:00:00 2001 From: "Jason R. Coombs" Date: Wed, 16 Dec 2015 08:25:05 -0500 Subject: 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. --- release.py | 20 -------------------- 1 file changed, 20 deletions(-) delete mode 100644 release.py (limited to 'release.py') diff --git a/release.py b/release.py deleted file mode 100644 index dd1d6a1c..00000000 --- a/release.py +++ /dev/null @@ -1,20 +0,0 @@ -""" -Setuptools is released using 'jaraco.packaging.release'. To make a release, -install jaraco.packaging and run 'python -m jaraco.packaging.release' -""" - -import os - -import pkg_resources - -pkg_resources.require('jaraco.packaging>=2.0') -pkg_resources.require('wheel') - -files_with_versions = 'setuptools/version.py', - -# bdist_wheel must be included or pip will break -dist_commands = 'sdist', 'bdist_wheel' - -test_info = "Travis-CI tests: http://travis-ci.org/#!/jaraco/setuptools" - -os.environ["SETUPTOOLS_INSTALL_WINDOWS_SPECIFIC_FILES"] = "1" -- cgit v1.2.1