Maximum run count usage example about apscheduler HOT 5 CLOSED

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

I think that the documentation improvements made for 2.1.0 should cover this.

from apscheduler.

Original comment by Dariusz Suchojad (Bitbucket: dsuch, GitHub: dsuch):

Thanks, that did the trick.

from apscheduler.

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

You misunderstand. Just pass max_runs= to add_interval_job() or whatever. The job adding functions pass along all keyword arguments to Job.

from apscheduler.

Original comment by Dariusz Suchojad (Bitbucket: dsuch, GitHub: dsuch):

OK, but the apscheduler.job.Job's docs say "Job instances are created by the scheduler when adding jobs, and it should not be directly instantiated." and I haven't ever had a need to use this class directly before.

Could either the 'max_runs' parameter be added to Scheduler.add_interval_job and Scheduler.add_cron_job or the docstring updated so that users don't get an impression they shouldn't be tinkering with this class themselves?

On a related note, how does 'max_runs' influence one-time jobs? I mean, how can a job be both of a one-time type and have 'max_runs' provided? I'm asking because the changelog says the parameter is to do with all the jobs, not only interval-based and cron-style ones.

from apscheduler.

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

http://readthedocs.org/docs/apscheduler/en/latest/modules/job.html#apscheduler.job.Job

You can pass these as keyword arguments when adding a job. Perhaps I should point this out more clearly in the docs.

from apscheduler.