https://community.esri.com/t5/arcgis-api-for-python-questions/quot-future-quot-parameter-in-featurelayer-methods/m-p/1221348#M7886 <P>A good place to post an "Issue" or Question which is more target to the team</P><P><A href="https://github.com/Esri/arcgis-python-api" target="_blank">Esri/arcgis-python-api: Documentation and samples for ArcGIS API for Python (github.com)</A></P> Wed, 12 Oct 2022 23:42:47 GMT DanPatterson 2022-10-12T23:42:47Z https://community.esri.com/t5/arcgis-api-for-python-questions/quot-future-quot-parameter-in-featurelayer-methods/m-p/1221343#M7885 <P>Related:&nbsp;<A href="https://community.esri.com/t5/arcgis-api-for-python-questions/is-there-an-example-for-how-to-use-the-returned/m-p/1221301" target="_blank" rel="noopener">https://community.esri.com/t5/arcgis-api-for-python-questions/is-there-an-example-for-how-to-use-the-returned/m-p/1221301</A></P><P>I went into the source code to try and figure out how setting "future=True" behaved in various methods for arcgis.features.FeatureLayer objects, such as delete_features() or edit_features().&nbsp; Here's a snippet from the end of delete_features(), found in ~env\Lib\site-packages\arcgis\features\layer.py:</P><P>&nbsp;</P><LI-CODE lang="python">if future is False: return self._con.post(path=delete_url, postdata=params) else: params["async"] = True import concurrent.futures executor = concurrent.futures.ThreadPoolExecutor(1) res = self._con.post(path=delete_url, postdata=params) time.sleep(2) future = executor.submit( self._status_via_url, *(self._con, res["statusUrl"], {"f": "json"}), ) executor.shutdown(False) return future</LI-CODE><P>&nbsp;</P><P>Somebody please correct me if I'm wrong, but isn't this implementation of a concurrent.futures.ThreadPoolExecutor pointless?&nbsp; Whether it's edit_features() or delete_features() or whatever, they're all only sending a single http POST request at the end of the day, and they all create only a single thread.&nbsp; As I understand it, the ThreadPoolExecutor will block the rest of the program until all its threads (well, just one here) finish and join back together.&nbsp; I'm also not sure the motivation behind the 2 second sleep.</P><P>Am I misunderstanding something?&nbsp; It seems like maybe they should instead be returning us all the stuff they pass to executor.submit() so that we can put together our own thread pool and send a bunch of requests at once.</P> Thu, 13 Oct 2022 00:39:20 GMT https://community.esri.com/t5/arcgis-api-for-python-questions/quot-future-quot-parameter-in-featurelayer-methods/m-p/1221343#M7885 SamSzotkowski 2022-10-13T00:39:20Z https://community.esri.com/t5/arcgis-api-for-python-questions/quot-future-quot-parameter-in-featurelayer-methods/m-p/1221348#M7886 <P>A good place to post an "Issue" or Question which is more target to the team</P><P><A href="https://github.com/Esri/arcgis-python-api" target="_blank">Esri/arcgis-python-api: Documentation and samples for ArcGIS API for Python (github.com)</A></P> Wed, 12 Oct 2022 23:42:47 GMT https://community.esri.com/t5/arcgis-api-for-python-questions/quot-future-quot-parameter-in-featurelayer-methods/m-p/1221348#M7886 DanPatterson 2022-10-12T23:42:47Z https://community.esri.com/t5/arcgis-api-for-python-questions/quot-future-quot-parameter-in-featurelayer-methods/m-p/1221360#M7888 <P>Thank you, I'll consider posting there after I solidify my understanding a bit more, but there's not much info out there so I'm hoping someone in this community has actually used these parameters and either got it to work or came to the same conclusion as me.</P> Thu, 13 Oct 2022 00:37:32 GMT https://community.esri.com/t5/arcgis-api-for-python-questions/quot-future-quot-parameter-in-featurelayer-methods/m-p/1221360#M7888 SamSzotkowski 2022-10-13T00:37:32Z