From: Gregory S. <sw...@gm...> - 2011-07-07 13:52:25
|
Sorry for the slow response, there was something wrong with my list subscription and I just saw the reply. I'm using Python 2.7 Yes, the exe was built, but I don't think it's a DLL issue. Or if it is, it's one I don't understand. Because I get the error even when I run it on the system I built the exe on, where the code was runs fine in script form. Shouldn't it at least run on the system without having to do any work with DLLs. Isn't the whole point that the system I build it on already has all the necessary DLLs? |
From: Werner F. B. <wer...@fr...> - 2011-07-09 10:05:22
|
On 07/07/2011 03:52 PM, Gregory Sloan wrote: > Sorry for the slow response, there was something wrong with my list > subscription and I just saw the reply. > > I'm using Python 2.7 > > Yes, the exe was built, but I don't think it's a DLL issue. Or if it > is, it's one I don't understand. Because I get the error even when I > run it on the system I built the exe on, where the code was runs fine > in script form. Shouldn't it at least run on the system without > having to do any work with DLLs. Isn't the whole point that the > system I build it on already has all the necessary DLLs? Python 2.6+ uses MS runtime v9 stuff and MS changed the way things works. I think if the manifest stuff is not correctly done then you might see errors even on the machine you build the exe. I haven't done much work with py 2.7 but initial casual tests showed that the Python 2.6 setup.py shown here still worked with Py 2.7. http://wiki.wxpython.org/py2exe-python26 Werner |