BSK-E0003 error

Missing variable type annotation

Fires when a module-level variable has no type annotation. In strict mode every module-level binding must carry an explicit annotation so that Basilisk can verify downstream usage and generate accurate stubs.

Real basilisk check output

What you see when BSK-E0003 fires on a minimal example:

basilisk check output reporting BSK-E0003 — Missing variable type annotation

How to handle it

Every rule is on by default — strict is the default, not a cage. You can dial BSK-E0003 down per-file or per-path from your editor or pyproject.toml, or fix the code so it type-checks. See the Missing Annotations rules and the complete diagnostic reference.

Canonical URL: https://www.basilisk-python.dev/errors/BSK-E0003