René's URL Explorer Experiment


Title: [Discussion:] ConversationHandler · Issue #2770 · python-telegram-bot/python-telegram-bot · GitHub

Open Graph Title: [Discussion:] ConversationHandler · Issue #2770 · python-telegram-bot/python-telegram-bot

X Title: [Discussion:] ConversationHandler · Issue #2770 · python-telegram-bot/python-telegram-bot

Description: Several ideas for changes and/or additions have been gathered in the v14 project, mentioned in the user group or issues or dwelled in the back of my head. So I'm writing this issue to keep track of them better. The following list of idea...

Open Graph Description: Several ideas for changes and/or additions have been gathered in the v14 project, mentioned in the user group or issues or dwelled in the back of my head. So I'm writing this issue to keep track of...

X Description: Several ideas for changes and/or additions have been gathered in the v14 project, mentioned in the user group or issues or dwelled in the back of my head. So I'm writing this issue to keep trac...

Opengraph URL: https://github.com/python-telegram-bot/python-telegram-bot/issues/2770

X: @github

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Discussion:] ConversationHandler","articleBody":"Several ideas for changes and/or additions have been gathered in the v14 project, mentioned in the user group or issues or dwelled in the back of my head. So I'm writing this issue to keep track of them better.\r\n\r\nThe following list of ideas should be discussed before release of v14 because at least some of them are easier to implement if we do them non-backwards compatible. I'd like to emphasize that most of these are very rough first thoughts and I'm fully aware that we may scrape many of them.\r\n\r\nRelated: https://github.com/python-telegram-bot/python-telegram-bot/discussions/2802\r\n\r\n---\r\n\r\n* Make `CH.fallbacks` optional. I've seen a lot of people (including me) setting at to an empty list for some use cases … Poolitzer already expressed support for this idea\r\n* ~ConverstanionHandler + run_async: Problem is that we can't persist futures/promises. But we should be able to guarantee that all futures are done on (clean) shutdown. One could add something like `BasePersistence.resolve_conversation_promises` that persistence classes can call before flushing on shutdown.~ This already get's handled on v20\r\n* #2390 (closed just for better overview, not actually implemented)\r\n* add a \"prefallbacks\" list, i.e. the state-handlers only trigger, if the \"prefallback\" handlers don't trigger. The current alternative is to add those handlers to the `fallbacks` list, which requires to make all state handlers ignore updates that should be handled by the `fallbacks`. see also #2764 #2960\r\n* Include `entry_points`, `fallbacks` (and eventual \"prefallbacks\") into the `states` dict. We already have special states for `TIMEOUT` and `WAITING`, so I think it would make the interface cleaner if we used special states `(PRE)FALLBACK` and `END` as keys for these lists rather than making them standalone kwargs of `__init__`\r\n* Think about \"conversation related data\", e.g. `context.conversation_data`. It should be an object unique per conversation key and `ConversationHandler` instance. It may even be automatically deleted when the conversation ends . See also #4136\r\n* Rethink which parts of `ConversationHandler` we consider public.\r\n  * e.g. the `conversations` is currently public, although undocumented and basically part of the internals. If we make it private, we can rework the setters of `persistence` and `conversations` to something like `get_persisted_data(persistence)` or `initialize_persistence(persistence)`\r\n  * We also rather regularly get questions like \"how do I access the current state of the conversation\" and \"how do I check if a user has an active conversation\". Making the logic of how the keys are build and how `conversations` works public *may* help with some of these and also with the above `context.conversation_data`\r\n  * One could take this one step further and let the user customize how the key is generated. This could be useful e.g. in situations where one wants to handle 3rd-party updates (e.g. login into an external service) within the conversation, which are not of type `telegram.Update`. see also #4768 for a request to make the CH state per message thread ID\r\n* think about `conversation_timeout`:\r\n  * Is it worth to allow timeout handlers to put the conversation in a non-end state?\r\n  * it it worth to try & allow a different timeout duration per state?\r\n  * Can we make them work for nested conversations?\r\n  * Can we ensure that the timeout jobs can be persisted?\r\n* #2827 to make CH be based more on a class-like structure\r\n* nested conversations:\r\n  * Check behavior of the `WATING` state, especially with nested conversations\r\n  * Check behavior of async handlers with nested conversations\r\n  * Once a child conversation has started one may want the next update to be processed exclusively by that child conversation, even if it's not the first handler in the state. Maybe this can be made possible. See also https://stackoverflow.com/questions/78143788\r\n* Think about a mechanism to lazy-load persisted conversation states to allow to reduce load on startup. would be especially useful for stateless server designs. See [here](https://t.me/pythontelegrambotgroup/558187) for some initial discussion. Note also that in stateless setups, a `refresh_conversation_data` would be useful, see #4452.\r\n* When the conversation has ended, pass `CH.END` to `persistence.update_conversation` instead of `None`\r\n* We currently issue a warning for `per_message=True, per_chat=False` - this is not necessarily valid in case `inline_message_ids` are used\r\n* `entry_points` should be checked *after* the states are checked - that way, state handlers may trigger before any `entry_points` trigger via `allow_reentry`. See https://t.me/pythontelegrambotgroup/606782?thread=606781 for a question on that. Edit: On second thought, the `allow_reentry` may not be needed at all - the user can just repeat the `entry_points` in the `fallbacks`. If \"prefallbacks\" (see above) are added, that even allows the user to customize which of state handlers and `entry_points` are checked first\r\n* A commonly requested feature is to track a \"conversation\" between two (or more) users who each chat with the bot in the respective private chat. If we could make something like this feasible, that would be awesome.\r\n* discuss possibility to make job timeouts persistent: #3522 \r\n* Improve type hinting where possible - see #3665 (closed only to track this here)\r\n* Errors in the timeout state should be handled like errors in handlers, not like errors in jobs - see https://t.me/pythontelegrambotgroup/675226\r\n* In case built-in states are used, they should either not be easy to reproduce or we should warn if the user tries to use them manually. See https://github.com/python-telegram-bot/python-telegram-bot/issues/3834\r\n* Rethink if we want to allow for some error handling on CH or even state level. See #2277 for some discussion ","author":{"url":"https://github.com/Bibo-Joshi","@type":"Person","name":"Bibo-Joshi"},"datePublished":"2021-11-07T10:33:08Z","url":"https://github.com/python-telegram-bot/python-telegram-bot/issues/2770"}

