@BasiliskPython

Completely new Python dev experience. Type checking, debugging, profiling, refactoring and more in Vscode, IntelliJ, Zed, Neovim and more

 Python
basilisk-python.dev/
Joined June 2026
  • Tweets51
  • Following42
  • Followers49
10Media
We submitted a pull request to remove Basilisk from the Python typing repo. Many of the conformance tests were depending on pattern matching text in the PEP tests. We're working on fixing this and we will update the website ASAP. Read about it here github.com/python/typing/pul…

Remove Basilisk from conformance results by MelbourneDeveloper · Pull Request #2330 · python/typing

Reverts #2316. I'm the author of Basilisk, and I'm asking for it to be taken out of the conformance results. Our published score doesn't measure what the table says it measu...

github.com
1
3
98
⚡ Cold `basilisk check` got cheaper: a precomputed `builtins.pyi` index, lazy off-thread typeshed activation, zero-copy stub decode — and no Python spawn for auto-discovered interpreters, whose `sys.platform` and `site-packages` are already knowable. (#375)
2
36
🔍 Basilisk now recognises methods defined inside if, try, with and match blocks in a class body — so classes that build their methods conditionally, like under if TYPE_CHECKING:, check cleanly. (#366)
1
2
45
🙈 Inlay hints, twice fixed: the internal `Unknown` sentinel no longer leaks out as `list[Unknown]`. Display keeps the last good parse; diagnostics deliberately don't. (#392)
1
2
45
⌨️ Dot-completion now resolves loop variables, inferred literals, subscripted generics and expressions. A string-literal receiver even selects the PEP 675 `LiteralString` overloads now. (#392)
1
2
36
🚀 Basilisk 0.39.0 is here. Dot-completion wakes up on receivers that offered nothing, inlay hints stop leaking `Unknown` and stop vanishing mid-keystroke, and `basilisk check` cold-starts faster. Release notes thread 👇 🧵
1
1
3
996
📥 New rule: `imports_missing_name` flags `from M import X` when workspace module M defines no X. Deliberately conservative: a module-level `__getattr__`, a star-import, or an unreadable target all keep it quiet. (#362) 🧵
1
28
🐛 `str.join` arguments are now judged by their resolved TYPE instead of the syntactic shape of the expression. That one change closed 4 false positives and caught 1 error we were missing. (#357) 🧵
1
1
31
💾 Caching is now a property of your project, not of the command line you happened to type: `[tool.basilisk] cache` and `cache-dir`, surfaced in the VS Code configuration editor. `--no-cache` beats `--cache` when both appear. (#364) 🧵
1
1
28
🔗 Share any snippet by URL: the source is compressed into the hash fragment, so no server ever stores your code. Every diagnostic deep-links to its own /errors/BSK-XXXX/ page, so the playground teaches like every other surface. (#364) 🧵
1
1
34
🔌 And it's honest about what it is. Every import search root is empty, so it can never read your disk. The stdlib comes from the embedded typeshed snapshot, so `import typing` resolves in the browser exactly like it does locally. (#364) 🧵
1
1
33
🎮 The real checker, compiled to WebAssembly, running in your browser. Same parse → resolve → check pipeline `basilisk check` runs, not a reimplementation, so every rule fix reaches it for free. Zero server. Try it: basilisk-python.dev/playgrou… (#364) 🧵
1
2
64
🚀 Basilisk 0.38.0 is here, and the headline is a big one: the checker now runs in your browser. Release notes thread 👇 🧵
1
1
1
2
1,208
✅ Through all of it: 100% conformance with the Python typing spec, 0 false positives — straight from the unmodified python/typing harness. That's the whole game. 🐍
1
30
🏗️ The release pipeline is hardened end-to-end — CRLF-proof typeshed index, native linux-arm64 wheels, and fixed Windows VSIX builds. (#344, #345, #346) 🧵
1
1
41
🔧 CLI/LSP parity: `basilisk check` now checks stdlib module attributes exactly like the editor, and user-stub star re-exports resolve cleanly through the active typeshed. (#331, #350) 🧵
1
1
40
🛡️ `basilisk fix` will never rewrite your virtualenv again (detected via pyvenv.cfg), and a bare `fix` now touches only your configured include roots — never the whole working dir. (#347) 🧵
1
1
26
🐛 Big false-positive fixes: walrus operator (x := ...) bindings, quoted cast("Widget", x) forward refs, and tuple return-type inference all now behave correctly. (#347, #348) 🧵
1
1
32
🏷️ Fresh workspaces are pinned & reproducible out of the box, and typeshed status warnings are now real, config-gradable diagnostics you can grade or silence like any rule. (#347, #351) 🧵
1
1
35
🔒 Every typeshed pin is cryptographically verified — one mutated byte fails the pin. And if it's missing or corrupt, you get a loud, actionable error, not silently-disabled checking. (#338, #342) 🧵
1
1
44

No more items