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

Jump to bottom

Support @processes(n) with ProcessPoolExecutor #1

Open
madisonmay opened this issue Aug 2, 2015 · 2 comments
Open

Support @processes(n) with ProcessPoolExecutor #1

madisonmay opened this issue Aug 2, 2015 · 2 comments

Comments

@madisonmay
Copy link
Owner

Current blocker is function serialization. A potential solution might use dill and override __getstate__ and __setstate__.
@madisonmay
Copy link
Owner Author

Currently partially functional. I'm running into issues when chaining together Tomorrow's because it's difficult to make the Tomorrow object serializable (since it overrides __getattr__). I'm confident there's a solution, just haven't been able to sort it out yet. A [WIP] PR should be up soon.

@cyh24
Copy link

cyh24 commented Oct 23, 2015

This project: multicpu let you set the number of the process and thread at one time. But, I can't find out a solution to use like @set_process_thread(cpu_num, thread_num). Do you have any ideas about that?

madisonmay pushed a commit that referenced this issue Feb 16, 2020
@oooeeee
Merge pull request #1 from oooeeee/python3-support
e6cf011 
Python3 support
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cyh24 @madisonmay