John Cass

I have made an attempt to fix this over at the django-tenants project: see https://github.com/tomturner/django-tenants/pull/198. You might be able to re-use parts of that to create a pull request for...

+1

Would this achieve the same result and perhaps be easier to understand (untested)? ```python import functools from apscheduler.schedulers.blocking import BlockingScheduler from django import db class BlockingDBScheduler(BlockingScheduler): @util.close_old_connections def add_job(self, func,...

Ok. I think this approach could be handy for folks who **only** intend to schedule jobs that **always** read or mutate the database. The drawback is that if you use...

APScheduler will [remove the job](https://apscheduler.readthedocs.io/en/latest/userguide.html#removing-jobs) from the table automatically if there are no more runs scheduled to occur in the future for whatever reason. If you could post an example...

This is probably related to #161: we need to remove the dependency on `pytz` eventually though I am not sure if there is a hard deadline by which that should...

It's a warning, not an error, so you can just ignore it. If staring at the warning really bothers you then you can [enable a warning filter](https://docs.python.org/3/library/warnings.html#default-warning-filter) to suppress it...

Unfortunately APScheduler does not currently provide a mechanism for the job store to notify the scheduler when new jobs are added to the job store. But this feature is in...

We're waiting for APScheduler 4.0 to be released - you can track the status on that project's repository using the link to the issue in the comments above.

We could perhaps introduce a `DjangoJob.is_removed` `BooleanField` that is set when a job is removed by the scheduler via `remove_job`. This will also distinguish removed jobs from paused jobs (that...