Skip to content

Commit

Permalink
bpo-36814: ensure os.posix_spawn() handles None (GH-13144)
Browse files Browse the repository at this point in the history
Fix an issue where os.posix_spawn() would incorrectly raise a TypeError
when file_actions is None.
  • Loading branch information
tonybaloney authored and vstinner committed May 10, 2019
1 parent fce5ff1 commit 948ed8c
Show file tree
Hide file tree
Showing 3 changed files with 11 additions and 1 deletion.
9 changes: 9 additions & 0 deletions Lib/test/test_posix.py
Expand Up @@ -1550,6 +1550,15 @@ def test_specify_environment(self):
with open(envfile) as f:
self.assertEqual(f.read(), 'bar')

def test_none_file_actions(self):
pid = self.spawn_func(
self.NOOP_PROGRAM[0],
self.NOOP_PROGRAM,
os.environ,
file_actions=None
)
self.assertEqual(os.waitpid(pid, 0), (pid, 0))

def test_empty_file_actions(self):
pid = self.spawn_func(
self.NOOP_PROGRAM[0],
Expand Down
@@ -0,0 +1 @@
Fix an issue where os.posix_spawnp() would incorrectly raise a TypeError when file_actions is None.
2 changes: 1 addition & 1 deletion Modules/posixmodule.c
Expand Up @@ -5465,7 +5465,7 @@ py_posix_spawn(int use_posix_spawnp, PyObject *module, path_t *path, PyObject *a
goto exit;
}

if (file_actions != NULL) {
if (file_actions != NULL && file_actions != Py_None) {
/* There is a bug in old versions of glibc that makes some of the
* helper functions for manipulating file actions not copy the provided
* buffers. The problem is that posix_spawn_file_actions_addopen does not
Expand Down

0 comments on commit 948ed8c

Please sign in to comment.