Skip to content
This repository
Newer
Older
100644 38 lines (31 sloc) 1.615 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.
25 #. You no longer need to fiddle with PATH environment variables.
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
29 simply importing gtk, gobject, etc might[1] not work without
30 the .require() call. The .require() call is typically done only
31 once in a startup script somewhere.
32 #. The all-in-one installer version will stay at 2.22.0.0 until
33 there's a stable release. If you want to test newer snapshots
34 when they get available, you'll first need to uninstall the
35 previous one, either from the "add/remove program" control panel
36 applet, or by executing the old versions .msi file and choosing
37 the "Remove" option (just to be on the safe side)...
Something went wrong with that request. Please try again.