No os.spawn*p* on Windows

[chrispalmer]

BPO	1166378
Nosy	@tiran

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2008-01-05.19:16:59.763>
created_at = <Date 2005-03-19.03:41:26.000>
labels = ['type-feature', 'library']
title = 'No os.spawn*p* on Windows'
updated_at = <Date 2008-01-05.19:16:59.762>
user = 'https://bugs.python.org/chrispalmer'

bugs.python.org fields:

activity = <Date 2008-01-05.19:16:59.762>
actor = 'christian.heimes'
assignee = 'none'
closed = True
closed_date = <Date 2008-01-05.19:16:59.763>
closer = 'christian.heimes'
components = ['Library (Lib)']
creation = <Date 2005-03-19.03:41:26.000>
creator = 'chris_palmer'
dependencies = []
files = []
hgrepos = []
issue_num = 1166378
keywords = []
message_count = 5.0
messages = ['54419', '54420', '54421', '54422', '59304']
nosy_count = 3.0
nosy_names = ['tzot', 'christian.heimes', 'chris_palmer']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = None
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue1166378'
versions = []

[chrispalmer]

You have the other spawn* functions, and exec*p*, but
no spawn*p*. It exists on Linux. These functions should
either exist everywhere or nowhere.

[tzot]

Logged In: YES
user_id=539787

This is documented (see
http://docs.python.org/lib/os-process.html). Python lib has
many places where underlying platform controls availability
of functionality.
Suggest closing of this bug or converting it to wishlist item.

[chrispalmer]

Logged In: YES
user_id=1242303

Okay, I read the page you point to. It provides no
explanation, just a statement of the fact I had already
discovered. An explanation would be nice.

Don't you think it's strange that these three conditions
should hold:

1. os.exec*p* are supported on Windows;
2. Windows systems have a PATH environment variable with the
   same meaning and use as UNIX; and yet
3. os.spawn*p* are not supported on Windows?

If there's some difference to how the environment is treated
or used between exec* and spawn* on Windows, wouldn't it be
easy to emulate the PATH-searching feature?

My options are to emulate the PATH-searching feature myself
and ignore os.spawn*p* on all platforms, or to use it when
it's present and only emulate it on Windows. The first
option is ridiculous, the second is ridiculous and ugly.

If you won't emulate the spawn*p* behavior -- it's three
lines of Python! -- it would help if you could at least
explain why, technically.

Thanks.

[tzot]

Logged In: YES
user_id=539787

This bug is *not* a bug, so it should be closed, and an
entry made in RFE (Request For Enhancements) aka wishlist.
Google has many pointers. See for example
http://mail.python.org/pipermail/python-dev/2003-April/034473.html
.
Patches are welcome (either code or documentation).

[tiran]

The subprocess is the successor of the various exec, popen and spawn
functions.