John Cass
John Cass
I think we will wait until [AppScheduler 4.0 is released](https://github.com/agronholm/apscheduler/issues/465) and then re-assess the architecture changes that would be required for this project (including async support) in one go.
Closing due to lack of response - please reopen if required.
Looks like a missing Python dependency. If you made changes to you Python environment recently you could try running `pip install django-apscheduler` to refresh everything.
Thank you Eduardo, I have added you as a collaborator.
Thank you @TGoddessana, I have added you as a contributor.
Have a look at https://github.com/jcass77/django-apscheduler/blob/develop/docs/releasing.md, which explains the release procedures and how to merge `develop` into `main` as part of cutting a new release. I would drop Python 3.8, which...
[Release v0.7.0](https://github.com/jcass77/django-apscheduler/releases/tag/v0.7.0) has been cut and the test suite is passing against Python 3.9 - 3.12 and Django >= 4.2. Thank you @eduardopdev and @TGoddessana for stepping forward and helping...
Any chance of getting a test case contributed to test using multiple databases with this change?
#1401 addresses this requirement (at least as far as extension development is concerned). Is that sufficient for us to close this issue?
The Mopidy-Pandora backend extension currently spawns a separate thread for running `on_start` in order to fill caches and pre-load stuff that it will need by the time the user does...