From d68664ed6e5f31bf87ebfa01251434b4abe1a617 Mon Sep 17 00:00:00 2001 From: Ben Clifford Date: Mon, 9 Oct 2023 11:55:36 +0000 Subject: [PATCH] Add some discussion on DFK choice --- parsl/dataflow/futures.py | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/parsl/dataflow/futures.py b/parsl/dataflow/futures.py index 912d909af1..d12a3a7db7 100644 --- a/parsl/dataflow/futures.py +++ b/parsl/dataflow/futures.py @@ -124,6 +124,13 @@ def __getitem__(self, key: Any) -> AppFuture: # hack around circular imports for python_app from parsl.app.app import python_app + # TODO: it would be nice to avoid redecorating this each time, + # which was done to avoid import loops here -- but the DFK + # is not defined at import time, and so this decoration needs + # to happen at least once per DFK. So perhaps for implementation + # simplicity, this redecoration should always happen, as happens + # for example with the globus data provider. + # TODO: this should be run on the same DFK as is executing the # task that is associated with this future. That value isn't # easily available here (although probably the right thing to