Filewatcher File Search File Search
Content Search
» » » » » pygtk-2.24.0.tar.bz2 » Content »
pkg://pygtk-2.24.0.tar.bz2:2361097/pygtk-2.24.0/  info  downloads


Original authors: James Henstridge <>
                  Johan Dahlin <>

Past maintainers: Gustavo J A M Carneiro <>
                  Paul Pogonyshev <>
                  Gian Mario Tagliaretti <>

Maintainers:      John Stowers <>
                  Dieter Verfaillie <>

This archive contains modules that allow you to use GTK+-2 in Python
programs.  At present, it is a complete set of bindings up to and including
the gtk+-2.24 API.

If you have any enhancements or bug reports, please file them in
bugzilla at:

If you have a patch, file the bug first and then use the "create new
attachment" link on the bug's info page.  My preferred format for
patches is unified diff format (ie. diff -u).  Please don't send me
diffs which don't have any context, as these make it very difficult to
see what the patch does.

New Versions

New versions of this package can be found at:

Mailing list

There is a mailing list for pygtk.  You can subscribe to it through
the web interface:

  * C compiler (GCC, MSVC and mingw supported)
  * Python 2.3.5 or higher
  * PyGObject 2.21.3 or higher
  * Pycairo 1.0.2 or higher
  * Glib 2.8.0 or higher
  * GTK+ 2.8.0 or higher (optional) or
    GTK+ 2.10.0 or higher for 2.10 API
    GTK+ 2.12.0 or higher for 2.12 API
    GTK+ 2.14.0 or higher for 2.14 API
    GTK+ 2.16.0 or higher for 2.16 API
    GTK+ 2.18.0 or higher for 2.18 API
    GTK+ 2.20.0 or higher for 2.20 API
    GTK+ 2.22.0 or higher for 2.22 API
    GTK+ 2.24.0 or higher for 2.24 API
  * libglade 2.5.0 or higher (optional)
  * pycairo 1.0.2 or higher (optional)
  * numpy (optional)

This release is supporting the following GTK+ releases:


To include support for the 2.10 API you'll need GTK+ 2.10.0 etc.

Copyright Information

This software is covered by the GNU Lesser General Public Licence
(version 2.1, or if you choose, a later version).  Basically just don't
say you wrote bits you didn't.


PyGTK uses the standard autotools for the build infrastructure.  To
build, it should be as simple as running:

    $ ./configure --prefix=<prefix where python is installed>
    $ make
    $ make install

To build the reference documentation, supply the argument
"--enable-docs" to configure.

If your Python interpreter isn't in the path, or is not called
"python", you can set the PYTHON environment variable to the full path
of the interpreter:

    $ PYTHON=/prefix/bin/python
    $ export PYTHON

If configure can't find GTK+, you may need to set the PKG_CONFIG_PATH
environment variable to help it find the libraries.

The "make install" target will generate normal and optimised bytecode
for all the .py files.

Note. If you're installing to another prefix than the one where python
is installed you'll need to set the PYTHONPATH variable to the
$prefix/lib/pythonX.Y/site-packages directory created by
the PyGTK installation.


After having compiled and installed pygtk, you may want to test them.
There are a number of example programs available in the examples/

Getting Help

If you have questions about programming with PyGTK, you might want to
send a message to the mailing list (information on subscribing is
above).  Alternatively, your question may be answered in the FAQ:
Results 1 - 1 of 1
Help - FTP Sites List - Software Dir.
Search over 15 billion files
© 1997-2017