react-profiling0
react-import-mapreact,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322
route-pattern/_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format)
route-controllervoltron_issues_fragments
route-actionissue_layout
fetch-noncev2:2eec3287-82b5-2c96-3ab3-b9481d6b8d01
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-idAFD6:34CAB:4D92B33:62D82CE:6B0279D3
html-safe-nonce3f090e0bd7fea164139cfbd855605c13f0bd2625840b615e4414cb6c59eac8ea
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBRkQ2OjM0Q0FCOjREOTJCMzM6NjJEODJDRTo2QjAyNzlEMyIsInZpc2l0b3JfaWQiOiIzNzMwNDc4Njg1MjI1MTIyMjU5IiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0=
visitor-hmacbc45828f6f72f3778489d8772c5aa01dfd3fc1f0e95dd1f97b2d3e506f13242e
hovercard-subject-tagissue:1046711967
github-keyboard-shortcutsrepository,issues,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///voltron/issues_fragments/issue_layout
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/python-telegram-bot/python-telegram-bot/2770/issue_layout
twitter:imagehttps://opengraph.githubassets.com/0f9f9fb8e153d5067dc1229b9d6cec28976ad4e26084c8dd5ccdde4ae9e80cf1/python-telegram-bot/python-telegram-bot/issues/2770
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/0f9f9fb8e153d5067dc1229b9d6cec28976ad4e26084c8dd5ccdde4ae9e80cf1/python-telegram-bot/python-telegram-bot/issues/2770
og:image:altSeveral ideas for changes and/or additions have been gathered in the v14 project, mentioned in the user group or issues or dwelled in the back of my head. So I'm writing this issue to keep track of...
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernameBibo-Joshi
hostnamegithub.com
expected-hostnamegithub.com
None87e774ee7c6b3bee0490394e4d3e57ec9dbc956f74b87ea685dc8996c1676456
turbo-cache-controlno-preview
go-importgithub.com/python-telegram-bot/python-telegram-bot git https://github.com/python-telegram-bot/python-telegram-bot.git
octolytics-dimension-user_id16178365
octolytics-dimension-user_loginpython-telegram-bot
octolytics-dimension-repository_id38696925
octolytics-dimension-repository_nwopython-telegram-bot/python-telegram-bot
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id38696925
octolytics-dimension-repository_network_root_nwopython-telegram-bot/python-telegram-bot
turbo-body-classeslogged-out env-production page-responsive
disable-turbofalse
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
release423dbb54c5e7bfecc838eb387c1435eb3d0e760d
ui-targetfull
theme-color#1e2327
color-schemelight dark
react-app-nameissues

