From: Aahz <aa...@py...> - 2009-10-27 21:58:49
|
Message http://osdir.com/ml/python.py2exe/2007-01/msg00003.html from the distant past seems to have produced no documentation that I can find. I tried updating http://py2exe.org/index.cgi/py2exeAndWindowsServices but it's immutable. Also, I'd appreciate it if someone could point me at docs that explain using objects instead of strings for setup() targets. -- Aahz (aa...@py...) <*> http://www.pythoncraft.com/ "You could make Eskimos emigrate to the Sahara by vigorously arguing -- at hundreds of screens' length -- for the wonder, beauty, and utility of snow." --PNH to rb in r.a.sf.f |
From: Thomas H. <th...@ct...> - 2009-10-28 19:50:30
|
Aahz schrieb: > Message http://osdir.com/ml/python.py2exe/2007-01/msg00003.html from the > distant past seems to have produced no documentation that I can find. I > tried updating > http://py2exe.org/index.cgi/py2exeAndWindowsServices > but it's immutable. Hm, I created a new account (for testing) and was possible to edit the page after I logged in. However, I did use Firefox, not lynx ;-). > Also, I'd appreciate it if someone could point me at docs that explain > using objects instead of strings for setup() targets. Hm, you could look into the examples bundled with py2exe itself, in Lib\site-packages\py2exe\examples subdirs. I do not remember if other docs exist. -- Thanks, Thomas |
From: Aahz <aa...@py...> - 2009-10-29 19:56:24
|
On Wed, Oct 28, 2009, Thomas Heller wrote: > Aahz schrieb: >> >> Message http://osdir.com/ml/python.py2exe/2007-01/msg00003.html from the >> distant past seems to have produced no documentation that I can find. I >> tried updating >> http://py2exe.org/index.cgi/py2exeAndWindowsServices >> but it's immutable. > > Hm, I created a new account (for testing) and was possible to edit the > page after I logged in. However, I did use Firefox, not lynx ;-). Lynx works fine -- I just missed the message about "password too short" creating my account. >> Also, I'd appreciate it if someone could point me at docs that explain >> using objects instead of strings for setup() targets. > > Hm, you could look into the examples bundled with py2exe itself, > in Lib\site-packages\py2exe\examples subdirs. Do you know whether using objects is a py2exe-ism or a distutils-ism? -- Aahz (aa...@py...) <*> http://www.pythoncraft.com/ "You could make Eskimos emigrate to the Sahara by vigorously arguing -- at hundreds of screens' length -- for the wonder, beauty, and utility of snow." --PNH to rb in r.a.sf.f |
From: Thomas H. <th...@ct...> - 2009-10-30 11:43:05
|
Aahz schrieb: > On Wed, Oct 28, 2009, Thomas Heller wrote: >> Aahz schrieb: >>> Also, I'd appreciate it if someone could point me at docs that explain >>> using objects instead of strings for setup() targets. >> >> Hm, you could look into the examples bundled with py2exe itself, >> in Lib\site-packages\py2exe\examples subdirs. > > Do you know whether using objects is a py2exe-ism or a distutils-ism? It is a py2exe-ism. -- Thanks, Thomas |
From: Aahz <aa...@py...> - 2009-10-30 17:14:25
|
On Fri, Oct 30, 2009, Thomas Heller wrote: > Aahz schrieb: >> On Wed, Oct 28, 2009, Thomas Heller wrote: >>> Aahz schrieb: >>>> >>>> Also, I'd appreciate it if someone could point me at docs that explain >>>> using objects instead of strings for setup() targets. >>> >>> Hm, you could look into the examples bundled with py2exe itself, >>> in Lib\site-packages\py2exe\examples subdirs. >> >> Do you know whether using objects is a py2exe-ism or a distutils-ism? > > It is a py2exe-ism. Okie-doke, updated http://py2exe.org/index.cgi/py2exeAndWindowsServices -- Aahz (aa...@py...) <*> http://www.pythoncraft.com/ "You could make Eskimos emigrate to the Sahara by vigorously arguing -- at hundreds of screens' length -- for the wonder, beauty, and utility of snow." --PNH to rb in r.a.sf.f |
From: Chris S. <csp...@ci...> - 2009-11-02 08:52:56
|
I upgraded my win32all package to version 214 yesterday and tried to run my program after bundling it with py2exe. The _memimporter command on line 98 of zipextimporter.py threw an exception. I reverted back to win32all version 212 and the error message went away. I wish I had saved the particular exception message, but in trying to get my program to work again, I lost the exception message. So if you are using py2exe and win32all, I'd suggest NOT updating to version 214. Stay on 212. Chris. |
From: Chris S. <csp...@ci...> - 2009-11-02 08:56:40
|
Of course I forgot the most important piece of this warning. The import error happened on the module "win32api.pyd". Chris. On Mon, 02 Nov 2009 03:39:50 -0500, Chris Spencer <csp...@ci...> wrote: >I upgraded my win32all package to version 214 yesterday and tried to >run my program after bundling it with py2exe. The _memimporter >command on line 98 of zipextimporter.py threw an exception. > >I reverted back to win32all version 212 and the error message went >away. > >I wish I had saved the particular exception message, but in trying to >get my program to work again, I lost the exception message. > >So if you are using py2exe and win32all, I'd suggest NOT updating to >version 214. Stay on 212. > >Chris. > >------------------------------------------------------------------------------ >Come build with us! The BlackBerry(R) Developer Conference in SF, CA >is the only developer event you need to attend this year. Jumpstart your >developing skills, take BlackBerry mobile applications to market and stay >ahead of the curve. Join us from November 9 - 12, 2009. Register now! >http://p.sf.net/sfu/devconference >_______________________________________________ >Py2exe-users mailing list >Py2...@li... >https://lists.sourceforge.net/lists/listinfo/py2exe-users |
From: Chris S. <csp...@ci...> - 2009-11-03 04:34:23
|
<shrug> In my code it works fine in 212. It doesn't work in 214. I guess I must be unlucky. Just one question, are you using 214 with py2exe in Windows 7? That MIGHT make a difference...maybe. Chris. On Tue, 03 Nov 2009 08:32:20 +1100, Mark Hammond <ski...@gm...> wrote: >On 3/11/2009 5:32 AM, Aahz wrote: >> On Mon, Nov 02, 2009, Chris Spencer wrote: >>> >>> I upgraded my win32all package to version 214 yesterday and tried to >>> run my program after bundling it with py2exe. The _memimporter >>> command on line 98 of zipextimporter.py threw an exception. >> >> I'm using py2exe with 214 and no difficulty. > >FYI, I am too and know many others who are too. > >> (Assuming I trust >> pywin32.version.text -- I can't figure out how to get the build number >> from the code.) > >That is the canonical version - even pythonwin opens and reads the >version from this file to display in its "about" box. > >Cheers, > >Mark > > >------------------------------------------------------------------------------ >Come build with us! The BlackBerry(R) Developer Conference in SF, CA >is the only developer event you need to attend this year. Jumpstart your >developing skills, take BlackBerry mobile applications to market and stay >ahead of the curve. Join us from November 9 - 12, 2009. Register now! >http://p.sf.net/sfu/devconference >_______________________________________________ >Py2exe-users mailing list >Py2...@li... >https://lists.sourceforge.net/lists/listinfo/py2exe-users |
From: Aahz <aa...@py...> - 2009-11-03 04:35:09
|
On Mon, Nov 02, 2009, Chris Spencer wrote: > > <shrug> In my code it works fine in 212. It doesn't work in 214. I > guess I must be unlucky. > > Just one question, are you using 214 with py2exe in Windows 7? That > MIGHT make a difference...maybe. Nope, I'm sticking with XP for now. -- Aahz (aa...@py...) <*> http://www.pythoncraft.com/ [on old computer technologies and programmers] "Fancy tail fins on a brand new '59 Cadillac didn't mean throwing out a whole generation of mechanics who started with model As." --Andrew Dalke |
From: Aahz <aa...@py...> - 2009-11-02 18:32:32
|
On Mon, Nov 02, 2009, Chris Spencer wrote: > > I upgraded my win32all package to version 214 yesterday and tried to > run my program after bundling it with py2exe. The _memimporter > command on line 98 of zipextimporter.py threw an exception. I'm using py2exe with 214 and no difficulty. (Assuming I trust pywin32.version.text -- I can't figure out how to get the build number from the code.) -- Aahz (aa...@py...) <*> http://www.pythoncraft.com/ [on old computer technologies and programmers] "Fancy tail fins on a brand new '59 Cadillac didn't mean throwing out a whole generation of mechanics who started with model As." --Andrew Dalke |
From: Mark H. <ski...@gm...> - 2009-11-02 21:33:25
|
On 3/11/2009 5:32 AM, Aahz wrote: > On Mon, Nov 02, 2009, Chris Spencer wrote: >> >> I upgraded my win32all package to version 214 yesterday and tried to >> run my program after bundling it with py2exe. The _memimporter >> command on line 98 of zipextimporter.py threw an exception. > > I'm using py2exe with 214 and no difficulty. FYI, I am too and know many others who are too. > (Assuming I trust > pywin32.version.text -- I can't figure out how to get the build number > from the code.) That is the canonical version - even pythonwin opens and reads the version from this file to display in its "about" box. Cheers, Mark |