Asssertion in Windows debug build

[theller]

BPO	1039
Nosy	@gvanrossum, @theller
Files	os.diff

^{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 = 'https://github.com/theller'
closed_at = <Date 2007-08-30.17:15:43.002>
created_at = <Date 2007-08-28.06:01:58.780>
labels = ['type-feature', 'OS-windows']
title = 'Asssertion in Windows debug build'
updated_at = <Date 2010-03-21.18:32:38.332>
user = 'https://github.com/theller'

bugs.python.org fields:

activity = <Date 2010-03-21.18:32:38.332>
actor = 'Alexander.Belopolsky'
assignee = 'theller'
closed = True
closed_date = <Date 2007-08-30.17:15:43.002>
closer = 'theller'
components = ['Windows']
creation = <Date 2007-08-28.06:01:58.780>
creator = 'theller'
dependencies = []
files = ['8338']
hgrepos = []
issue_num = 1039
keywords = []
message_count = 5.0
messages = ['55350', '55439', '55492', '101439', '101441']
nosy_count = 3.0
nosy_names = ['gvanrossum', 'theller', 'Alexander.Belopolsky']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue1039'
versions = ['Python 3.0']

[theller]

In a windows debug build, an assertion is triggered when os.execvpe is
called with an empty argument list:

self.assertRaises(OSError, os.execvpe, 'no such app-', [], None)

The same problem is present in the trunk version.
Attached is a patch that fixes this, with a test.

[gvanrossum]

If it works for you, can you submit it?

[theller]

Applied in rev. 57731.

[AlexanderBelopolsky]

Link to revision: r57731

[AlexanderBelopolsky]

This issue was misclassified as an interpreter crash while in fact it was a bug in the underlying OS utility. Please see discussion in bpo-8154.

Since the fix changes behavior, it should be documented and a NEWS entry added.