![]() ![]() scripts), or is something other than third-party mods or blacklisted tools crashing my toolbox? If importing other scripts is not allowed, is the recommendation to throw all your functions into the toolbox? I was avoiding doing this, as it makes the code unreadable. Are you similarly unable to import other custom modules (i.e. def main(): proc subprocess.Popen( 'python3', '-u', '-m', 'rver', '8070', stdoutsubprocess.PIPE, stderrsubprocess.STDOUT) try: time.sleep(0.2) resp (' assert b'Directory listing' in resp.read() finally: proc.terminate() try: outs, municate(timeout0.2) print(' subprocess e. None of my tools do either of these things, but they do import custom modules that I wrote which use only native arcpy and Python mods. Looking at the sparse documentation, it appears that tools will not function if they call third-party modules, or use tools from a list of specific ArcGIS toolboxes. Also, time.sleep is used to suspend the operation of a script for a period of time. ![]() However, you will need to put the code you want to run continually inside the loop: /usr/bin/python while True: some python code that I want to keep on running. After installing and assigning the new 64-bit paths to my PYTHONPATH, I found that all my tools crash immediately without an explanation. Yes, you can use a while True: loop that never breaks to run Python code continually. I know about the potentials using and, etc., but the implementation seems too tedious, and wanted to see if 64-bit background geoprocessing would process these large datasets. I have been experiencing consistent crashes trying to process large datasets (>100,000 features) with my custom python toolbox tools, which I believe to be a memory issue, as smaller datasets run smoothly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |