From: Daniel F <nan...@gm...> - 2005-09-05 16:14:31
|
Hi, I am running on py2exe 0.5.4 with python 2.4.1, (on winxp sp2) and when i freeze a .pyw file, it is exactly the same as when i freeze a .py file - the console window still shows up when running the exe. I would have thought that freezing a .pyw file would preserve the "no console" behavior of the .pyw. Is this a bug, or is it the way it's supposed to be? whether it is a bug or not, how would i create an exe that runs in the background without opening a console window, as if the script was running through pythonw, rather than python? any help appreciated! -d |
From: Bob I. <bo...@re...> - 2005-09-05 16:39:42
|
On Sep 5, 2005, at 9:14 AM, Daniel F wrote: > I am running on py2exe 0.5.4 with python 2.4.1, (on > winxp sp2) and when i freeze a .pyw file, it is exactly > the same as when i freeze a .py file - the console > window still shows up when running the exe. If you use the console option in your setup.py, you get a console. It doesn't matter what the extension of the script is. -bob |
From: Daniel F <nan...@gm...> - 2005-09-05 16:59:19
|
On 9/5/05, Bob Ippolito <bo...@re...> wrote: >=20 > On Sep 5, 2005, at 9:14 AM, Daniel F wrote: >=20 > > I am running on py2exe 0.5.4 with python 2.4.1, (on > > winxp sp2) and when i freeze a .pyw file, it is exactly > > the same as when i freeze a .py file - the console > > window still shows up when running the exe. >=20 > If you use the console option in your setup.py, you get a console. > It doesn't matter what the extension of the script is. >=20 > -bob ah, cool, changing the setup.py to 'windows=3D' rather than 'console=3D' works perfectly. thanks for the quick reply! :) -d |
From: Daniel F <nan...@gm...> - 2005-09-05 17:15:05
|
On 9/5/05, Daniel F <nan...@gm...> wrote: > On 9/5/05, Bob Ippolito <bo...@re...> wrote: > > > > On Sep 5, 2005, at 9:14 AM, Daniel F wrote: > > > > > I am running on py2exe 0.5.4 with python 2.4.1, (on > > > winxp sp2) and when i freeze a .pyw file, it is exactly > > > the same as when i freeze a .py file - the console > > > window still shows up when running the exe. > > > > If you use the console option in your setup.py, you get a console. > > It doesn't matter what the extension of the script is. > > > > -bob >=20 > ah, cool, changing the setup.py to 'windows=3D' rather than 'console=3D' > works perfectly. thanks for the quick reply! :) >=20 > -d >=20 another related question. if i want to create two exe's, one to run with console, and one without, from the same python script, how would i do that? if i put something like this in the setup.py: console =3D ["script.pyw"], windows =3D ["script.pyw"], then console option creates an exe called script.exe, then windows option creates an exe, and overwrites the console version of script.exe (as expected). is there a way to specify an option for the filename of the target exe to be created, from console and windows options? something like: windows =3D [=20 {=20 "script": "script.pyw",=20 "target_filename": "blabla.exe" }=20 ],=20 i know i could just make a copy of the script.pyw and name them differently, but i would like to avoid that since it would be a pain to do every time. -d |
From: Thomas H. <th...@py...> - 2005-09-05 17:47:43
|
Daniel F <nan...@gm...> writes: > On 9/5/05, Daniel F <nan...@gm...> wrote: >> On 9/5/05, Bob Ippolito <bo...@re...> wrote: >> > >> > On Sep 5, 2005, at 9:14 AM, Daniel F wrote: >> > >> > > I am running on py2exe 0.5.4 with python 2.4.1, (on >> > > winxp sp2) and when i freeze a .pyw file, it is exactly >> > > the same as when i freeze a .py file - the console >> > > window still shows up when running the exe. >> > >> > If you use the console option in your setup.py, you get a console. >> > It doesn't matter what the extension of the script is. >> > >> > -bob >> >> ah, cool, changing the setup.py to 'windows=' rather than 'console=' >> works perfectly. thanks for the quick reply! :) >> >> -d >> > another related question. if i want to create two exe's, one to run > with console, and one without, from the same python script, how would > i do that? if i put something like this in the setup.py: > > console = ["script.pyw"], > windows = ["script.pyw"], > > then console option creates an exe called script.exe, then windows > option creates an exe, and overwrites the console version of > script.exe (as expected). > > is there a way to specify an option for the filename of the target exe > to be created, from console and windows options? lib/site-packages/samples/advanced demonstrates this. Basically you use class instances or dictionaries in the console and windows lists, and use the dest_base instance variable or key to specify the basename of the exe. I'll insert a pointer to the samples into the web-page for the new release. Thomas |
From: fred d. <fre...@gm...> - 2005-09-09 22:55:27
|
Daniel F <nanotube <at> gmail.com> writes: > > Hi, > > I am running on py2exe 0.5.4 with python 2.4.1, (on > winxp sp2) and when i freeze a .pyw file, it is exactly > the same as when i freeze a .py file - the console > window still shows up when running the exe. > > I would have thought that freezing a .pyw file would > preserve the "no console" behavior of the .pyw. > > Is this a bug, or is it the way it's supposed to be? > > whether it is a bug or not, how would i create an exe that > runs in the background without opening a console > window, as if the script was running through pythonw, > rather than python? > this is how i do it after lookint at how other people did it. ############################3 setup( windows = [ {"script": "simple.py", "dest_base" : OutputName, "icon_resources": [(1, "pc.ico")], "version": "1.5.0", "copyright": "julian ceasern", }, #{"script": "print_all_options.py", # "icon_resources": [(1, "pc.ico")] #}, ], #console=[{"script": "simple.py", # "dest_base" : OutputName + "Console", # "icon_resources": [(1, "pc.ico")], # "version": "1.1.1", # "copyright": "julian ceaser", # },] # ) ############################3 |
From: Daniel F <nan...@gm...> - 2005-09-11 02:48:30
|
> lib/site-packages/samples/advanced demonstrates this. Basically you use > class instances or dictionaries in the console and windows lists, and > use the dest_base instance variable or key to specify the basename of > the exe. > > I'll insert a pointer to the samples into the web-page for the new > release. > thanks for the help! for future reference, the following in setup.py works to create two different exe's from one script: ------------------ console =3D [ { "script": "script.pyw", "dest_base": "script_debug" } ], windows =3D [ { "script": "script.pyw", "dest_base": "script" } ], ------------------- -d |