NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI · #1391 most downloaded on PyPI
static type checking for Python (but based)
Last release 7 days ago
10 Sep 2026
Ships fairly regularly
a new release about every 3 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
3 years old
119 releases · first in 2024
fix duplicated semantic token for decorators which caused them to not get highlighted as decorators in neovim by @DetachHead in https://github.com/Det
reportUnusedFunction on unused protected methods when the class is decorated with @final by @DetachHead in https://github.com/DetachHead/basedpyright/pull/937reportUnsafeMultipleInheritance false positive in diamond inheritance scenarios, which is safe due to how MRO works by @DetachHead in https://github.com/DetachHead/basedpyright/pull/940Callable types in inlay hints by @DetachHead in https://github.com/DetachHead/basedpyright/pull/943settings table by @baggiponte in https://github.com/DetachHead/basedpyright/pull/950Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.22.1...v1.23.0
One column per month.
fix incorrect inlay hints for generics where one of the types is a tuple by @DetachHead in https://github.com/DetachHead/basedpyright/pull/901
reportUnnecessaryIsInstance errors when narrowing Callable while strictGenericNarrowing is enabled by @DetachHead in https://github.com/DetachHead/basedpyright/pull/909 & https://github.com/DetachHead/basedpyright/pull/916Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.22.0...v1.22.1
when narrowing a type using an isinstance check, there's no way for the type checker to narrow its type variables, so pyright just narrows them to "Un
when narrowing a type using an isinstance check, there's no way for the type checker to narrow its type variables, so pyright just narrows them to "Unknown":
def foo(value: object):
if isinstance(value, list):
reveal_type(value) # list[Unknown]
this makes sense in cases where the generic is invariant and there's no other way to represent any of its possibilities. for example if it were to be narrowed to list[object], you wouldn't be able to assign list[int] to it. however in cases where the generic is covariant, contravariant, or uses constraints, it can be narrowed more accurately.
this release introduces the new strictGenericNarrowing setting to address this:
class Foo[T_co, T_contra]:
def foo(self, value: T_contra) -> T_co: ...
def foo(value: object):
if isinstance(value, Foo):
reveal_type(value) # previously `Foo[Any, Any]`, now `Foo[object, Never]`
for more information, see the docs.
huge thanks to @beauxq for the help on this. implemented in https://github.com/DetachHead/basedpyright/pull/745
reportExplicitAnysimilar to reportAny, however this rule bans usages of the Any type itself rather than expressions that are typed as Any:
def foo(baz: Any) -> Any: # error: reportExplicitAny
print(baz) # error: reportAny
implemented in https://github.com/DetachHead/basedpyright/pull/83
strictListInference in the docs by @rbrgmn in https://github.com/DetachHead/basedpyright/pull/888Never instead of NoReturn when it's inferred as the return type of a function by @peacewalker122 in https://github.com/DetachHead/basedpyright/pull/895Never and NoReturn by @DetachHead in https://github.com/DetachHead/basedpyright/pull/899Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.21.1...v1.22.0
Update License Info with Well-known OSA MIT License Classifier by @macserv in https://github.com/DetachHead/basedpyright/pull/857
package.json with "type": "module" by @DetachHead in https://github.com/DetachHead/basedpyright/pull/862Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.21.0...v1.21.1
…rules such as reportUnreachable and reportDeprecated supported special diagnostic categories like "unreachable" and "deprecated" respectively, which w…
"hint" diagnostic categorypreviously, in addition to the standard diagnostic categories "error" and "warning", some diagnostic rules such as reportUnreachable and reportDeprecated supported special diagnostic categories like "unreachable" and "deprecated" respectively, which would show as a hint in your editor instead of an error:
the issue with these hints is that they only make sense for diagnostic rules that relate to unnecessary or deprecated code. but there was no way to set a hint-level diagnostic for other diagnostic rules. the configuration for these hints was also needlessly confusing (eg. "unreachable" and "unused" look exactly the same). they also didn't make sense for editors that don't support diagnostic tags.
this release introduces the new "hint" diagnostic category to replace the "deprecated", "unused" and "unreachable" categories, which are now deprecated. for most rules, they will display as a hint:
but for rules where it makes sense to do so, the appropriate diagnostic tag (unnecessary or deprecated) will be applied automatically. this also allows all baselined diagnostics to be displayed as a hint, rather than just ones that can be considered unreachable/unnecessary.
for more information, see the docs
(implemented in https://github.com/DetachHead/basedpyright/pull/845)
super() calls by @DetachHead in https://github.com/DetachHead/basedpyright/pull/847Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.20.0...v1.21.0
these can be enabled using the new basedpyright.analysis.inlayHints.genericTypes setting:
these can be enabled using the new basedpyright.analysis.inlayHints.genericTypes setting:
Final and ClassVar annotations (https://github.com/DetachHead/basedpyright/pull/809)
note that it's disabled by default because the information it provides is often redundant when basedpyright.analysis.inlayHints.variableTypes is enabled:
reportUnannotatedClassAttributepyright does not warn when a member of a class that doesn't have a type annotation is overridden with an incompatible type:
class A:
value = 1
class B(A):
value = None # no error, even though the type on the base class is `int` and the type here is `None`
this decision seems to have been made for performance reasons, which is fair enough. but because it's unsafe, there should be a check that enforces type annotations on class attributes (unless the class is decorated with @final). the reportUnannotatedClassAttribute rule will do just that:
class A:
value = 1 # error: Type annotation for attribute `value` is required because this class is not decorated with `@final`
(implemented in https://github.com/DetachHead/basedpyright/pull/812)
TypedDict updateTypedDicts:foo: dict[{"foo": int}] = {"foo": 1}
+ foo: TypedDict[{"foo": int}] = {"foo": 1}
dict[{"foo": int}] syntax. from now on any deviations we make from the standard will be configured using a separate option instead of using pyright's enableExperimentalFeatures setting, which is now disabled by default like it is in pyright (https://github.com/DetachHead/basedpyright/pull/831)pyproject.toml contains an emoji by @DetachHead in https://github.com/DetachHead/basedpyright/pull/822Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.19.1...v1.20.0
fix typeCheckingMode still defaulting to "all" in the language server when there's no config file by @DetachHead in https://github.com/DetachHead/base
typeCheckingMode still defaulting to "all" in the language server when there's no config file by @DetachHead in https://github.com/DetachHead/basedpyright/pull/791Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.19.0...v1.19.1
it may be an unpopular opinion, but i believe that type checkers/linters should be as strict as possible by default - to ensure that the user is made
typeCheckingModeit may be an unpopular opinion, but i believe that type checkers/linters should be as strict as possible by default - to ensure that the user is made aware of all potential issues in their code, and that they are the ones responsible for making the conscious decision to reduce the strictness if they wish. i expand on my perspective in this comment.
the reality though is that it's really annoying for the user to see the same red line on both an unknown import and an unused import.
basedpyright 1.19.0 introduces a new default typeCheckingMode called "recommended", which sets most of the stricter rules to be reported as a warning instead of an error. we've also added a new setting called failOnWarnings for the CLI which is enabled by default in this mode.
i believe this addresses the concerns some users have had regarding the default settings, while still ensuring that the user is made aware of all the checks basedpyright has to offer.
you can read more about the diagnostic rulesets in the docs.
(implemented in https://github.com/DetachHead/basedpyright/pull/759)
reportImplicitAbstractClass diagnostic rule by @DetachHead & @kotlinisland in https://github.com/DetachHead/basedpyright/pull/774Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.18.4...v1.19.0
add settings to disable each type of inlay hint by @DetachHead in https://github.com/DetachHead/basedpyright/pull/738, https://github.com/DetachHead/b
Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.18.3...v1.18.4
update upstream pyright version to 1.1.383 by @DetachHead in https://github.com/DetachHead/basedpyright/pull/730
Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.18.2...v1.18.3
fix hyperlinks to the docs from diagnostics in the language server by @DetachHead in https://github.com/DetachHead/basedpyright/pull/717
Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.18.1...v1.18.2
fix baseline when running in multithreaded/background analysis mode by @DetachHead in https://github.com/DetachHead/basedpyright/pull/702
Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.18.0...v1.18.1
have you ever wanted to adopt a new tool or enable new checks in an existing project, only to be immediately bombarded with thousands of errors you'd
have you ever wanted to adopt a new tool or enable new checks in an existing project, only to be immediately bombarded with thousands of errors you'd have to fix? baseline solves this problem by allowing you to only report errors on new or modified code. it works by generating a baseline file keeping track of the existing errors in your project so that only errors in newly written or modified code get reported.
to enable baseline, run basedpyright --writebaseline in your terminal or run the "basedpyright: Write new errors to baseline" task in vscode. this will generate a ./basedpyright/baseline.json for your project. you should commit this file so others working on your project can benefit from it too.
this file gets automatically updated as errors are removed over time in both the CLI and the language server. if you ever need to baseline new errors or an error that resurfaced because you've modified the same line of code it was on, just run that command again.
heavily inspired by basedmypy
more info is available in the documentation
(implemented in https://github.com/DetachHead/basedpyright/pull/608)
Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.17.5...v1.18.0
update upstream pyright version to 1.1.381 by @DetachHead in https://github.com/DetachHead/basedpyright/pull/676
Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.17.4...v1.17.5
improve fuzzy matching for auto-complete suggestions by @beauxq in https://github.com/DetachHead/basedpyright/pull/656
Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.17.3...v1.17.4
Add Helix configuration to installation.md by @Maarrk in https://github.com/DetachHead/basedpyright/pull/645
Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.17.2...v1.17.3
Add emacs lsp-pyright installation instructions to docs by @zipy124 in https://github.com/DetachHead/basedpyright/pull/627
Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.17.1...v1.17.2
make the python vscode extension a dependency of the basedpyright vscode extension as it's required to detect the python interpreter by @DetachHead in
Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.17.0...v1.17.1
fix unreachable, unused & deprecated diagnostic severity levels not working when set in the language server config by @DetachHead in https://github.co…
reportInvalidCast false positive when casting to/from None and type by @DetachHead in https://github.com/DetachHead/basedpyright/pull/579reportUnusedParameter rule by @DetachHead in https://github.com/DetachHead/basedpyright/pull/589reportUnnecessaryComparison when using assert_never in an intentionally unreachable case in a match statement by @DetachHead in https://github.com/DetachHead/basedpyright/pull/593Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.16.0...v1.17.0
send an error notification over LSP when an invalid diagnosticMode value is set by @DetachHead in https://github.com/DetachHead/basedpyright/pull/560
diagnosticMode value is set by @DetachHead in https://github.com/DetachHead/basedpyright/pull/560 & https://github.com/DetachHead/basedpyright/pull/565Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.15.2...v1.16.0
basedpyright playground now runs entirely in the browser by @DetachHead in https://github.com/DetachHead/basedpyright/pull/514 & https://github.com/De
Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.15.1...v1.15.2
update upstream pyright version to 1.1.374 by @DetachHead in https://github.com/DetachHead/basedpyright/pull/533
enableReachabilityAnalysis option in favor of reportUnreachable which is more flexible. setting enableReachabilityAnalysis to false is treated as an alias for reportUnreachable = 'none'. more info hereFull Changelog: https://github.com/DetachHead/basedpyright/compare/v1.15.0...v1.15.1
fix intermittent errors in if not TYPE_CHECKING blocks by @DetachHead in https://github.com/DetachHead/basedpyright/pull/503
if not TYPE_CHECKING blocks by @DetachHead in https://github.com/DetachHead/basedpyright/pull/503enableTypeIgnoreComments by default by @DetachHead in https://github.com/DetachHead/basedpyright/pull/504
# pyright: ignore comments instead. see the docs for more infoAny type istelf by @DetachHead in https://github.com/DetachHead/basedpyright/pull/506Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.14.0...v1.15.0
improve emacs installation instructions by @DetachHead in https://github.com/DetachHead/basedpyright/pull/493
implemented in #460 & #499
Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.13.3...v1.14.0
add lsp-bridge for emacs by @manateelazycat in https://github.com/DetachHead/basedpyright/pull/479
Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.13.2...v1.13.3
fix crash in some cases when building & installing wheel from github by @DetachHead in https://github.com/DetachHead/basedpyright/pull/465
Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.13.1...v1.13.2
Update configuration.md with scoped rule example by @jmann345 in https://github.com/DetachHead/basedpyright/pull/434
reportUnsafeMultipleInheritance to correctly account for MRO by @DetachHead in https://github.com/DetachHead/basedpyright/pull/444reportUnreachable on assert_never calls by @DetachHead in https://github.com/DetachHead/basedpyright/pull/450Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.13.0...v1.13.1
unlike pylance, this shows docstrings for all supported python versions & platforms, regardless of your current environment. in this example, the tzse
unlike pylance, this shows docstrings for all supported python versions & platforms, regardless of your current environment. in this example, the tzset function does not exist on windows, but we can still see its docstring:
you can read more about it in the docs. huge thanks to @AThePeanut4 for creating docify, which made this feature possible!
implemented in https://github.com/DetachHead/basedpyright/pull/420 and https://github.com/DetachHead/basedpyright/pull/423
typeCheckingMode not defaulting to "all" (was broken by a recent upstream change) by @DetachHead in https://github.com/DetachHead/basedpyright/pull/422reportUninitializedInstanceVariable on NamedTuples by @DetachHead in https://github.com/DetachHead/basedpyright/pull/425Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.12.6...v1.13.0
fix values with a type annotation that were narrowed to Never being coloured as a type by @DetachHead in https://github.com/DetachHead/basedpyright/pu
Never being coloured as a type by @DetachHead in https://github.com/DetachHead/basedpyright/pull/401Never type aliases being coloured as a variable when using the new python 3.12 type alias syntax by @DetachHead in https://github.com/DetachHead/basedpyright/pull/403executionEnvironments by @DetachHead in https://github.com/DetachHead/basedpyright/pull/408Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.12.5...v1.12.6
fix values that were narrowed to Never being coloured as a type by @DetachHead in https://github.com/DetachHead/basedpyright/pull/390
Never being coloured as a type by @DetachHead in https://github.com/DetachHead/basedpyright/pull/390TypedDicts (it was removed in 1.1.366)Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.12.4...v1.12.5
update upstream pyright version to 1.1.365 by @DetachHead in https://github.com/DetachHead/basedpyright/pull/381
extends config option by @DetachHead in https://github.com/DetachHead/basedpyright/pull/381Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.12.3...v1.12.4
update upstream pyright version to 1.1.364 by @DetachHead in https://github.com/DetachHead/basedpyright/pull/375
Any being coloured as a variable instead of a type by @DetachHead in https://github.com/DetachHead/basedpyright/pull/373Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.12.2...v1.12.3
fix reportUnsafeMultipleInheritance false positives when the class has a base class that does not define an __init__ or __init_subclass__ by @DetachHe
reportUnsafeMultipleInheritance false positives when the class has a base class that does not define an __init__ or __init_subclass__ by @DetachHead in https://github.com/DetachHead/basedpyright/pull/351reportAbstractUsage conflicting with reportMisssingSuperCall by @DetachHead in https://github.com/DetachHead/basedpyright/pull/352Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.12.1...v1.12.2
fix reportUnsafeMultipleInheritance false positives on TypedDicts and dataclasses by @DetachHead in https://github.com/DetachHead/basedpyright/pull/34
reportUnsafeMultipleInheritance false positives on TypedDicts and dataclasses by @DetachHead in https://github.com/DetachHead/basedpyright/pull/344Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.12.0...v1.12.1
switch from nodejs-bin to nodejs-wheel by @lewis6991 in https://github.com/DetachHead/basedpyright/pull/323
reportMissingSuperCall less annoying, as it no longer needs to report missing super() calls on classes with no base class when reportUnsafeMultipleInheritance is enabledFull Changelog: https://github.com/DetachHead/basedpyright/compare/v1.11.0...v1.12.0
support disabling deprecation, unused and unreachable hints in diagnostic severity overrides by @DetachHead in https://github.com/DetachHead/basedpyri…
python -m basedpyright) by @vemel in https://github.com/DetachHead/basedpyright/pull/324pyright: ignore is safer and preferred over type: ignore comments by @KotlinIsland in https://github.com/DetachHead/basedpyright/pull/331TypeAlias inlay hint if their type came from a type alias by @DetachHead in https://github.com/DetachHead/basedpyright/pull/328Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.10.4...v1.11.0
activate vscode extension if workspace contains a pyproject.toml by @DetachHead in https://github.com/DetachHead/basedpyright/pull/316
pyproject.toml by @DetachHead in https://github.com/DetachHead/basedpyright/pull/316Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.10.3...v1.10.4
fix reportImplicitRelativeImport not being configurable by @DetachHead in https://github.com/DetachHead/basedpyright/pull/306
reportImplicitRelativeImport not being configurable by @DetachHead in https://github.com/DetachHead/basedpyright/pull/306Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.10.2...v1.10.3
fix reportPrivateLocalImportUsage not being configurable by @DetachHead in https://github.com/DetachHead/basedpyright/pull/301
reportPrivateLocalImportUsage not being configurable by @DetachHead in https://github.com/DetachHead/basedpyright/pull/301Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.10.1...v1.10.2
bump upstream pyright version to 1.1.358 by @DetachHead in https://github.com/DetachHead/basedpyright/pull/281
python.languageServer setting in vscode and improve automatic fixes for when pylance is installed by @DetachHead in https://github.com/DetachHead/basedpyright/pull/285Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.10.0...v1.10.1
add new reportInvalidCast rule for casts to non-overlapping types by @DetachHead in https://github.com/DetachHead/basedpyright/pull/245
reportInvalidCast rule for casts to non-overlapping types by @DetachHead in https://github.com/DetachHead/basedpyright/pull/245AbstractContextManager and AbstractAsyncContextManager at runtime on python 3.8 by @DetachHead in https://github.com/DetachHead/basedpyright/pull/263Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.9.1...v1.10.0
fix --version showing the basedpyright version as the upstream version number by @DetachHead in https://github.com/DetachHead/basedpyright/pull/256
--version showing the basedpyright version as the upstream version number by @DetachHead in https://github.com/DetachHead/basedpyright/pull/256Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.9.0...v1.9.1
add support for Sublime Text by @jfcherng in https://github.com/DetachHead/basedpyright/pull/224
parameter semantic token type by @ValdezFOmar in https://github.com/DetachHead/basedpyright/pull/229Unknown and Any variables being coloured as Unbound by @ValdezFOmar in https://github.com/DetachHead/basedpyright/pull/235--gitlabcodequality argument to generate gitlab code quality report by @DetachHead in https://github.com/DetachHead/basedpyright/pull/247Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.8.0...v1.9.0
from now on, any breaking changes to upstream pyright will be configurable. sorry about that!
defaultLibrary semantic token modifier by @ValdezFOmar (#193)decorator semantic token type by @ValdezFOmar (#217)--version output (#218)
reportImplicitRelativeImport diagnostic rule instead of banning them entirely in the import resolver (#220)
Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.7.0...v1.8.0
add new reportPrivateLocalImportUsage rule to detect imports from local modules that are not intended to be re-exported
reportPrivateLocalImportUsage rule to detect imports from local modules that are not intended to be re-exported (#187)reportIgnoreCommentWithoutRule rule to enforce error codes in type:ignore/pyright:ignore comments (#186)
reportGeneralTypeIssuesFull Changelog: https://github.com/DetachHead/basedpyright/compare/v1.6.1...v1.7.0
introducing the basedpyright playground: http://basedpyright.com
Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.6.0...v1.6.1
new logo by @DetachHead in https://github.com/DetachHead/basedpyright/pull/146
Callable types were incorrectly coloured as functions (#142)_ were coloured as readonly (#139)type keyword in pyhthon 3.12 was being coloured as a type (this was an upstream issue in vscode and pylance) (#144)TypeVars that have bounds or variance arguments (#141)Callables (#136)_ (#138)Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.5.0...v1.6.0
i've also made some improvements that are not present in pylance:
| before | after |
|---|---|
i've also made some improvements that are not present in pylance:
Final are coloured as read-onlyFull Changelog: https://github.com/DetachHead/basedpyright/compare/v1.4.0...v1.5.0
prevent vscode extension from locking the language server executable by @DetachHead in https://github.com/DetachHead/basedpyright/pull/100 & https://g
Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.3.1...v1.4.0
fix reportDuplicateImport not reporting duplicated aliases and duplicated imports across different import statements by @DetachHead in https://github.
reportDuplicateImport not reporting duplicated aliases and duplicated imports across different import statements by @DetachHead in https://github.com/DetachHead/basedpyright/pull/91reportDeclaration not reporting multiple redeclarations of the same type by @DetachHead in https://github.com/DetachHead/basedpyright/pull/93Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.3.0...v1.3.1
add import suggestion code actions by @DetachHead in https://github.com/DetachHead/basedpyright/pull/79
. by @DetachHead in https://github.com/DetachHead/basedpyright/pull/85Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.2.0...v1.3.0
remove typing.Callable deprecation since Callable is not a collection by @DetachHead in https://github.com/DetachHead/basedpyright/pull/80
typeCheckingMode to all by default by @DetachHead in https://github.com/DetachHead/basedpyright/pull/75typing.Callable deprecation since Callable is not a collection by @DetachHead in https://github.com/DetachHead/basedpyright/pull/80reportAny rule by @DetachHead in https://github.com/DetachHead/basedpyright/pull/73Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.1.0...v1.2.0
make all config validation errors exit with a non-zero exit code and add error for unknown config options by @DetachHead in https://github.com/DetachH
Full Changelog: https://github.com/DetachHead/basedpyright/compare/v1.0.0...v1.1.0
Basedpyright is a static type checker for Python that is built on top of the work done by the pyright project.
Basedpyright is a static type checker for Python that is built on top of the work done by the pyright project.
new features include:
reportUnreachable optionand more coming soon! :)))
see the documentation for more information about these features and the motivation behind this project.
all typeCheckingMode option and disable warnings when typeCheckingMode is off by @DetachHead in https://github.com/DetachHead/basedpyright/pull/49Full Changelog: https://github.com/DetachHead/basedpyright/compare/v0.2.7...v1.0.0
fix reportUnreachable setting not being read by @DetachHead in https://github.com/DetachHead/basedpyright/pull/42
reportUnreachable setting not being read by @DetachHead in https://github.com/DetachHead/basedpyright/pull/42Full Changelog: https://github.com/DetachHead/basedpyright/compare/v0.2.6...v0.2.7
update docs by @DetachHead in https://github.com/DetachHead/basedpyright/pull/32
reportUnreachable option by @DetachHead in https://github.com/DetachHead/basedpyright/pull/34Full Changelog: https://github.com/DetachHead/basedpyright/compare/v0.2.5...v0.2.6
nothing to see here, just a ci fix
nothing to see here, just a ci fix
Fix issue where exit code was always 0 by @DetachHead in https://github.com/DetachHead/basedpyright/pull/28
Full Changelog: https://github.com/DetachHead/basedpyright/compare/v0.2.2...v0.2.4
pypi package: https://pypi.org/project/basedpyright/
pypi package: https://pypi.org/project/basedpyright/
Your coding agent can read these notes before it upgrades. Set up the MCP server →