Jean-Michel,
Jean-Michel Fauth wrote:
2009/4/8 Robin Dunn <robin@alldunn.com <mailto:robin@alldunn.com>>
Werner F. Bruhin wrote:
I see that rc1 for above is announced. Scanning the news.txt
I do not see any mention of the problem related to py2exe and
wxPython. Does anyone know if the relevant changes made it
into 2.6.2, making it worse while to start testing/working
with it?
I don't know about the py2exe issues, but my request to include a
reference to the common controls DLL in Python's manifest never
got any traction, so I don't expect that will be there. I'm close
to a solution for the problem implemented in wxPython's code however.
Werner,
In my understanding,
- the py2exe isssues are *mainly* related to the use of the new VS
compiler (SxS, ...)
- the wxPython issue is *mainly* a problem due to the miscellaneous manifest
files in the libraries (DLL, exe, pyd(?) )
I didn't install 2.6.2 but I installed the 3.1's. The installer does not
allow to install Python with the option "just for me", but forces the use
of the option "all users" (at least on Vista). That seems to indicate
an exe application created with py2exe with "local" libs is not more
possible or this has not be considered (if technically possible).
Thanks for the info. Will give 2.6.2 a try in a few weeks and see how far I get (not sure how far all the libraries are that I use).
Werner
The Python 2.6 serie and the Python 3 serie are compiled with the same compiler (VS2008) and are therfore presenting the same difficulties. It is a pure Python “issue”.
The “basic” libs are the libs used to run Python itself. Eg
Microsoft.VC90.CRT.manifest
msvcr90.dll
msvcm90.dll
msvcp90.dll
python26.dll or python30.dll or python31.dll
jmf
being compiled with the same compiler as used for the Python 3 srie, qualitatively the problem remaaspresents the same bottln
···
2009/4/9 Werner F. Bruhin werner.bruhin@free.fr
Jean-Michel,
…
I didn’t install 2.6.2 but I installed the 3.1’s. The installer does not
allow to install Python with the option “just for me”, but forces the use
of the option “all users” (at least on Vista). That seems to indicate
an exe application created with py2exe with “local” libs is not more
possible or this has not be considered (if technically possible).
Thanks for the info. Will give 2.6.2 a try in a few weeks and see how far I get (not sure how far all the libraries are that I use).
python@bdurham.com wrote:
Mike,
if you're a Windows developer that wants to help, let me know.
This statement referred to my project of getting developers to work to provide executables for third party packages that don't have them (like the way people submit projects to debian or ubuntu packagers). I called it the "Python Extension Building Network". Helping with wxPython is good too!
I subscribe to python-list, wxpython-users, and the py2exe mailing lists
and I've read the traffic regarding problems with Python 2.6x/3.x,
wxPython, and Py2exe. Unfortunately, I'm still confused about the
*exact* problem(s) that need to be fixed in order for these 3 products
to work together smoothly.
My understanding is:
1. The root cause of all the problems is the use of the new MS VS2008 MS
C runtime files and the fact that the Python runtime and wxPython DLL's
use mis-matched manifest files ???
This is my impression as well. Robin posted a good link that described the issue last month. I think this is it: http://www.tejerodgers.com/snippets/2009/why-wxpython-crashes-python-26/
2. The wxPython/wxWidgets DLL's were compiled with MS VS 2005 C runtime
files ???
I know Robin said he has VS2008, so I assume that is what he used for the py2.6 installer...
For anyone reading the archives, the previous two sentences are
conjecture - not statements of fact.
I'm willing to help, but I need a more clear description of the problem.
Malcolm
Robin said he had a fix that was almost baked in the original reply to the OP. If you want to help him, drop him a line. He's pretty open to help.
···
-------------------
Mike Driscoll
Blog: http://blog.pythonlibrary.org
Jean-Michel,
Jean-Michel Fauth wrote:
2009/4/9 Werner F. Bruhin <werner.bruhin@free.fr <mailto:werner.bruhin@free.fr>>
Jean-Michel,
...
I didn't install 2.6.2 but I installed the 3.1's. The
installer does not
allow to install Python with the option "just for me", but
forces the use
of the option "all users" (at least on Vista). That seems to
indicate
an exe application created with py2exe with "local" libs is
not more
possible or this has not be considered (if technically possible).
Thanks for the info. Will give 2.6.2 a try in a few weeks and see
how far I get (not sure how far all the libraries are that I use).
The Python 2.6 serie and the Python 3 serie are compiled with the same compiler (VS2008) and are therfore presenting the same difficulties. It is a *pure* Python "issue".
The "basic" libs are the libs used to run Python itself. Eg
Microsoft.VC90.CRT.manifest
msvcr90.dll
msvcm90.dll
msvcp90.dll
python26.dll or python30.dll or python31.dll
I am aware of this. When I mentioned libraries above I am not thinking of the standard Python stuff but of things such as matplotlib, sqlalchemy, kinterbasdb etc.
Will have to check each of them, but noted lately that some of the announcements mention 2.6 compatibility, but often not yet 3.x.
Werner