I am pleased to announce the release of GNU pyconfigure 0.2.2.
GNU pyconfigure is a set of template files for Python developers to use to easily implement the standard GNU configure/install process for their packages. The standard GNU process generally consists of two familiar steps:
$ ./configure --prefix=/usr/ $ make install
By using the templates provided by GNU pyconfigure, the Python developer gains the power and flexibility of the time-tested, language-agnostic GNU installation process, while the user or the software packager encounters a familiar and convenient interface.
GNU pyconfigure is designed to work either alongside of or in place of the Python 'distutils' module's setup.py script. Thus, if your project already has a setup.py script, pyconfigure can simply wrap its functionality, leveraging the work you have already done.
To learn more and to read the documentation, visit the website at: http://www.gnu.org/software/pyconfigure
You may download the release from http://ftp.gnu.org/gnu/pyconfigure/
You may also download from your nearest mirror at http://ftpmirror.gnu.org/pyconfigure/
Here are the compressed sources and a GPG detached signature[*]:
Here are the MD5 and SHA1 checksums:
1f0aaa6060ce4a783a95fcb789c0eacf pyconfigure-0.2.2.tar.gz bf68b579589f6b8831a667246b0f904195f59c8c pyconfigure-0.2.2.tar.gz
[*] Use a .sig file to verify that the corresponding file (without the .sig suffix) is intact. First, be sure to download both the .sig file and the corresponding tarball. Then, run a command like this:
gpg --verify pyconfigure-0.2.1.tar.gz.sig
If that command fails because you don't have the required public key, then run this command to import it:
gpg --keyserver keys.gnupg.net --recv-keys EB7AB74D
and rerun the 'gpg --verify' command.
This release is a bugfix release fixing a critical bug in the Python M4 macros.
- pkgpythondir and pkgpyexecdir are correctly constructed. In some cases, the package name was not being appended to these variables, which could have some nasty effects if used blindly. This has been fixed.