From e981a7fc1f658eb04eb30570b00061214d8fd4e0 Mon Sep 17 00:00:00 2001 From: Ayush Kathpalia Date: Wed, 15 Nov 2023 01:06:06 +0530 Subject: [PATCH] Updated Making your bot persistent (markdown) --- Making-your-bot-persistent.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Making-your-bot-persistent.md b/Making-your-bot-persistent.md index 9620cda..5d7a509 100644 --- a/Making-your-bot-persistent.md +++ b/Making-your-bot-persistent.md @@ -17,7 +17,7 @@ In V12.0b1 we added a persistence mechanism to `telegram.ext`. This wiki page is * `Job`'s and the `job_queue` is not supported. However, the current `JobQueue` backend [APScheduler](https://apscheduler.readthedocs.io/) has its own persistence logic that you can leverage. -See e.g. [`ptbcontrib/ptb_sqlalchemy_jobstore`](https://github.com/python-telegram-bot/ptbcontrib/tree/main/ptbcontrib/ptb_jobstores) +See e.g. [`ptbcontrib/ptb_jobstores`](https://github.com/python-telegram-bot/ptbcontrib/tree/main/ptbcontrib/ptb_jobstores) * For a special note about `Bot` instances, see [below](#storing-bots) ## Included persistence classes