parsemail.sh: don't set the python version

This is to fix using the wrong python version when inside a virtualenv.

Signed-off-by: Ali Alnubani <alialnu@mellanox.com>
Signed-off-by: Stephen Finucane <stephen@that.guru>
(cherry picked from commit 951a58e)

Author: alialnu

patchwork/bin/parsemail-batch.sh

@@ -23,7 +23,7 @@ BIN_DIR=$(dirname "$0")
 PATCHWORK_BASE=$(readlink -e "$BIN_DIR/../..")
 
 if [ -z "$PW_PYTHON" ]; then
-    PW_PYTHON=python2
+    PW_PYTHON=python
 fi
 
 if [ -z "$DJANGO_SETTINGS_MODULE" ]; then

patchwork/bin/parsemail.sh

@@ -23,7 +23,7 @@ BIN_DIR=$(dirname "$0")
 PATCHWORK_BASE=$(readlink -e "$BIN_DIR/../..")
 
 if [ -z "$PW_PYTHON" ]; then
-    PW_PYTHON=python2
+    PW_PYTHON=python
 fi
 
 if [ -z "$DJANGO_SETTINGS_MODULE" ]; then

releasenotes/notes/use-system-python-parsemail-9b161cebfd7d6159.yaml

@@ -0,0 +1,7 @@
+---
+fixes:
+  - |
+    The ``parsemail.sh`` and ``parsemail-batch.sh`` scripts, found in
+    ``patchwork/bin``, will now default to using ``python`` rather than
+    ``python2`` for calling ``manage.py``. This resolves an issue when
+    Patchwork is deployed with a virtualenv.