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

Job execution does not work with ProcessPoolExecutor #29

Closed
agronholm opened this issue Sep 7, 2012 · 2 comments
Closed

Job execution does not work with ProcessPoolExecutor #29

agronholm opened this issue Sep 7, 2012 · 2 comments
Labels
bug major scheduler

Comments

@agronholm
Copy link
Owner

Originally reported by: Alex Grönholm (Bitbucket: agronholm, GitHub: agronholm)

APScheduler uses a custom thread pool to execute jobs. The API was intended so you could use any PEP 3148 compliant executor in its place. However, this does not work with ProcessPoolExecutor since the arguments are pickled and the target callable is one of the arguments.
@agronholm
Copy link
Owner Author

Original comment by Alex Grönholm (Bitbucket: agronholm, GitHub: agronholm):

I think I'll be reworking the executor model anyway so I'm moving this to 3.x.

@agronholm
Copy link
Owner Author

Original comment by Alex Grönholm (Bitbucket: agronholm, GitHub: agronholm):

APScheduler 3.0 has full support for process pools.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug major scheduler
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@agronholm