I am pleased to announce the release of GNU pyconfigure 0.2.3. 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 Here are the compressed sources and a GPG detached signature[*]: pyconfigure/pyconfigure-0.2.3.tar.gz pyconfigure/pyconfigure-0.2.3.tar.gz.sig Here are the MD5 and SHA1 checksums: 8a64b3187cf2d43e3230d1ee68d607b5 pyconfigure-0.2.3.tar.gz 0590628eab986d8cf2755d93c9f71e0953e50516 pyconfigure-0.2.3.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.3.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 was bootstrapped with the following tools: Autoconf 2.69 Automake 1.15 NEWS This is a bugfix release. * Uninstallation of scripts was fixed and uninstallation was made safer in general. A bug in uninstalling scripts via the Makefile has been fixed. Uninstallation via the Makefile was previously safe if the relevant targets and variables were used correctly, however it was possible to implement some Very Bad Ideas. It should be a lot more difficult to do that now. * Checking for python interpreters is more robust Previously the macros could still be confused depending on whether the "python" executable points to "python2" or "python3". The correct version should be detected in all cases now.
signature.asc
Description: This is a digitally signed message part
-- If you have a working or partly working program that you'd like to offer to the GNU project as a GNU package, see https://www.gnu.org/help/evaluation.html.
