I am pleased to announce the release of GNU pyconfigure 0.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:
- 881975b519f0330165bc45f07ff85aa6 pyconfigure-0.2.tar.gz
- 4f62655779a9f3a82946ad272e2682b6c056c46e pyconfigure-0.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.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.
Version 0.2 NEWS This release introduces a major restructuring of pyconfigure, making it easier to use for projects with different needs. Please read the documentation to learn more about the changes.
The new ‘pyconf’ script makes starting a new project easier. Previously, pyconfigure’s template files had to be manually copied into new projects. Now this process is simplified by the ‘pyconf’ script that is installed with pyconfigure. This script is called From within a Python project’s directory and copies/generates all of the necessary files into the directory for you. Its command-line options support several different project needs.
Writing your build/install logic in Make is now supported. In addition to having the Makefile be a wrapper around setup.py, it is now possible to do the opposite and have setup.py be a wrapper around the Makefile. This allows you to write all of your build and install logic in Make.
The template files contain more comments. Many of the template files have been filled with even more useful comments, making the process of setting up pyconfigure for your project even easier. Also, the ‘configure.ac’ template has been rearranged into a more logical structure.
PC_INITAutoconf macro simplifies getting started. This macro makes finding a Python interpreter even easier and more flexible by letting you specify minimum and maximum versions, freeing you from having to write this version checking code yourself in ‘configure.ac’.
PC_PYTHON_VERIFY_VERSIONmacro has been made more flexible. Of course, if you do want to do some kind of version checking, it has been made even easier. You can now perform any kind of version test with
PC_PYTHON_VERIFY_VERSION: greater-than, less-than, equals, etc.