From: Jimmy R. <ji...@re...> - 2005-12-10 21:52:28
|
Thomas Heller wrote: >=20 > Larry Bates <lar...@we...> writes: >=20 > > Alex Mandel wrote: > >> This may a more general python question. > >> > >> I've got a program that uses a window specified in the setup.py > >> During the execution of some actions in the program I use a spawnv to > >> launch an cmd line executable. Everything works fine, there's just a > >> blip of the cmd window that flashes across the screen. I was wondering > >> if there's a way to suppress this, either in the setup.py or more > likely > >> some setting in the python code itself. > >> Note that the window does not show up when testing the program from > >> python code before building an exe. > > > > I use win32process module instead of spanv if I don't want to see > > this sort of artifact. >=20 > Same for me, with the subprocess module. Same here - subprocess is included with Python 2.4, and the last time I checked effbot.org had a link to download it for Python 2.3. There is an example at the bottom of the page at (watch out for URL wrapping here): http://starship.python.net/crew/theller/moin.cgi/Py2ExeSubprocessInterac tions You'll need the win32 extensions for the constant used there. The rest of that page has information on dealing with stdin/out/err pipes in windows/console py2exe apps. Jimmy |
From: Alex M. <tec...@wi...> - 2005-12-22 00:02:39
|
Jimmy Retzlaff wrote: > Thomas Heller wrote: > >>Larry Bates <lar...@we...> writes: >> >> >>>Alex Mandel wrote: >>> >>>>This may a more general python question. >>>> >>>>I've got a program that uses a window specified in the setup.py >>>>During the execution of some actions in the program I use a spawnv > > to > >>>>launch an cmd line executable. Everything works fine, there's just > > a > >>>>blip of the cmd window that flashes across the screen. I was > > wondering > >>>>if there's a way to suppress this, either in the setup.py or more >> >>likely >> >>>>some setting in the python code itself. >>>>Note that the window does not show up when testing the program from >>>>python code before building an exe. >>> >>>I use win32process module instead of spanv if I don't want to see >>>this sort of artifact. >> >>Same for me, with the subprocess module. > > > Same here - subprocess is included with Python 2.4, and the last time I > checked effbot.org had a link to download it for Python 2.3. There is an > example at the bottom of the page at (watch out for URL wrapping here): > > http://starship.python.net/crew/theller/moin.cgi/Py2ExeSubprocessInterac > tions > > You'll need the win32 extensions for the constant used there. The rest > of that page has information on dealing with stdin/out/err pipes in > windows/console py2exe apps. > > Jimmy > Thanks for the hints everyone, now I'm just struggling to make it happy, maybe someone could give reformatting my call a try. Original ------------ ogr2ogr = 'C:/Program Files/FWTools1.0.0a7/bin/ogr2ogr' os.spawnv(os.P_WAIT, ogr2ogr,["-update ","-append ",dir2," ",shpFile," -nln",layer2," ",layer1," -nlt POINT"]) ------------ Trys: ----------- subP.Popen([pyRapix.ogr2ogr,["-update ","-append ",dir2," ",shpFile," -nln",layer2," ",layer1," -nlt POINT"]]) ----------- test_cmd = "-update -append %s %s -nln %s %s -lnt POINT" % (outShpFile,shpFile,layer2,layer1) subP.Popen([ogr2ogr,test_cmd]) It finds the program ok, but the program doesn't like the way the arguments come across. How can I trap the arguments to see them? Both attempts on my part return a argument usage error from the program. Thanks - Alex |
From: Larry B. <lar...@we...> - 2005-12-22 16:36:24
|
Alex Mandel wrote: > Jimmy Retzlaff wrote: > >> Thomas Heller wrote: >> >>> Larry Bates <lar...@we...> writes: >>> >>> >>>> Alex Mandel wrote: >>>> >>>>> This may a more general python question. >>>>> >>>>> I've got a program that uses a window specified in the setup.py >>>>> During the execution of some actions in the program I use a spawnv >> >> >> to >> >>>>> launch an cmd line executable. Everything works fine, there's just >> >> >> a >> >>>>> blip of the cmd window that flashes across the screen. I was >> >> >> wondering >> >>>>> if there's a way to suppress this, either in the setup.py or more >>> >>> >>> likely >>> >>>>> some setting in the python code itself. >>>>> Note that the window does not show up when testing the program from >>>>> python code before building an exe. >>>> >>>> >>>> I use win32process module instead of spanv if I don't want to see >>>> this sort of artifact. >>> >>> >>> Same for me, with the subprocess module. >> >> >> >> Same here - subprocess is included with Python 2.4, and the last time I >> checked effbot.org had a link to download it for Python 2.3. There is an >> example at the bottom of the page at (watch out for URL wrapping here): >> >> http://starship.python.net/crew/theller/moin.cgi/Py2ExeSubprocessInterac >> tions >> >> You'll need the win32 extensions for the constant used there. The rest >> of that page has information on dealing with stdin/out/err pipes in >> windows/console py2exe apps. >> >> Jimmy >> > > Thanks for the hints everyone, now I'm just struggling to make it happy, > maybe someone could give reformatting my call a try. > > Original > ------------ > ogr2ogr = 'C:/Program Files/FWTools1.0.0a7/bin/ogr2ogr' > > os.spawnv(os.P_WAIT, ogr2ogr,["-update ","-append ",dir2," ",shpFile," > -nln",layer2," ",layer1," -nlt POINT"]) > ------------ > Trys: > ----------- > subP.Popen([pyRapix.ogr2ogr,["-update ","-append ",dir2," ",shpFile," > -nln",layer2," ",layer1," -nlt POINT"]]) > ----------- > test_cmd = "-update -append %s %s -nln %s %s -lnt POINT" % > (outShpFile,shpFile,layer2,layer1) > > subP.Popen([ogr2ogr,test_cmd]) > > > It finds the program ok, but the program doesn't like the way the > arguments come across. How can I trap the arguments to see them? > Both attempts on my part return a argument usage error from the program. > > Thanks - Alex > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click Just a shot in the dark: Why are you passing blank arguments in the argument list? os.spawnv(os.P_WAIT, ogr2ogr,["-update ","-append ",dir2," ",shpFile, "-nln",layer2," ",layer1," -nlt POINT"]) You have a blank argument after dir2 and one after layer2. This won't inserta a blank space, I believe it will cause a problem. I also don't think that the leading space in " -nit POINT" is necessary. spawnv will insert spaces between the arguments before passing to os to execute. Hope this helps. If not, try posting to comp.lang.python as this isn't really a py2exe question. -Larry Bates |