Skip to content
This repository
Newer
Older
100644 48 lines (40 sloc) 2.073 kb
5c4ed978 »
2010-11-12 first commit
1 ===============
2 pygtk-installer
3 ===============
4
da0c5e84 »
2010-11-12 Add some more documentation
5 The pygtk-installer project provides:
5c4ed978 »
2010-11-12 first commit
6
9d342c4c »
2010-11-12 [docs] improve the warning, point out some pitfalls
7 - build_bindings.sh: a tool that builds windows installer packages (both .exe
8 and .msi) for pygtk and dependencies.
9 - build_installer.py: a tool that generates an all-in-one installer bundling
10 the separate .msi installers created by build_bindings.sh and the gtk+ runtime
11 from ftp.gnome.org/pub/GNOME/binaries/win32/.
da0c5e84 »
2010-11-12 Add some more documentation
12
9d342c4c »
2010-11-12 [docs] improve the warning, point out some pitfalls
13 =======
14 WARNING
15 =======
16
17 The all-in-one installer should be considered as a proof of concept.
18 Please do not use it on productions systems just yet.
19
20 If you decide to give it a test anyway:
21
22 #. Make absolutely sure the separate pycairo, pygtk, pygobject, etc
23 packages are uninstalled. The all-in-one installer does not yet
24 check for their presence and will happily overwrite them.
ff7203bf »
2010-11-12 [docs] improve the warning
25 #. You no longer need to fiddle with the PATH environment variable.
9d342c4c »
2010-11-12 [docs] improve the warning, point out some pitfalls
26 The pygtk version that's installed with the all-in-one installer
27 should take care of loading the included gtk+ runtime on PATH
28 when you import pygtk; pygtk.require('2.0'). As a consequence
ff7203bf »
2010-11-12 [docs] improve the warning
29 simply importing gtk, gobject, etc might not work without
9d342c4c »
2010-11-12 [docs] improve the warning, point out some pitfalls
30 the .require() call. The .require() call is typically done only
31 once in a startup script somewhere.
ff7203bf »
2010-11-12 [docs] improve the warning
32 #. Why did you say "might not work" above? Ah, good question. If
33 you've got another gtk+ runtime on your PATH environment variable - for
34 example you installed Dia, MonoDevelop (gtk#), etc. - the PyGTK bindings might
35 use one of those runtime libraries. In that case the behavior of the PyGTK
36 bindings is unspecified (it might crash, error out, etc.).
37 #. If you want to test newer snapshots of the all-in-one installer when they
38 get available, you'll first need to uninstall the previous one, either from
39 the "add/remove program" control panel applet, or by executing the old
40 version's .msi file and choosing the "Remove" option (just to be on the safe
41 side)...
42 #. If it doesn't work, consider executing the following and study the
43 output::
44
45 $ python -v
46 >>> import pygtk
47 >>> pygtk.require('2.0)
Something went wrong with that request. Please try again.