Skip to content

Conversation

@WardLT
Copy link
Contributor

@WardLT WardLT commented Nov 29, 2025

Description

Expands the documentation about the concurrent.futures.Executor-based interface to Parsl (ParslPoolExecutor).

I've been using this more lately and had a conversation with @jan-janssen about it. So, it's probably past time we introduce it to users more clearly.

Changed Behaviour

Expands the documentation

Fixes

N/A

Type of change

  • Update to human readable text: Documentation/error messages/comments

@WardLT WardLT mentioned this pull request Nov 29, 2025
9 tasks
A few other grammar/style fixes too: avoiding the 2nd-person,
not repeating a word within the same paragraph.

3. *No Multiprocessing Objects*: Tools such as the :class:`multiprocessing.Queue` and
`synchronization primitives <https://docs.python.org/3/library/multiprocessing.html#synchronization-primitives>`_
may not work in Parsl without specific configuration of the :class:`multiprocessing.Manager`.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would simplify this to those objects will not work.

if you want to overlay your own self-constructed comms network using however you want, then so be it but you don't need to be tricked into thinking that's a good idea in this intro guide.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great point

The core concept of workflows is that Parsl Apps produce **Futures**
with all features from those in Python's :mod:`concurrent.futures` module and more.

The Parsl programs must contain a ``parsl.load`` statement to start
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not true, if you're passing in a config like with ParslPoolExecutor(config=config) as pool: ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep. That need fixing

workflow
exceptions
lifted_ops
logging
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is from your adjacent PR I think and doesn't belong here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops. Yea, I messed up my commits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants