5 This archive contains bindings for the GLib, and GObject,
6 to be used in Python. It is a fairly complete set of bindings,
7 it's already rather useful, and is usable to write moderately
8 complex programs. (see the examples directory for some examples
9 of the simpler programs you could write).
11 If you have any enhancements or bug reports, please file them in
14 http://bugzilla.gnome.org/enter_bug.cgi?product=pygobject
16 If you have a patch, file the bug first and then use the "create new
17 attachment" link on the bug's info page. My preferred format for
18 patches is unified diff format (ie. diff -u). Please don't send me
19 diffs which don't have any context, as these make it very difficult to
20 see what the patch does.
26 New versions of this package can be found at:
28 http://ftp.gnome.org/pub/GNOME/sources/pygobject/
34 pygobject development is discussed on the GNOME python-hackers mailing list.
35 You can subscribe to it through the web interface:
37 https://mail.gnome.org/mailman/listinfo/python-hackers-list/
43 * C compiler (GCC and MSVC supported)
44 * Python 2.7 or higher
45 * Glib/Gio 2.38.0 or higher
46 * gobject-introspection 1.46.0 or higher
53 This software is covered by the GNU Lesser General Public Licence
54 (version 2.1, or if you choose, a later version). Basically just don't
55 say you wrote bits you didn't.
61 PyGObject uses the standard autotools for the build infrastructure. To
62 build, it should be as simple as running::
64 $ ./configure --prefix=<prefix where python is installed>
68 By default, configure searches for a few well-known Python interpreter
69 names, such as "python3", "python2", "python2.7", or "python". If your
70 Python interpreter isn't in the path, or is not called "python", you can
71 configure pygobject to build against that with --with-python=<path> or
72 setting the PYTHON environment variable::
74 $ ./configure --with-python=python3
75 $ PYTHON=python3.2 ./configure
76 $ ./configure --with-python=~/my-patched-python/python
78 If configure can't find GTK+, you may need to set the PKG_CONFIG_PATH
79 environment variable to help it find the libraries.
81 The "make install" target will generate normal and optimised bytecode
82 for all the .py files.
84 Note. If you're installing to another prefix than the one where python
85 is installed you'll need to set the PYTHONPATH variable to the
86 $prefix/lib/pythonX.Y/site-packages directory created by
87 the PyGObject installation.
93 After having compiled and installed pygobject, you may want to test them.
94 There are a number of example programs available in the examples/
101 If you have questions about programming with PyGObject, you might want to
102 check the documentation on
104 https://live.gnome.org/PyGObject/
106 If that does not help, send a message to the mailing list (information on
107 subscribing is above), or join #python on irc.gnome.org.
114 * James Henstridge <james@daa.com.au>
115 * Johan Dahlin <johan@gnome.org>
118 * Tomeu Vizoso <tomeu.vizoso@collabora.co.uk>
119 * Martin Pitt <martinpitt@gnome.org>
120 * Paolo Borelli <pborelli@gnome.org>
121 * Ignacio Casal Quinteiro <icq@gnome.org>
122 * Sebastian Pölsterl <sebp@k-d-w.org>
123 * Simon Feltman <sfeltman@gnome.org>
124 * Christoph Reiter <reiter.christoph@gmail.com>
126 See the NEWS file and the git history for a list of all contributors.