Not sure exactly what is going on. I am relatively new to Python,
wxPython and py2exe. Seems py2exe complains that it can't find the
MSVCP90.dll file. I been doing looking all over the net for a
solution to this problem but can't seem to find one other then to run
Python 2.5.4. Can anyone help me out. I don't know what the hell
this winsxs stuff I hear about is.
Hi,
Not sure exactly what is going on. I am relatively new to Python,
wxPython and py2exe. Seems py2exe complains that it can't find the
MSVCP90.dll file. I been doing looking all over the net for a
solution to this problem but can't seem to find one other then to run
Python 2.5.4. Can anyone help me out. I don't know what the hell
this winsxs stuff I hear about is.
The winsxs stuff is the new and "improved" way of compiling programs.
Another term for it is Side-by-Side assemblies. There are a couple of
threads in the archives about this.
Werner has written a wiki entry on it:
http://wiki.wxpython.org/py2exe
And you can read about the original issue here (which is supposed to
be fixed with the new 2.8.10.1 release):
http://www.tejerodgers.com/snippets/2009/why-wxpython-crashes-python-26/
Finally, here are a couple of the more recent threads on the issue:
http://groups.google.com/group/wxPython-users/browse_frm/thread/d822b994ca44247d#
http://groups.google.com/group/wxPython-users/browse_frm/thread/b7296dbcea0755ee#
Hopefully one of those will get you going.
- Mike
···
On May 31, 9:38 pm, blewisjr86 <blewisj...@gmail.com> wrote:
Hi Mike,
Hi,
> Not sure exactly what is going on. I am relatively new to Python,
> wxPython and py2exe. Seems py2exe complains that it can't find the
> MSVCP90.dll file. I been doing looking all over the net for a
> solution to this problem but can't seem to find one other then to run
> Python 2.5.4. Can anyone help me out. I don't know what the hell
> this winsxs stuff I hear about is.The winsxs stuff is the new and "improved" way of compiling programs.
Another term for it is Side-by-Side assemblies. There are a couple of
threads in the archives about this.Werner has written a wiki entry on it:
And you can read about the original issue here (which is supposed to
be fixed with the new 2.8.10.1 release):http://www.tejerodgers.com/snippets/2009/why-wxpython-crashes-python-26/
Finally, here are a couple of the more recent threads on the issue:
Hopefully one of those will get you going.
- Mike
Those links were very helpful, however, it seems Werner fails to
mention where I get the manifest file on Windows Vista from. I looked
around and under WinSxS folder it seems I have 2 folders with dll's
for the crt.
x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.21022.8_none_bcb86ed6ac711f91
and
x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_e163563597edeada
Then under the Manifests folder I have 2 manifests matching the
folders above.
Not sure which one I should be grabbing the dll's and manifests for.
···
On Jun 1, 12:01 pm, Mike Driscoll <kyoso...@gmail.com> wrote:
On May 31, 9:38 pm, blewisjr86 <blewisj...@gmail.com> wrote:
Hi,
Hi Mike,
> Hi,
> > Not sure exactly what is going on. I am relatively new to Python,
> > wxPython and py2exe. Seems py2exe complains that it can't find the
> > MSVCP90.dll file. I been doing looking all over the net for a
> > solution to this problem but can't seem to find one other then to run
> > Python 2.5.4. Can anyone help me out. I don't know what the hell
> > this winsxs stuff I hear about is.> The winsxs stuff is the new and "improved" way of compiling programs.
> Another term for it is Side-by-Side assemblies. There are a couple of
> threads in the archives about this.> Werner has written a wiki entry on it:
> And you can read about the original issue here (which is supposed to
> be fixed with the new 2.8.10.1 release):>http://www.tejerodgers.com/snippets/2009/why-wxpython-crashes-python-26/
> Finally, here are a couple of the more recent threads on the issue:
>http://groups.google.com/group/wxPython-users/browse_frm/thread/d822b…
> Hopefully one of those will get you going.
> - Mike
Those links were very helpful, however, it seems Werner fails to
mention where I get the manifest file on Windows Vista from. I looked
around and under WinSxS folder it seems I have 2 folders with dll's
for the crt.x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.21022.8_none_bcb86ed6ac711f91
and
x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_e163563597edeada
Then under the Manifests folder I have 2 manifests matching the
folders above.Not sure which one I should be grabbing the dll's and manifests for.
As I understand it, you can use the manifest that comes with Python
2.6 OR you can extract the manifest somehow using ctypes. Robin
mentioned a way of doing that in the archives (not sure if one of my
links included that message or not). However, I am NOT a ctypes guru,
so I can't tell you how to do that.
Werner will hopefully jump in here too and give his two cents worth.
He's actually been playing with Python 2.6 + wxPython whereas I have
not.
- Mike
···
On Jun 1, 2:45 pm, Bill Lewis Jr <blewisj...@gmail.com> wrote:
On Jun 1, 12:01 pm, Mike Driscoll <kyoso...@gmail.com> wrote:
> On May 31, 9:38 pm, blewisjr86 <blewisj...@gmail.com> wrote:
Hi Mike,
···
On Jun 1, 4:18 pm, Mike Driscoll <kyoso...@gmail.com> wrote:
Hi,
On Jun 1, 2:45 pm, Bill Lewis Jr <blewisj...@gmail.com> wrote:
> Hi Mike,
> On Jun 1, 12:01 pm, Mike Driscoll <kyoso...@gmail.com> wrote:
> > Hi,
> > On May 31, 9:38 pm, blewisjr86 <blewisj...@gmail.com> wrote:
> > > Not sure exactly what is going on. I am relatively new to Python,
> > > wxPython and py2exe. Seems py2exe complains that it can't find the
> > > MSVCP90.dll file. I been doing looking all over the net for a
> > > solution to this problem but can't seem to find one other then to run
> > > Python 2.5.4. Can anyone help me out. I don't know what the hell
> > > this winsxs stuff I hear about is.> > The winsxs stuff is the new and "improved" way of compiling programs.
> > Another term for it is Side-by-Side assemblies. There are a couple of
> > threads in the archives about this.> > Werner has written a wiki entry on it:
> > And you can read about the original issue here (which is supposed to
> > be fixed with the new 2.8.10.1 release):> >http://www.tejerodgers.com/snippets/2009/why-wxpython-crashes-python-26/
> > Finally, here are a couple of the more recent threads on the issue:
> >http://groups.google.com/group/wxPython-users/browse_frm/thread/d822b…
> > Hopefully one of those will get you going.
> > - Mike
> Those links were very helpful, however, it seems Werner fails to
> mention where I get the manifest file on Windows Vista from. I looked
> around and under WinSxS folder it seems I have 2 folders with dll's
> for the crt.> x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.21022.8_none_bcb86ed6ac711f91
> and
> x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_e163563597edeada
> Then under the Manifests folder I have 2 manifests matching the
> folders above.> Not sure which one I should be grabbing the dll's and manifests for.
As I understand it, you can use the manifest that comes with Python
2.6 OR you can extract the manifest somehow using ctypes. Robin
mentioned a way of doing that in the archives (not sure if one of my
links included that message or not). However, I am NOT a ctypes guru,
so I can't tell you how to do that.Werner will hopefully jump in here too and give his two cents worth.
He's actually been playing with Python 2.6 + wxPython whereas I have
not.- Mike
Yea the main problem is the python directory does not contain a
manifest on Vista for some reason.
So I am not sure which manifest I need.
Bill Lewis Jr wrote:
Yea the main problem is the python directory does not contain a
manifest on Vista for some reason.
It's embedded in the python.exe, which is part of the problem that we've been trying to deal with. If you have VC++ there is a mt.exe tool that can extract it, otherwise you can pull it out using win32 APIs (via ctypes for example.)
···
--
Robin Dunn
Software Craftsman
Robin thx a lot. I happen to have stopped using c++ years ago so I think I will use this as a excuse to learn ctypes through python. Would you happen to know of any good resources off hand? If not thanks for your help anyway much appreciated.
···
Sent via BlackBerry by AT&T
-----Original Message-----
From: Robin Dunn <robin@alldunn.com>
Date: Mon, 01 Jun 2009 15:09:19
To: <wxPython-users@googlegroups.com>
Subject: [wxPython-users] Re: Python 2.6.2, wxPython, and py2exe issues
Bill Lewis Jr wrote:
Yea the main problem is the python directory does not contain a
manifest on Vista for some reason.
It's embedded in the python.exe, which is part of the problem that we've
been trying to deal with. If you have VC++ there is a mt.exe tool that
can extract it, otherwise you can pull it out using win32 APIs (via
ctypes for example.)
--
Robin Dunn
Software Craftsman
Hi,
Robin thx a lot. I happen to have stopped using c++ years ago so I think I will use this as a excuse to learn ctypes through python. Would you happen to know of any good resources off hand? If not thanks for your help anyway much appreciated.
Sent via BlackBerry by AT&T
Check out the official docs and FAQ:
http://wiki.python.org/moin/ctypes
http://docs.python.org/library/ctypes.html
http://www.python.org/doc/2.5.2/lib/ctypes-ctypes-tutorial.html
http://fsckd.com/2009/4/25/simple-python-ctypes-example/
I think the PyWin32 group also supports ctypes…but it looks like there is a really low-traffice ctypes-specific list here:
https://lists.sourceforge.net/lists/listinfo/ctypes-users
- Mike
···
On Mon, Jun 1, 2009 at 5:24 PM, blewisjr86@gmail.com wrote:
Bill,
Sorry for getting back into this thread a bit late - was not on the computer much over the weekend and I am also having ADSL connection problems.
Bill Lewis Jr wrote:
...
Those links were very helpful, however, it seems Werner fails to
mention where I get the manifest file on Windows Vista from.
I was mainly playing around on Windows 7 with Python 2.6.2 (as I wanted to be 100% sure not to mess up my dev environment), on Win7 (actually on all Windows versions except Vista) one can install "install for me only" which then puts the manifest and needed dll's into the Python 2.6 folder, otherwise they will go into the SxS folder.
I looked
around and under WinSxS folder it seems I have 2 folders with dll's
for the crt.
The manifest I show on the wiki page is one way of getting it.
x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.21022.8_none_bcb86ed6ac711f91
Python 2.6.2 is using the above version ("9.0.21022"), which is the one I posted on the wiki.
and
x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_e163563597edeada
You must have something else installed which uses the same dll's but a newer version.
Then under the Manifests folder I have 2 manifests matching the
folders above.
I think it is best to use the exactly the same version as Python 2.6 uses, so the 9.0.21022 one.
Not sure which one I should be grabbing the dll's and manifests for.
Will update the wiki page later this week to expand on all this a bit more.
Werner
Werner much appreciated no reply is ever too late. Especially if it helps. Looking forward to your wiki update.
···
Sent via BlackBerry by AT&T
-----Original Message-----
From: "Werner F. Bruhin" <wbruhin@gmail.com>
Date: Tue, 02 Jun 2009 11:13:42
To: <wxPython-users@googlegroups.com>
Subject: [wxPython-users] Re: Python 2.6.2, wxPython, and py2exe issues
Bill,
Sorry for getting back into this thread a bit late - was not on the
computer much over the weekend and I am also having ADSL connection
problems.
Bill Lewis Jr wrote:
...
Those links were very helpful, however, it seems Werner fails to
mention where I get the manifest file on Windows Vista from.
I was mainly playing around on Windows 7 with Python 2.6.2 (as I wanted
to be 100% sure not to mess up my dev environment), on Win7 (actually on
all Windows versions except Vista) one can install "install for me only"
which then puts the manifest and needed dll's into the Python 2.6
folder, otherwise they will go into the SxS folder.
I looked
around and under WinSxS folder it seems I have 2 folders with dll's
for the crt.
The manifest I show on the wiki page is one way of getting it.
x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.21022.8_none_bcb86ed6ac711f91
Python 2.6.2 is using the above version ("9.0.21022"), which is the one
I posted on the wiki.
and
x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_e163563597edeada
You must have something else installed which uses the same dll's but a
newer version.
Then under the Manifests folder I have 2 manifests matching the
folders above.
I think it is best to use the exactly the same version as Python 2.6
uses, so the 9.0.21022 one.
Not sure which one I should be grabbing the dll's and manifests for.
Will update the wiki page later this week to expand on all this a bit more.
Werner
Now that the release candidate for python 3.1 is out (and this time they have osx binary packages, yay), can Robin or anyone comment on when a build (a prerelease build would be fine) of wxpython for python 3.x will be available?
Thanks,
Stephen.
Stephen M. Gava wrote:
Now that the release candidate for python 3.1 is out (and this time they have osx binary packages, yay), can Robin or anyone comment on when a build (a prerelease build would be fine) of wxpython for python 3.x will be available?
I'm in the process of putting things in motion for the wxPython 3.x effort and along the way I plan on doing things that will make it easier to also have Python 3.x support. I don't think I'll put much effort into doing them concurrently, (but you never know) so at this point the best I can say is, "Sometime after wxPython 3.x for Python 2.x is ready."
···
--
Robin Dunn
Software Craftsman
Robin Dunn wrote:
Stephen M. Gava wrote:
Now that the release candidate for python 3.1 is out (and this time they have osx binary packages, yay), can Robin or anyone comment on when a build (a prerelease build would be fine) of wxpython for python 3.x will be available?
I'm in the process of putting things in motion for the wxPython 3.x effort and along the way I plan on doing things that will make it easier to also have Python 3.x support. I don't think I'll put much effort into doing them concurrently, (but you never know) so at this point the best I can say is, "Sometime after wxPython 3.x for Python 2.x is ready."
Ok, thanks Robin. Btw, you rule at ruling and stuff.
Stephen.
blewisjr86@gmail.com wrote:
Werner much appreciated no reply is ever too late. Especially if it helps. Looking forward to your wiki update.
wiki is updated, let us know if you get things working
Werner
Thanks will try it out when I get home from work.
···
Sent via BlackBerry by AT&T
-----Original Message-----
From: "Werner F. Bruhin" <wbruhin@gmail.com>
Date: Wed, 03 Jun 2009 12:20:57
To: <wxPython-users@googlegroups.com>
Subject: [wxPython-users] Re: Python 2.6.2, wxPython, and py2exe issues
blewisjr86@gmail.com wrote:
Werner much appreciated no reply is ever too late. Especially if it helps. Looking forward to your wiki update.
wiki is updated, let us know if you get things working
Werner
Ok I am still having issues and I am not sure why. Apparently py2exe
still can't fine the dll's been working on this for a few days now
everything seems to be coded right in the setup.py here it is.
···
++++++++++++++++++++++++++++++++++++++
from distutils.core import setup
import os
import py2exe
data =
# Populate data list
for files in os.listdir('C:/PyMSdlls/'):
tmp1 = 'C:/PyMSdlls/' + files
# Skip if it is a directory
if os.path.isfile(tmp1):
tmp2 = 'Microsoft.VC90.CRT', [tmp1]
data.append(tmp2)
setup(
windows=['SimpleApp.py'],
data_files = data
)
++++++++++++++++++++++++++++++++++++
On Jun 3, 8:32 am, blewisj...@gmail.com wrote:
Thanks will try it out when I get home from work.
Sent via BlackBerry by AT&T-----Original Message-----
From: "Werner F. Bruhin" <wbru...@gmail.com>Date: Wed, 03 Jun 2009 12:20:57
To: <wxPython-users@googlegroups.com>
Subject: [wxPython-users] Re: Python 2.6.2, wxPython, and py2exe issuesblewisj...@gmail.com wrote:
> Werner much appreciated no reply is ever too late. Especially if it helps. Looking forward to your wiki update.wiki is updated, let us know if you get things working
Werner
Bill,
Bill Lewis Jr wrote:
Ok I am still having issues and I am not sure why. Apparently py2exe
still can't fine the dll's been working on this for a few days now
everything seems to be coded right in the setup.py here it is.++++++++++++++++++++++++++++++++++++++
from distutils.core import setup
import os
import py2exedata =
# Populate data list
for files in os.listdir('C:/PyMSdlls/'):
tmp1 = 'C:/PyMSdlls/' + files
maybe your slashes?
If you use "glob" this is simpler, see lines 64 to 70 in the py2exe wiki page.
# Skip if it is a directory
if os.path.isfile(tmp1):
tmp2 = 'Microsoft.VC90.CRT', [tmp1]
I think this should be:
tmp2 = ('Microsoft.VC90.CRT', [tmp1])
data.append(tmp2)
setup(
windows=['SimpleApp.py'],
data_files = data
)
Werner
Made some changes however still having the same issue. py2exe is
blurting out that it can't fine MSVCP90.dll still.
I am getting to the point where it seems just more logical to
downgrade to python 2.5.4.
···
+++++++++++++++++++++++++++++++++++++++++++++
from distutils.core import setup
import os
import glob
import py2exe
import zlib
import shutil
shutil.rmtree("build", ignore_errors=True)
shutil.rmtree("dist", ignore_errors=True)
data =
baseFolder, progFolder = os.path.split(os.getcwd())
pyMSdlls = glob.glob(r"C:\PyMSdlls\*.*")
data += [("Microsoft.VC90.CRT", pyMSdlls),
("lib\Microsoft.VC90.CRT", pyMSdlls),]
setup(
data_files = data,
zipfile = "lib\library.zip",
windows=["SimpleApp.py"]
)
+++++++++++++++++++++++++++++++++++++++++++++
On Jun 6, 3:20 am, "Werner F. Bruhin" <wbru...@gmail.com> wrote:
Bill,
Bill Lewis Jr wrote:
> Ok I am still having issues and I am not sure why. Apparently py2exe
> still can't fine the dll's been working on this for a few days now
> everything seems to be coded right in the setup.py here it is.> ++++++++++++++++++++++++++++++++++++++
> from distutils.core import setup
> import os
> import py2exe> data =
> # Populate data list
> for files in os.listdir('C:/PyMSdlls/'):
> tmp1 = 'C:/PyMSdlls/' + filesmaybe your slashes?
If you use "glob" this is simpler, see lines 64 to 70 in the py2exe wiki
page.> # Skip if it is a directory
> if os.path.isfile(tmp1):
> tmp2 = 'Microsoft.VC90.CRT', [tmp1]I think this should be:
tmp2 = \('Microsoft\.VC90\.CRT', \[tmp1\]\)
> data.append(tmp2)
> setup(
> windows=['SimpleApp.py'],
> data_files = data
> )Werner
Bill,
Bill Lewis Jr wrote:
Made some changes however still having the same issue. py2exe is
blurting out that it can't fine MSVCP90.dll still.
This happens when you run setup.py py2exe? Or when you try to run the generated exe?
Does it say where it is looking for it?
I am getting to the point where it seems just more logical to
downgrade to python 2.5.4.+++++++++++++++++++++++++++++++++++++++++++++
from distutils.core import setup
import os
import glob
import py2exe
import zlib
import shutilshutil.rmtree("build", ignore_errors=True)
shutil.rmtree("dist", ignore_errors=True)data =
baseFolder, progFolder = os.path.split(os.getcwd())
pyMSdlls = glob.glob(r"C:\PyMSdlls\*.*")
data += [("Microsoft.VC90.CRT", pyMSdlls),
("lib\Microsoft.VC90.CRT", pyMSdlls),]setup(
data_files = data,
zipfile = "lib\library.zip",
windows=["SimpleApp.py"]
)
I am not sure but I think for zipfile to work you should also set the options "compressed=2" and "bundle_file=3"
Werner
Werner it does not generate anything at all. All it says is Can't
find MSVCP90.dll and the dist directory is empty. It does not mention
where it is looking for it.
···
On Jun 8, 6:16 am, "Werner F. Bruhin" <wbru...@gmail.com> wrote:
Bill,
Bill Lewis Jr wrote:
> Made some changes however still having the same issue. py2exe is
> blurting out that it can't fine MSVCP90.dll still.This happens when you run setup.py py2exe? Or when you try to run the
generated exe?Does it say where it is looking for it?
> I am getting to the point where it seems just more logical to
> downgrade to python 2.5.4.> +++++++++++++++++++++++++++++++++++++++++++++
> from distutils.core import setup
> import os
> import glob
> import py2exe
> import zlib
> import shutil> shutil.rmtree("build", ignore_errors=True)
> shutil.rmtree("dist", ignore_errors=True)> data =
> baseFolder, progFolder = os.path.split(os.getcwd())
> pyMSdlls = glob.glob(r"C:\PyMSdlls\*.*")
> data += [("Microsoft.VC90.CRT", pyMSdlls),
> ("lib\Microsoft.VC90.CRT", pyMSdlls),]> setup(
> data_files = data,
> zipfile = "lib\library.zip",
> windows=["SimpleApp.py"]
> )I am not sure but I think for zipfile to work you should also set the
options "compressed=2" and "bundle_file=3"Werner