run ( args, *, stdin = None, input = None, stdout = None, stderr = None, capture_output = False, shell = False, cwd = None, timeout = None, check = False, encoding = None, errors = None, text = None, env = None, universal_newlines = None, ** other_popen_kwargs ) ¶ Underlying Popen interface can be used directly. The recommended approach to invoking subprocesses is to use the run()įunction for all use cases it can handle. WebAssembly platforms for more information. This module does not work or is not available on WebAssembly platforms join ( (str (exit_code ) ,stdout ,stderr ) ) Ĭ:\Python27\ArcGIS圆410.1\python.exe īefore running, I have a batch file to set up some environment variables: offġ - make sure you're not calling subprocess.Popen with shell=True.Ģ - try passing a custom "env" to subprocess.Popen with the above env vars, i.e (completely untested.): env =os. Works for me in 64 bit python (using the following standalone script) and I have both 32 & 64 bit python installed. I haven't uninstalled the 32-bit version of Python, but that's my next step. Trying to fix things, I added a PYTHONPATH environment variable (which curiously didn't previously exist) that points to 'C:\Python27\ArcGIS圆410.1', but that didn't do the trick. My feeling is that for 'some reason' even though I am running the script from 64-bit python and launching the subprocesses as 64-bit python, when arcpy is being imported in the 64-bit python.exe subprocess, arcpy thinks that it is in 32-bit land still. Subprocess.Popen(, shell=False)įunny thing is that the 'lidar_hydro_child_v101.py' script (the import arcpy part) runs just fine stand alone in 64-bit and/or 32-bit Python, but just not when called as a subprocess. The subprocess call is to the 64bit version of Python, and I have verified that this is the exe that is launching under subprocess. However, when I attempt to launch a subprocess of arcpy with a 64 bit version of Python, the subprocess script fails upon attempting to import arcpy with the following error:Ĭ:\Python27\ArcGIS圆410.1 Python Traceback Info: File "\\snarf\am\div_lm\ds\gis\projects\lidar_hydro_all \lidar_hydro_child_v101.py", line 7, in import arcpy Python Error Info: : DLL load failed: %1 is not a valid Win32 application. Both versions of python will import and play with arcpy just fine. After installing the 'ArcGIS_BackgroundGP_for_Desktop_101sp1.exe' 64-bit geoprocessing package I have both the 32-bit and 64-bit versions of Python 2.7 on my machine. I have a script that relys on the 'subprocess' module to basically run seperate instances of arcpy as a parallel process.
0 kommentar(er)
