Per #1747, this is slightly unrelated. But after installing the netCD…

…F4 module on kiowa for /usr/local/met-python3/bin/python3, we should no longer need a custom PATH setting to get unit_python.xml to work. Reverting the change I made to it a couple of days ago to get it working.

test/xml/unit_python.xml

@@ -7,7 +7,6 @@
   <!ENTITY INPUT_DIR      "${MET_TEST_INPUT}">
   <!ENTITY OUTPUT_DIR     "${MET_TEST_OUTPUT}">
   <!ENTITY MET_PYTHON_EXE "/usr/local/python3/bin/python3">
-  <!ENTITY ANACONDA_BIN   "/usr/local/anaconda3-20190923/bin">
 
   <!ENTITY CONFIG_DIR      "&TEST_DIR;/config">
   <!ENTITY DATA_DIR_PYTHON "&INPUT_DIR;/python">
@@ -392,8 +391,7 @@
 
   <!-- Invokes Python pickle logic to read NUMPY text data -->
   <test name="python_numpy_plot_data_plane_pickle">
-    <exec>export PATH='&ANACONDA_BIN;:${PATH}'; \
-          &MET_BIN;/plot_data_plane</exec>
+    <exec>&MET_BIN;/plot_data_plane</exec>
     <env>
        <pair><name>MET_PYTHON_EXE</name> <value>&MET_PYTHON_EXE;</value></pair>
     </env>