chore(core): fix a `TYPE_CHECKING`-related import
What the developer wrote
Authored by Roman Zeyde
chore(core): fix a `TYPE_CHECKING`-related import
[no changelog]
What changed, and why it matters
This is a trivial Python import-path correction inside a type-checking-only block. It changes `from common import ExceptionType` to `from .common import ExceptionType` so the type checker resolves the module correctly. It has no runtime effect and no security relevance.
No security action needed. Treat as a normal code-quality fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch fixes a relative import in core/src/trezor/ui/layouts/menu.py under an if TYPE_CHECKING: guard. TYPE_CHECKING is always false at runtime, so this import is only used by static type checkers. The change from absolute common to relative .common corrects module resolution but cannot affect executed code, firmware behavior, or attack surface.
Changed components
core/src/trezor/ui/layouts/menu.pyInspect captured patch +1 / −1
diff --git a/core/src/trezor/ui/layouts/menu.py b/core/src/trezor/ui/layouts/menu.py
index 1608718b..65cc4117 100644
--- a/core/src/trezor/ui/layouts/menu.py
+++ b/core/src/trezor/ui/layouts/menu.py
@@ -10,7 +10,7 @@ if TYPE_CHECKING:
from typing_extensions import Self
- from common import ExceptionType
+ from .common import ExceptionType
T = TypeVar("T")
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.