summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlex Grönholm <alex.gronholm@nextday.fi>2022-09-04 23:00:45 +0300
committerAlex Grönholm <alex.gronholm@nextday.fi>2022-09-04 23:00:57 +0300
commit4b98fb1ef7db49c05f9372d4f6878d214461381e (patch)
tree6d16d6c5f5f68ec3ef4125770c0b247896630d92
parent034586a876ab0b8a416462a4afba01774255d49e (diff)
downloadapscheduler-4b98fb1ef7db49c05f9372d4f6878d214461381e.tar.gz
Fixed references to run_until_stopped()
-rw-r--r--docs/userguide.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/userguide.rst b/docs/userguide.rst
index f9f1b50..fd88d1c 100644
--- a/docs/userguide.rst
+++ b/docs/userguide.rst
@@ -83,11 +83,11 @@ Running the scheduler
=====================
The scheduler can run either in the foreground, blocking on a call to
-:meth:`~apscheduler.schedulers.sync.Scheduler.run_until_complete`, or in the background
+:meth:`~apscheduler.schedulers.sync.Scheduler.run_until_stopped`, or in the background
where it does its work while letting the rest of the program run.
If the only intent of your program is to run scheduled tasks, then you should start the
-scheduler with :meth:`~apscheduler.schedulers.sync.Scheduler.run_until_complete`. But if
+scheduler with :meth:`~apscheduler.schedulers.sync.Scheduler.run_until_stopped`. But if
you need to do other things too, then you should call
:meth:`~apscheduler.schedulers.sync.Scheduler.start_in_background` before running the
rest of the program.