reply_text and making mypy happy #5073

BlankAdventure

BlankAdventure
Dec 29, 2025

Consider a pretty standard command callback function:

async def command(update: Update, context: ContextTypes.DEFAULT_TYPE) -> None:
	await update.message.reply_text("hello world")

mypy will complain about this as message can vary depending on different calling contexts:

error: Item "None" of "Message | None" has no attribute "reply_text" [union-attr]

To keep mypy happy I've taken to using this pattern in all my callbacks:

async def command(update: Update, context: ContextTypes.DEFAULT_TYPE)) -> None:
	if update.message:
		await update.message.reply_text("hello world")

But its kind of annoying repeating this everywhere, and moreoever, none of the code examples seem bother with this. I know mypy isn't the be-all-end-all, but I'm curious about this discrepancy.

1 You must be logged in to vote

All reactions

Bibo-Joshi

Bibo-Joshi
Dec 30, 2025
Maintainer

Hi. please have a look at #3332

1 You must be logged in to vote

All reactions

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

reply_text and making mypy happy #5073

Uh oh!

{{title}}

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

reply_text and making mypy happy #5073

Uh oh!

{{title}}

Uh oh!

BlankAdventure Dec 29, 2025

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Bibo-Joshi Dec 30, 2025 Maintainer

Select a reply

Uh oh!

Footer

Footer navigation

BlankAdventure
Dec 29, 2025

Bibo-Joshi
Dec 30, 2025
Maintainer