From: Mark H. <ski...@gm...> - 2009-03-19 22:15:13
|
I think this will be fixed in Python 2.6.2; you should either revert to 2.5, wait for 2.6.2, or build 2.6 yourself from sources. Cheers, Mark On 19/03/2009 7:35 PM, Paul Sijben wrote: > I am using come custom python modules in my python 2.6 project, I have > compiled the modules nicely with visual studio but then the problems > started, once I made it all into an executable with py2exe but the > standard Visual Studio dlls could not be found. > > So I included the Visual redist dlls into my distributed code and made > some manifest to get it all to work on XP. (attached) > > Now I find that these dlls cause an R6034 error on Vista, the now > infamous dll hell. > > Is there a standard way to avoid this and have an app that works on both > XP and Vista? > > Paul |
From: Paul S. <si...@pe...> - 2009-03-20 06:06:14
|
Mark Hammond wrote: > I think this will be fixed in Python 2.6.2; you should either revert > to 2.5, wait for 2.6.2, or build 2.6 yourself from sources. Ouch that is bad news. What is different between the 2.6 that I could build from sources (using the current visual studio) and the released one? Paul > > Cheers, > > Mark > > On 19/03/2009 7:35 PM, Paul Sijben wrote: >> I am using come custom python modules in my python 2.6 project, I have >> compiled the modules nicely with visual studio but then the problems >> started, once I made it all into an executable with py2exe but the >> standard Visual Studio dlls could not be found. >> >> So I included the Visual redist dlls into my distributed code and made >> some manifest to get it all to work on XP. (attached) >> >> Now I find that these dlls cause an R6034 error on Vista, the now >> infamous dll hell. >> >> Is there a standard way to avoid this and have an app that works on both >> XP and Vista? >> >> Paul |
From: Mark H. <mha...@sk...> - 2009-03-20 21:53:02
|
> Mark Hammond wrote: > > I think this will be fixed in Python 2.6.2; you should either revert > > to 2.5, wait for 2.6.2, or build 2.6 yourself from sources. > Ouch that is bad news. Why is moving back to 2.5 such a burden? > What is different between the 2.6 that I could build from sources > (using > the current visual studio) and the released one? Fixes to the way imports are done were checked in after 2.6.1 Mark |
From: Paul S. <si...@pe...> - 2009-03-21 06:32:14
|
Mark Hammond wrote: >> Mark Hammond wrote: >> >>> I think this will be fixed in Python 2.6.2; you should either revert >>> to 2.5, wait for 2.6.2, or build 2.6 yourself from sources. >>> >> Ouch that is bad news. >> > > Why is moving back to 2.5 such a burden? > because I have some custom modules. Compiling those for 2.5 requires a version of Visual Studio that is no longer available. > > >> What is different between the 2.6 that I could build from sources >> (using >> the current visual studio) and the released one? >> > > Fixes to the way imports are done were checked in after 2.6.1 > > aha so not just build from source but build from cvs/svn that makes sense. Do you have a concrete pointer which files to look at for this? (as I would need to port those changes to stackless python too, so building a complete checkout would be more of an issue I guess). Paul > Mark > > |
From: Mark H. <mha...@sk...> - 2009-03-21 23:48:23
|
> aha so not just build from source but build from cvs/svn that makes sense. > Do you have a concrete pointer which files to look at for this? http://bugs.python.org/issue4566 is the underlying issue with the affecting change. Cheers, Mark |
From: Paul S. <si...@pe...> - 2009-03-23 05:47:36
|
ah great, thanks. Since I am in a hurry to release, looks like I need to start compiling my own python.exe (especially since I am also using stackless) One question: After this patch do the manifests work for Vista or are they no longer needed? Paul Mark Hammond wrote: >> aha so not just build from source but build from cvs/svn that makes sense. >> > > >> Do you have a concrete pointer which files to look at for this? >> > > http://bugs.python.org/issue4566 is the underlying issue with the affecting > change. > > Cheers, > > Mark > > |
From: Mark H. <mha...@sk...> - 2009-03-23 06:10:28
|
An earlier patch removed the manifest from .pyd files causing the initial problem. After the patch I pointed at, the .pyd modules should now load even though they still don't have a manifest. Cheers, Mark ---- From: Paul Sijben [mailto:si...@pe...] Sent: Monday, 23 March 2009 4:47 PM To: Mark Hammond Cc: py2...@li... Subject: Re: [Py2exe-users] template to avoid manifest hell ah great, thanks. Since I am in a hurry to release, looks like I need to start compiling my own python.exe (especially since I am also using stackless) One question: After this patch do the manifests work for Vista or are they no longer needed? Paul Mark Hammond wrote: aha so not just build from source but build from cvs/svn that makes sense. Do you have a concrete pointer which files to look at for this? http://bugs.python.org/issue4566 is the underlying issue with the affecting change. Cheers, Mark |