APScheduler 3.7.0 released

[Alex Grönholm]

I've released APScheduler 3.7.0 yesterday. I figured that since the work
on v4.0 is taking longer than I initially hoped, it would be prudent to
at least fix a bunch of persistent bugs and shortcomings in the current
release branch. The new release contains a total of 13 fixes to various
annoyances. Python 3.4 support was phased out, as it's long since
reached its end of life. APScheduler 4.0, on the other hand, is expected
to drop at least Python 3.5 support, likely 3.6 as well.

There won't be any more feature releases on the 3.x series. Regressions
will be fixed, but design problems will have to be dealt with in the 4.x
series.

[schatur...@gmail.com]

Hi,

I want to print the next run time of a particular job every time before the job is triggered. I've learned about get_jobs, but it only prints the next run time only once. Can you please tell me how can i print the next run time every time. I'm sorry if the answer is very obvious as I'm new to this module. I've attached the code snippet below. Thanks in advance.

[Alex Grönholm]

You can subscribe to executor events using scheduler.add_listener(). See here: https://apscheduler.readthedocs.io/en/stable/userguide.html#scheduler-events

You will want to inspect every JobExecutionEvent and get the scheduled_run_time attribute in it.

Let me know if you have trouble getting this to work.

--
You received this message because you are subscribed to the Google Groups "APScheduler" group.
To unsubscribe from this group and stop receiving emails from it, send an email to apscheduler...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/apscheduler/90c850c4-9177-4432-bef9-552534d8ace3n%40googlegroups.com.

[schatur...@gmail.com]

Can you please explain how "class apscheduler.events.JobSubmissionEvent(code, job_id, jobstore, scheduled_run_times)" works.

[Alex Grönholm]

Such an event is emitted every time a job has been submitted to the designated executor. The "scheduled_run_times" property is a list of datetimes the job was supposed to have been started on, after the last run time of the job up until the present time (can be multiple values when coalescing is enabled).

To view this discussion on the web visit https://groups.google.com/d/msgid/apscheduler/d5b99c56-411a-4f0c-a812-c5796b5cb3ean%40googlegroups.com.

[Sukrati Chaturvedi]

Thanks! Can I request you to give an example demonstrating the use of "scheduler.add_listener()"  for  printing next run time everytime the job is triggered so that it can be more clear to me.

To view this discussion on the web visit https://groups.google.com/d/msgid/apscheduler/930a461d-0d48-ef13-8acf-600247b1dd32%40nextday.fi.

[Alex Grönholm]

So I wouldn't always have to write example code for everyone, I'd like to ask if you've read this part of the documentation: https://apscheduler.readthedocs.io/en/stable/userguide.html#scheduler-events

Is there something I didn't explain properly here?

To view this discussion on the web visit https://groups.google.com/d/msgid/apscheduler/CAGhEfcRjjPa-wCm_x6aOwuVDaMDghA5Pkm1FNeAMFb4wf3D7hA%40mail.gmail.com.

[Sukrati Chaturvedi]

Sorry, I didn't mean anything like that.And yes, I have read the mentioned part of documentation a few times but it's me who is not able to understand how this thing can be embedded in my program. 

You received this message because you are subscribed to a topic in the Google Groups "APScheduler" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/apscheduler/MwIHiRkOAD8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to apscheduler...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/apscheduler/a9ebd9d6-3388-f3a5-76ba-6b4052fe37dd%40nextday.fi.

[Alex Grönholm]

Well, that documentation section has an actual example, so you need to tell me what part you're having difficulties with so that I can assist you.

To view this discussion on the web visit https://groups.google.com/d/msgid/apscheduler/CAGhEfcSSz4N%3DknD4vdf5MmQF%2Br3KFiq6TX2GmoQgCAO%3DmoUMsw%40mail.gmail.com.

[Sukrati Chaturvedi]

Hi Alex,

Thanks for all of your support. I've another doubt regarding apscheduler.  Is there any possible way to get the list of all the jobs that have been paused. If yes, how can we do that?

To view this discussion on the web visit https://groups.google.com/d/msgid/apscheduler/4921a33d-9d3d-ca08-992d-d88a488b8804%40nextday.fi.

[Alex Grönholm]

You can get a list of all jobs using scheduler.get_jobs() (after the scheduler has been started). You can then identify paused jobs by looking at the next_run_time attribute which is None for paused jobs.

To view this discussion on the web visit https://groups.google.com/d/msgid/apscheduler/CAGhEfcSRB91rd2%3DvZtXSSgnGSDQi6PoyNxJpFr053OB%3DNQkOJg%40mail.gmail.com.

[Sukrati Chaturvedi]

Thanks.It worked. Also, is there any documentation for queuing disciplines and setting preemptive and non-preemptive priorities of jobs in APScheduler 

To view this discussion on the web visit https://groups.google.com/d/msgid/apscheduler/6126db4f-ed9b-24c1-11f7-6e0aa267b133%40nextday.fi.

[Alex Grönholm]

There is no documentation for that because there is no such feature in APScheduler. If you want something like that, you'll have to implement it yourself.

To view this discussion on the web visit https://groups.google.com/d/msgid/apscheduler/CAGhEfcStfu4mr7Dk24Lu4sAoXGO2nz%2BCcOgK-T96-_K1KHybuw%40mail.gmail.com.