Skip to content
AIBRAINWORX / OpenSourceCoder.comLOCAL-FIRST. BUILT IN THE OPEN.
Open Source / Developer Tools

ty 0.0.107 fixes a type-checking hang and separates script environments

Astral’s November 18 beta adds initial-indexing progress and cancellation as a preview feature. It also stops uv-managed scripts briefly inheriting the project environment.

Listen to this articleBrowser Voice
Ready
Astral’s official ty command-line comparison chart from the versioned repository; publisher benchmark illustration.
Astral’s official Home Assistant benchmark chart, linked by the ty 0.0.107 README but labeled ty 0.0.99 in the source graphic. Older publisher evaluation used as product background; a white display backdrop was added for legibility. Not our test or a measurement of this release’s fixes. · Genuine official publisher wordmark from the source recorded in the artwork credits; editorial identification, without endorsement.
Event / context: 2026-11-18 UTC. Source check: Nov 20, 2026.

Astral’s Python type checker and language server ty has reached 0.0.107, a November 18 beta update addressing a constructor-specialization hang and the isolation of uv-managed scripts. The release notes also list progress reporting and cancellation during initial indexing as preview functionality.

These are separate repairs. A change that makes a stalled process interruptible is useful, but it is not the same thing as removing the computation that caused a particular type-checking hang.

One hang came from repeatedly rebuilding unions

The generic-constructor fix describes type substitutions rebuilding equivalent unions in different orders and cycling through them. The repair processes variables individually and handles cycles and bounds rather than treating each ordering as a new result.

The contributor reports that Bokeh completed in 20 seconds after a 180-second timeout on the comparison revision. That is an upstream regression observation, not our benchmark or a predicted improvement for all projects. We did not run either revision.

Script isolation starts before synchronization finishes

The environment change addresses a temporary inheritance problem: a script opting into uv synchronization could initially use the project’s virtual environment. It now starts without one and receives uv’s environment after synchronization succeeds.

If synchronization fails, the script retains an empty environment instead of borrowing the project’s dependencies. That protects the intended analysis boundary, although it does not make dependency installation or arbitrary script execution into a security sandbox.

Our analysis: correct diagnostics require the intended environment

A type checker can be fast and still produce confusing results if it resolves imports against the wrong packages. Separating a script’s dependencies from its surrounding repository makes the question being checked clearer: does this script work with its own declared environment?

For large repositories, visible progress and a usable interruption path also make a difference. They help a developer distinguish active preparation from a stalled command without assuming the machine or editor is broken.

The indexing change moves initial indexing off the main thread. Its author notes that a particular full reindex during watch mode remains outside that cancellation behavior. The release labels the indexing feature as preview, and the versioned README still identifies ty as beta.

Our repository profile links the MIT-licensed project. We reviewed source and upstream examples; no checker, environment synchronization or performance test was run locally.

EXPLORE THE SOURCE

GitHub repositories

Primary-source review and original editorial analysis. No software installation, model inference, API call, security validation or independent benchmark performed.

Follow your curiosity.

Pass the signal.