Links:

Skip to contenthttps://github.com/python-telegram-bot/python-telegram-bot/issues/2770#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fpython-telegram-bot%2Fpython-telegram-bot%2Fissues%2F2770
GitHubRepository hosting, code review, and collaborationhttps://github.com/platform
CopilotAI coding agent for tasks, projects, and automated workhttps://github.com/features/copilot
ActionsCI/CD and automationhttps://github.com/features/actions
Code QualityQuality analysis, fixes, and enforcementhttps://github.com/features/code-quality
CodespacesCloud development environmentshttps://github.com/features/codespaces
Code SecurityVulnerability detection and remediationhttps://github.com/security/advanced-security/code-security
Secret ProtectionSecret scanning and leak preventionhttps://github.com/security/advanced-security/secret-protection
All Featureshttps://github.com/features
Documentationhttps://docs.github.com/en
Traininghttps://learn.github.com/skills
Certificationshttps://learn.github.com/credentials
Build with Copilothttps://github.com/features/ai
Customize Copilothttps://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-copilot-overview
Integrationshttps://github.com/marketplace
Trending reposhttps://github.com/trending
GitHub Sponsorshttps://github.com/open-source/sponsors
Developer articleshttps://github.com/resources/articles
ChangelogYour source for the latest features, improvements, and fixes across GitHub products, all in one place.https://github.blog/changelog/
Enterpriseshttps://github.com/enterprise
Teamhttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
See all industrieshttps://github.com/solutions/industry
Why GitHubhttps://github.com/why-github
Customer Storieshttps://github.com/customer-stories
Business insightshttps://github.com/solutions/executive-insights
Trust Centerhttps://github.com/trust-center
GitHub Advanced SecurityEnterprise-grade code securityhttps://github.com/security/advanced-security
Copilot for businessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/enterprise/premium-support
Documentationhttps://docs.github.com/en
Resource centerhttps://github.com/resources
Bloghttps://github.blog/
Events & webinarshttps://github.com/resources/events
Community Forumhttps://github.com/orgs/community/discussions
Customer Storieshttps://github.com/customer-stories
Integrationshttps://github.com/marketplace
Customer supporthttps://help.github.com/
Traininghttps://learn.github.com/skills
GitHub Statushttps://www.githubstatus.com/
Abouthttps://github.com/about
Partnershttps://github.com/partners
Changeloghttps://github.blog/changelog/
GitHub UniverseThe event for developers, by developers — talks, workshops, and what’s next for GitHub.https://githubuniverse.com/
Pricinghttps://github.com/pricing
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fpython-telegram-bot%2Fpython-telegram-bot%2Fissues%2F2770
Sign uphttps://github.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fvoltron%2Fissues_fragments%2Fissue_layout&source=header-repo&source_repo=python-telegram-bot%2Fpython-telegram-bot
Reloadhttps://github.com/python-telegram-bot/python-telegram-bot/issues/2770
Reloadhttps://github.com/python-telegram-bot/python-telegram-bot/issues/2770
Reloadhttps://github.com/python-telegram-bot/python-telegram-bot/issues/2770
python-telegram-bothttps://github.com/python-telegram-bot
python-telegram-bothttps://github.com/python-telegram-bot/python-telegram-bot
Codehttps://github.com/python-telegram-bot/python-telegram-bot
Issues23 (23)https://github.com/python-telegram-bot/python-telegram-bot/issues
Pull requests19 (19)https://github.com/python-telegram-bot/python-telegram-bot/pulls
Discussionshttps://github.com/python-telegram-bot/python-telegram-bot/discussions
Actionshttps://github.com/python-telegram-bot/python-telegram-bot/actions
Projectshttps://github.com/python-telegram-bot/python-telegram-bot/projects
Wikihttps://github.com/python-telegram-bot/python-telegram-bot/wiki
Security and qualityhttps://github.com/python-telegram-bot/python-telegram-bot/security
Insightshttps://github.com/python-telegram-bot/python-telegram-bot/insights
https://github.com/python-telegram-bot/python-telegram-bot
New issuehttps://github.com/login?return_to=https://github.com/python-telegram-bot/python-telegram-bot/issues/2770
New issuehttps://github.com/login?return_to=https://github.com/python-telegram-bot/python-telegram-bot/issues/2770
💡 featurehttps://github.com/python-telegram-bot/python-telegram-bot/issues?q=type:"💡 feature"
[Discussion:] ConversationHandlerhttps://github.com/python-telegram-bot/python-telegram-bot/issues/2770#top
https://github.com/Bibo-Joshi
Bibo-Joshihttps://github.com/Bibo-Joshi
on Nov 7, 2021https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#issue-1046711967
#2802https://github.com/python-telegram-bot/python-telegram-bot/discussions/2802
[FEATURE] ConversationHandler: Allow special handlers/callbacks for entering states #2390https://github.com/python-telegram-bot/python-telegram-bot/issues/2390
Added impementation of "prefallbacks" list. #2764https://github.com/python-telegram-bot/python-telegram-bot/pull/2764
#2764; Implemented "prefallbacks" feature #2960https://github.com/python-telegram-bot/python-telegram-bot/pull/2960
[FEATURE] Have per-conversation data (or at least an identifier) in ConversationHandler #4136https://github.com/python-telegram-bot/python-telegram-bot/issues/4136
ConversationHandler do not support per_message_thread_id conversations #4768https://github.com/python-telegram-bot/python-telegram-bot/issues/4768
[FEATURE] class-based nested conversations #2827https://github.com/python-telegram-bot/python-telegram-bot/issues/2827
https://stackoverflow.com/questions/78143788https://stackoverflow.com/questions/78143788
herehttps://t.me/pythontelegrambotgroup/558187
[QUESTION] How to work with persistent conversation data across multiple processes #4452https://github.com/python-telegram-bot/python-telegram-bot/issues/4452
https://t.me/pythontelegrambotgroup/606782?thread=606781https://t.me/pythontelegrambotgroup/606782?thread=606781
[FEATURE] Persist timeouts of ConversationHandler #3522https://github.com/python-telegram-bot/python-telegram-bot/issues/3522
Sub-Optiomal type hints in ConversationHandler #3665https://github.com/python-telegram-bot/python-telegram-bot/issues/3665
https://t.me/pythontelegrambotgroup/675226https://t.me/pythontelegrambotgroup/675226
[FEATURE] warn if ConversationHandler.states has a key -1 #3834https://github.com/python-telegram-bot/python-telegram-bot/issues/3834
From error state to other state on a Conversational bot #2277https://github.com/python-telegram-bot/python-telegram-bot/issues/2277
Nexthttps://github.com/python-telegram-bot/python-telegram-bot/issues/2770?timeline_page=1
harshil21https://github.com/harshil21
v14https://github.com/python-telegram-bot/python-telegram-bot/milestone/22
on Jan 3, 2022https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#event-5835824072
harshil21https://github.com/harshil21
v20https://github.com/python-telegram-bot/python-telegram-bot/milestone/22
v20.0a1https://github.com/python-telegram-bot/python-telegram-bot/milestone/33
on May 12, 2022https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#event-6599369685
Bibo-Joshihttps://github.com/Bibo-Joshi
v20.0a1https://github.com/python-telegram-bot/python-telegram-bot/milestone/33
v20.0https://github.com/python-telegram-bot/python-telegram-bot/milestone/34
on May 21, 2022https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#event-6654888475
https://github.com/kirsanium
kirsaniumhttps://github.com/kirsanium
on Jun 20, 2022https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#issuecomment-1160727114
extremely hackyhttps://github.com/python-telegram-bot/python-telegram-bot/issues/1640#issuecomment-567706082
https://github.com/Poolitzer
Poolitzerhttps://github.com/Poolitzer
on Aug 1, 2022https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#issuecomment-1201662524
https://t.me/grammyjs_news/36https://t.me/grammyjs_news/36
https://github.com/Bibo-Joshi
Bibo-Joshihttps://github.com/Bibo-Joshi
on Aug 1, 2022https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#issuecomment-1201673354
#3042https://github.com/python-telegram-bot/python-telegram-bot/pull/3042
harshil21https://github.com/harshil21
v20.0https://github.com/python-telegram-bot/python-telegram-bot/milestone/34
v21.0https://github.com/python-telegram-bot/python-telegram-bot/milestone/41
on Nov 5, 2022https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#event-7745558261
https://github.com/Bibo-Joshi
Bibo-Joshihttps://github.com/Bibo-Joshi
on Jan 6, 2023https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#issuecomment-1374053785
https://t.me/grammyjs_news/36https://t.me/grammyjs_news/36
grammy docshttps://grammy.dev/plugins/conversations.html#how-wait-calls-work
wrap callshttps://grammy.dev/plugins/conversations.html#rule-i-all-side-effects-must-be-wrapped
store all updates and other variableshttps://grammy.dev/plugins/conversations.html#how-wait-calls-work
use complicated code setupshttps://grammy.dev/plugins/conversations.html#how-to-intercept-function-execution
re-run also some other thingshttps://grammy.dev/plugins/conversations.html#custom-context-objects
filter qurieshttps://grammy.dev/plugins/conversations.html#waiting-for-updates
filter querieshttps://grammy.dev/guide/filter-queries.html#example-queries
https://github.com/KnorpelSenf
KnorpelSenfhttps://github.com/KnorpelSenf
on Jan 6, 2023https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#issuecomment-1374082452
brainstorminghttps://github.com/grammyjs/grammY/issues/136
https://podrocket.logrocket.com/grammyhttps://podrocket.logrocket.com/grammy
https://github.com/Bibo-Joshi
Bibo-Joshihttps://github.com/Bibo-Joshi
on Jan 12, 2023https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#issuecomment-1380985166
@KnorpelSenfhttps://github.com/KnorpelSenf
on Telegramhttps://t.me/BiboJoshi
https://github.com/Bibo-Joshi
Bibo-Joshihttps://github.com/Bibo-Joshi
on Jan 22, 2023https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#issuecomment-1399538887
MWE in grammyjshttps://nekobin.com/fibenureqo.ts
problem sketch in pseudo-python-codehttps://nekobin.com/poheteqowe.py
herehttps://t.me/BotIdeasChat/19655
https://github.com/rejedai
rejedaihttps://github.com/rejedai
on Apr 3, 2023https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#issuecomment-1493713029
https://github.com/Poolitzer
Poolitzerhttps://github.com/Poolitzer
on Mar 9, 2024https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#issuecomment-1986959894
https://github.com/Bibo-Joshi
Bibo-Joshihttps://github.com/Bibo-Joshi
on Mar 9, 2024https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#issuecomment-1986968584
@Poolitzerhttps://github.com/Poolitzer
https://github.com/Bibo-Joshi
Bibo-Joshihttps://github.com/Bibo-Joshi
on May 27, 2024https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#issuecomment-2134022736
Palaptinhttps://github.com/Palaptin
on Jun 29, 2024https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#event-13339899396
Implemented the requirement to return CH.END instead of None to persi…https://github.com/Palaptin/python-telegram-bot/commit/9835ba3287523934bbeba19e20cb8723279527b9
9835ba3https://github.com/Palaptin/python-telegram-bot/commit/9835ba3287523934bbeba19e20cb8723279527b9
Bibo-Joshihttps://github.com/Bibo-Joshi
v22.0https://github.com/python-telegram-bot/python-telegram-bot/milestone/41
v23https://github.com/python-telegram-bot/python-telegram-bot/milestone/53
on Mar 15, 2025https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#event-16784751324
github-actionshttps://github.com/apps/github-actions
📋 stalework status: stalehttps://github.com/python-telegram-bot/python-telegram-bot/issues?q=state%3Aopen%20label%3A%22%F0%9F%93%8B%20stale%22
on Oct 7, 2025https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#event-20130841187
harshil21https://github.com/harshil21
📋 stalework status: stalehttps://github.com/python-telegram-bot/python-telegram-bot/issues?q=state%3Aopen%20label%3A%22%F0%9F%93%8B%20stale%22
on Oct 8, 2025https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#event-20153816108
github-actionshttps://github.com/apps/github-actions
📋 stalework status: stalehttps://github.com/python-telegram-bot/python-telegram-bot/issues?q=state%3Aopen%20label%3A%22%F0%9F%93%8B%20stale%22
on Oct 14, 2025https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#event-20259400629
https://github.com/apps/github-actions
github-actionshttps://github.com/apps/github-actions
on Oct 16, 2025https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#issuecomment-3408984612
GitHub Actionshttps://help.github.com/en/actions
https://t.me/pythontelegrambotgrouphttps://t.me/pythontelegrambotgroup
github-actionshttps://github.com/apps/github-actions
not plannedhttps://github.com/python-telegram-bot/python-telegram-bot/issues?q=is%3Aissue%20state%3Aclosed%20archived%3Afalse%20reason%3Anot-planned
on Oct 16, 2025https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#event-20308711194
harshil21https://github.com/harshil21
on Oct 16, 2025https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#event-20308940301
https://github.com/KnorpelSenf
KnorpelSenfhttps://github.com/KnorpelSenf
on Oct 16, 2025https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#issuecomment-3409208727
https://github.com/grammyjs/conversationshttps://github.com/grammyjs/conversations
Bibo-Joshihttps://github.com/Bibo-Joshi
📋 stalework status: stalehttps://github.com/python-telegram-bot/python-telegram-bot/issues?q=state%3Aopen%20label%3A%22%F0%9F%93%8B%20stale%22
on Oct 16, 2025https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#event-20310225098
harshil21https://github.com/harshil21
v23https://github.com/python-telegram-bot/python-telegram-bot/milestone/53
on May 30, 2026https://github.com/python-telegram-bot/python-telegram-bot/issues/2770#event-26139728470
Sign up for freehttps://github.com/signup?return_to=https://github.com/python-telegram-bot/python-telegram-bot/issues/2770
Sign in to commenthttps://github.com/login?return_to=https://github.com/python-telegram-bot/python-telegram-bot/issues/2770
💡 featurehttps://github.com/python-telegram-bot/python-telegram-bot/issues?q=type:"💡 feature"
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.