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.

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

Evaluate job schedulers libraries alternatives compatible with twisted #1769

Open
evilaliv3 opened this issue Sep 24, 2016 · 3 comments
Open

Comments

@evilaliv3
Copy link
Member

evilaliv3 commented Sep 24, 2016

was "Evaluate to re-integrate APScheduler"


This ticket is to evaluate the re-integration of APScheduler as job scheduler.

APScheduler was removed by me implementing a basic scheduler time ago when APScheduler was not officially supporting the integration with Twisted. That was causing variuos incompatibility issues that i decided to solve by implementing basic scheduling functionalities on top of the twisted reactor.

Nowadays this has become a limit because of the impossibility to monitor/stop/pause/restart a job.

All this capabilities seems to be now available int APScheduler is now mentioning official twisted support.

In addition the library seems to benefit of active development, has an important quality assurance with 93% of code coverage.

This ticket is to track the tests of the re-integration and the various alternatives evaluations.

@evilaliv3 evilaliv3 added this to the 2016 September milestone Sep 24, 2016
@evilaliv3
Copy link
Member Author

Sometimes they come back: https://www.youtube.com/watch?v=89esFmj7sZk

@evilaliv3
Copy link
Member Author

@evilaliv3 evilaliv3 changed the title Evaluate to re-integrate APSScheduler Evaluate to re-integrate APScheduler Sep 25, 2016
@evilaliv3 evilaliv3 changed the title Evaluate to re-integrate APScheduler Evaluate job schedulers libraries alternatives compatible with twisted Sep 25, 2016
@evilaliv3
Copy link
Member Author

No suitable solution exists off the shelf up to October 2016.

This makes our current custom solution remain sadly the best choice :/

Putting the ticket out of any milestone.

@evilaliv3 evilaliv3 removed this from the 2016 September milestone Oct 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant