Greetings Everyone- I too was running into problems attempting to get pygtk to work with python 2.6.5 on my windows XP machine. I attempted to install all of the various visual studio redistributables with no luck. I was finally able to resolve the issue by modifying my PATH environment variable. In particular, I had to make sure that the following paths were listed first in the PATH variable:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem; Then came my paths to python26, python26/scripts, GTK, etc. I hope this helps with what you're seeing as well. Good Luck. Todd Mark Schafer wrote: > > > > > > > > Hi Rafael, > thanks for the extra info. > I tried using the link you sent for the VC2008 redistributable - no > change :-( > I always install for all users - so that wasn't it either. > I believe I will wait for a new build based on 2.6.5 before continuing. > I think I could get it working by moving various files around but I > can't manage the time right now > (I am currently using pythoncard for my UI but I need to move to GTK+) > > Thanks for all the help and info, > Cheers, MarkS... > > Rafael Villar Burke (Pachi) wrote: > > > On 01/01/2001 1:33, John Stowers wrote: > > > On Tue, 2010-04-06 at 21:54 +1200, Mark Schafer wrote: > > > > Thanks for the advice Rafael, > Alas it has not worked. > I uninstalled python 2.6.5 and installed 2.6.4 > Then the same packages as before: > - pycairo-1.8.6.win32-py2.6.exe > - pygobject-2.20.0.win32-py2.6.exe > - pygtk-2.16.0+glade.win32-py2.6.exe > > But getting exact same error :-( > > I have installed the VC2008 redistributable (vcredist_x86.exe) and no > change > > > > AIUI it also depends on the version of python used to *generate* the > installer. Is this correct? > > > > Yes. AFAICT, 2.6.x versions up to 2.6.5 didn't have the patch to avoid > including a manifest that makes related libraries to include it. Now > that 2.6.5 doesn't have it, previous version generated libraries that > included the manifest break if they don't find a python dll with the > manifest. > > Stephen George also pointed that the SP1 version of the VC2008 > redistributable may be needed in some cases (perhaps when the extensions > were made in a system with them or the python executable included it). > > I still have to confirm that the SP1 version fixes the problem for one > user, as the initial VC2008 version didn't do it. Also, in the www some > people say that the installation method is also important, as the dlls > and manifests are installed in different places depending on whether the > installation is for all users (admin rights) or just for the current user. > > (It looks like VS 2010 will finally eliminate the manifest and will rely > on version numbers in the dll name to avoid dll version clashes, > finishing this new dll hell.) > > Regards, > > Rafael Villar Burke > _______________________________________________ > pygtk mailing list pygtk@daa.com.au > http://www.daa.com.au/mailman/listinfo/pygtk > Read the PyGTK FAQ: http://faq.pygtk.org/ > > > > > > > > > _______________________________________________ > pygtk mailing list pygtk@daa.com.au > http://www.daa.com.au/mailman/listinfo/pygtk > Read the PyGTK FAQ: http://faq.pygtk.org/ > -- View this message in context: http://old.nabble.com/Re%3A-Windows-7-issue-tp28125783p29065982.html Sent from the Gtk+ - Python mailing list archive at Nabble.com. _______________________________________________ pygtk mailing list pygtk@daa.com.au http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
