Permalink
Browse files

README: clarify some things

  • Loading branch information...
1 parent 464f0c5 commit 46498177aa1c77348e019fc3106231088f54b66d @dieterv committed Dec 23, 2010
Showing with 30 additions and 18 deletions.
  1. +30 −18 README.rst
View
@@ -2,6 +2,7 @@
Using the PyGTK All-in-one installer
====================================
+
The PyGTK All-in-one version number
===================================
@@ -11,22 +12,22 @@ major upgrades. The version number is constructed as follows::
PYGTK_MAJOR.PYGTK_MINOR.INSTALLER_REVISION
-Stable releases are kept available for download, testing revisions are removed
-from the download area once they are superseded by newer versions.
What file should I use?
=======================
-All the .msi files are named as follows:
+All the .msi files are named as follows::
pygtk-all-in-one-X.X.X.winYY-pyZ.Z.msi
Where X.X.X is the PyGTK All-in-one version number, YY is 32 or 64 and
-Z.Z is the Python version number the installer supports.
+Z.Z is the Python version number the installer supports. Currently, only
+32 bit Python is supported.
You need to make sure both YY and Z.Z correspond to the version of the Python
interpreter that's installed on your system.
+
I'm new, how do I start?
========================
@@ -49,7 +50,6 @@ choose between Python 2.6 and Python 2.7.
Then you install the PyGTK All-in-one version that matches the Python version
you choose above. It's that easy!
-Note: There are currently no 64 bit builds of PyGTK All-in-one!
Migrating from PyGTK+PyGObject+PyCairo packages
===============================================
@@ -66,14 +66,15 @@ for this you risk the following scenario:
- install PyCairo, PyGTK and PyGObject
- install PyGTK All-in-one
- uninstall PyCairo, PyGTK and PyGObject
- you now have a *broken* pygtk all-in-one installation
+ - you now have a *broken* pygtk all-in-one installation
This would also be a good time to remove the GTK+ runtime you've used with the
separate PyG* packages and to clean your PATH environment variable.
Note that the PyCaio, PyGObject, PyGTK, PyGoocanvas, PyGtkSourceView2 and PyRsvg
.exe installers (like any other .exe installer generated by distutils) sometimes
-leaves things behind when you uninstall them.
+leave things behind when you uninstall them.
+
Default installation
====================
@@ -86,6 +87,7 @@ To start a default PyGTK All-in-one installation, simply double click the
%WINDIR%\system32\msiexec.exe /i pygtk-all-in-one-X.X.X.winYY-pyZ.Z.msi
+
Custom installation
===================
@@ -147,25 +149,27 @@ UI (/q[n|b]) the automatic Python installation detection is skipped. In this
case setting the TARGETDIR property is required. You can also set the ALLUSERS
property if you want a system wide installation.
+
The PATH environment variable
=============================
The PyGTK All-in-one installer does not require you to fiddle with the PATH
environment variable. The PyGTK version that's installed with the all-in-one
installer takes care of loading the bundled GTK+ runtime on the PATH environment
variable on interpreter startup. As a consequence simply importing gobject,
-gtk, etc works out of the box. As an added advantage there is no possible way
+gtk, etc works out of the box. And as an added advantage there is no possible way
multiple GTK+ runtime versions on your system or user PATH environment variable
can interfere with PyGTK All-in-one.
+
Getting help
============
If something doesn't work as expected, you'll need to generate a couple of log
files before you'll be able to get help. It is simply impossible to determine
-why something went wrong without those log files!
+why something went wrong without these log files.
-If something went wrong when installing, you'll need both
+If something went wrong when installing, you'll need both:
- An installation log (install.log). Execute the following command from a Command Prompt (cmd.exe)::
@@ -180,19 +184,19 @@ the following command from a Command Prompt (cmd.exe)::
%WINDIR%\system32\msiexec.exe -x pygtk-all-in-one-X.X.X.winYY-pyZ.Z.msi /l*vx uninstall.log
-Known issues with 2.22.4
-========================
+Please consider compressing the log files you obtained before you send them
+by mail or attach them to a bug report. Those files can be quite large.
+If you do not have a compression program yes, 7-Zip from http://www.7-zip.org/
+is a good choice.
+
+
+Known issues
+============
- The bundled svg_pixbuf_loader does not seem to be compatible with the new,
split gdk-pixbuf-2.22.0. Other svg functionality works fine. See
https://bugzilla.gnome.org/show_bug.cgi?id=637742
-- On Windows 2000 you need gdiplus.dll:
-
- - Download the GDI+ Platform SDK redistributable from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6a63ab9c-df12-4d41-933c-be590feaa05a&displaylang=en
- - Execute the downloaded WindowsXP-KB975337-x86-ENU.exe and it will ask to extract some files.
- - Copy the extracted asms\\10\\msft\\windows\\gdiplus\\gdiplus.dll file to C:\\Python2X\\Lib\\site-packages\\gtk-2.0\\runtime\\bin
-
- In theory, Windows 2000 should be supported, but in practice the gtk+ binaries
on ftp.gnome.org are affected by libgio-2.0-0.dll needing the freeaddrinfo()
function wich is only available starting from Windows XP:
@@ -201,6 +205,14 @@ Known issues with 2.22.4
- related bug: https://bugzilla.gnome.org/show_bug.cgi?id=610502#c6
- related bug: https://bugzilla.gnome.org/show_bug.cgi?id=623128
- http://msdn.microsoft.com/en-us/library/ms737931%28v=vs.85%29.aspx
+
+- On Windows 2000 you need gdiplus.dll:
+
+ - Download the GDI+ Platform SDK redistributable from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6a63ab9c-df12-4d41-933c-be590feaa05a&displaylang=en
+ - Execute the downloaded WindowsXP-KB975337-x86-ENU.exe and it will ask to extract some files.
+ - Copy the extracted asms\\10\\msft\\windows\\gdiplus\\gdiplus.dll file to C:\\Python2X\\Lib\\site-packages\\gtk-2.0\\runtime\\bin
+
+
=================================
About the pygtk-installer project
=================================

0 comments on commit 4649817

Please sign in to comment.