Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DOC add explanation on the name loky in README #276

Merged
merged 1 commit into from
Jan 7, 2021
Merged

DOC add explanation on the name loky in README #276

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,6 +105,19 @@ modules. Run the test suite using:

from the root of the project.

### Why was the project named `loky`?

While developping `loky`, we had some bad experiences trying to debug deadlocks
when using `multiprocessing.Pool` and `concurrent.ProcessPoolExecutor`, especially
when calling functions with non-picklable arguments or returned values at the
beginning of the project. When we had to chose a name, we had dealt with so many
deadlocks that we wanted some kind of invocation to repel them! Hence `loky`:
a mix of a god, locks and the `y` that make it somehow cooler and nicer :) (and
also less likely to result in name conflict in google results ^^).

Fixes to avoid those deadlocks in `concurrent.futures` were also contributed upstream
in Python 3.7+, as a less mystical way to repel the deadlocks :D

### Acknowledgement

This work is supported by the Center for Data Science, funded by the IDEX
Expand Down