npm pyright 1.1.60
Published 1.1.60

latest releases: 1.1.360, 1.1.359, 1.1.358...
3 years ago

Bug Fix: Fixed a bug "aliased import with leading underscore produces private usage error".

Bug Fix: Fixed a bug that caused the wrong diagnostic message string to be used when "Generic" is used with no type arguments.

Enhancement: Added new diagnostic message for when "Generic" is used in contexts outside of a class definition statement.

Bug Fix (from Pylance): Use sys.version_info to query interpreter version.

Enhancement: Added heuristics to type var solver so it picks the "least complex" solution when considering the elements within a union.

Enhancement: Updated typeshed stubs to the latest versions.

Bug Fix: Fixed a bug that caused an error to be reported when a newline token was used within an f-string expression.

Enhancement: Added new diagnostic rule "reportInvalidStubStatement" (on by default in strict mode, off otherwise) that reports diagnostics for statements that should not appear within a type stub file.

Enhancement: Added diagnostic for a module-level __getattr__ function defined in a type stub file when in strict mode.

Bug Fix: Fixed bug that caused imports (and other symbols) to be reported as unaccessed if they were accessed from within code that was deemed to be unreachable (e.g. due to the current platform configuration).

Behavior Change: Changed logic for reportUnusedClass and reportUnusedFunction diagnostic rules so they don't report private-named functions and classes within stub files.

Bug Fix: The token "..." should mean an ellipsis object, not the ellipsis class, when used in a normal expression within a non-stub file.

Enhancement (from Pylance): Add python.analysis.autoImportCompletions to control auto-import completions.

Don't miss a new pyright release

NewReleases is sending notifications on new releases.