Add python_exec kwarg to processutils.execute()3.25.0

This commit adds a new kwarg to the process_utils.execute() function to
specify the python executable to use when launching python to check
prlimits. This is necessary when processutils.execute() is called from
inside an API server running with uwsgi. In this case sys.executable is
uwsgi (because uwsgi links libpython.so and is actually the interpreter)
This doesn't work with the execute() function because it assumes the
cpython interpreter CLI is used for the arguments it uses to call the
prlimits module. To workaround this and enable API servers that may run
under uwsgi to use this those applications can simply pass in an
executable to use.

Longer term it might be better to migrate the prlimits usage to call
multiprocessing instead of subprocessing python. But that would require
a more significant rewrite of both processutils and prlimit to
facilitate that.

Change-Id: I0ae60f0b4cc3700c783f6018e837358f0e053a09
Closes-Bug: #1712463

1 files changed, 5 insertions, 0 deletions

diff --git a/releasenotes/notes/add-python-exec-kwarg-3a7a0c0849f9bb21.yaml b/releasenotes/notes/add-python-exec-kwarg-3a7a0c0849f9bb21.yaml
new file mode 100644
index 0000000..852d3fc
--- /dev/null
+++ b/releasenotes/notes/add-python-exec-kwarg-3a7a0c0849f9bb21.yaml
@@ -0,0 +1,5 @@
+---
+features:
+  - A new kwarg, ``python_exec`` is added to the execute() function in the
+    processutils module. This option is used to specify the path to the python
+    executable to use for prlimits enforcement.