Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #15096
| Date | 2011-10-28 09:22 +0100 |
|---|---|
| From | Tim Golden <mail@timgolden.me.uk> |
| Subject | Re: spawnl issues with Win 7 access rights |
| References | (5 earlier) <4EA81B72.7040008@timgolden.me.uk> <mailman.2233.1319656830.27778.python-list@python.org> <98460dba-9e08-4d1a-8bf6-4e8fdbea2d0c@19g2000yqk.googlegroups.com> <4EA93421.1090905@timgolden.me.uk> <j8ccrv$ni8$2@dough.gmane.org> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.2279.1319790130.27778.python-list@python.org> (permalink) |
On 27/10/2011 20:53, Terry Reedy wrote: > On 10/27/2011 6:36 AM, Tim Golden wrote: >> On 27/10/2011 11:27, Propad wrote: >>> the suggestion to add the optional second parameter fixed the problem, >>> spawnl now works on the Win 7 computer I'm responsible for (with >>> Python 2.2). So the suggested cause seems to be right. >> >> FWIW, although it's not obvious, the args parameter to spawnl >> is intended to become the sys.args (in Python terms) of the >> newly-spawned process. Which is why the first element is expected >> to be the name of the process. It took me some time to realise >> this myself :) >> >> Anyway, glad we could be of help. > > Can we make this fix automatic for Win7 to fix #8036? > It's tempting, but I think not. In principle, the caller can pass any value as the first arg of spawn: it'll simply end up as sys.argv[0] in Python terms. If spawnl were the way of the future, I'd be inclined to argue for the change. As it it, though, I'd simply apply the patch and, possibly, add a line to the docs indicating that the args must be non-empty. (I started to import the patch yesterday but something got in the way; I'll see if I can get it done today). TJG
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
spawnl issues with Win 7 access rights Propad <npropadovic@googlemail.com> - 2011-10-24 05:43 -0700
Re: spawnl issues with Win 7 access rights Tim Golden <mail@timgolden.me.uk> - 2011-10-24 14:18 +0100
Re: spawnl issues with Win 7 access rights Propad <npropadovic@googlemail.com> - 2011-10-24 06:47 -0700
Re: spawnl issues with Win 7 access rights Terry Reedy <tjreedy@udel.edu> - 2011-10-24 18:16 -0400
Re: spawnl issues with Win 7 access rights Tim Golden <mail@timgolden.me.uk> - 2011-10-24 15:18 +0100
Re: spawnl issues with Win 7 access rights Terry Reedy <tjreedy@udel.edu> - 2011-10-24 18:14 -0400
Re: spawnl issues with Win 7 access rights Miki Tebeka <miki.tebeka@gmail.com> - 2011-10-24 17:21 -0700
Re: spawnl issues with Win 7 access rights Propad <npropadovic@googlemail.com> - 2011-10-25 00:01 -0700
Re: spawnl issues with Win 7 access rights Tim Golden <mail@timgolden.me.uk> - 2011-10-25 13:19 +0100
Re: spawnl issues with Win 7 access rights Terry Reedy <tjreedy@udel.edu> - 2011-10-25 21:11 -0400
Re: spawnl issues with Win 7 access rights Tim Golden <mail@timgolden.me.uk> - 2011-10-26 15:38 +0100
Re: spawnl issues with Win 7 access rights Terry Reedy <tjreedy@udel.edu> - 2011-10-26 15:20 -0400
Re: spawnl issues with Win 7 access rights Propad <npropadovic@googlemail.com> - 2011-10-27 03:27 -0700
Re: spawnl issues with Win 7 access rights Tim Golden <mail@timgolden.me.uk> - 2011-10-27 11:36 +0100
Re: spawnl issues with Win 7 access rights Terry Reedy <tjreedy@udel.edu> - 2011-10-27 15:53 -0400
Re: spawnl issues with Win 7 access rights Tim Golden <mail@timgolden.me.uk> - 2011-10-28 09:22 +0100
csiph-web