Skip to content

feature/process pool executor support#1328

Closed
antlobach wants to merge 2 commits into
basilisp-lang:mainfrom
antlobach:feature/process-pool-executor-support
Closed

feature/process pool executor support#1328
antlobach wants to merge 2 commits into
basilisp-lang:mainfrom
antlobach:feature/process-pool-executor-support

Conversation

@antlobach
Copy link
Copy Markdown

With the help of Claude code and Codex, I've managed to implemented support for ProcessPoolExecutor using cloudpickle. It passes all tests locally on Python 3.14, but I wasn’t able to run tests on other Python versions.

I asked Codex to write a detailed overview of the implementation, which is in dev-notes/process-pool-executor-support.md

Please feel free to reject this if it’s not a fit, but I thought it might be of interest to review.

Implemented ProcessPoolExecutor support with cloudpickle-based serialization so Basilisp futures can run in subprocesses, including closures and dynamic bindings. Added robust handling for low FD limits and lifecycle cleanup to avoid 'too many open files' errors, and ensured pools created via binding shut down automatically to prevent resource leaks.

Also added a clean-cache Makefile target and expanded .gitignore for editor/temp files.
@chrisrink10
Copy link
Copy Markdown
Member

@antlobach thank you for your interest in the project and for the submission. Unfortunately, we have made the decision at this time to not accept AI generated contributions.

Setting aside the AI generation aspect, while I do think this is an interesting concept I'm not sure I want to bring in this additional dependency right now. Perhaps it can be spun out into a separate dependency?

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