HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
microsoft
pylance-release
Python2020–2026
microsoft / pylance-release

pylance-release

Documentation and issues for Pylance

31Distinct people
33Mentions
0Explicit recommenders
2.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Documentation and issues for Pylance

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 4:00:59 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year33 dated mentions

Observed mentions: 2020-07-03 16:13:33 UTC to 2026-10-26 23:22:14 UTC.

02468102020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 7 mentions; 3 submissions, 4 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC734
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC1019
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC606
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC303
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC303
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC312

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Pylance Fast, feature-rich language support for Python This repository is for providing feedback and documentation on the Pylance language server extension in Visual Studio Code. You can use the repository to report issues or submit feature requests. The Pylance codebase is not open-source but you can contribute to Pyright to make improvements to the core typing engine that powers the Pylance experience. Pylance is the default language support for Python in Visual Studio Code and is shipped as part of that extension as an optional dependency. The Pylance name is a small ode to Monty Python's Lancelot who was the first knight to answer the bridgekeeper's questions in the Holy Grail. Quick Start Install the Python extension from the marketplace. Pylance will be installed as an optional extension. Open a Python (.py) file and the Pylance extension will activate. Note: If you've previously set a language server and want to try Pylance, make sure you've set "python.languageServer": "Default" or "Pylance" in your settings.json file using the text editor, or using the Settings Editor UI. Features Pylance provides some awesome features for Python 3, including: Docstrings Signature help, with type information Parameter suggestions Code completion Auto-imports (as well as add and remove import code actions) As-you-type reporting of code errors and warnings (diagnostics) Code outline Code navigation Type checking mode Native multi-root workspace support Jupyter Notebooks compatibility Semantic highlighting Generate Dependency File command for workspace roots, Explorer folders, and Python scripts (Pylance: Generate Dependency File) Toggle Block Comment command for Python (Pylance: Toggle Block Comment) Install Matching Type Stubs command that finds and installs type stub packages for your installed dependencies (Pylance: Install Matching Type Stubs) Copilot Chat skills for fact-grounded Python help, type inference, inline type annotations, finding reviewed third-party stubs, stub authoring, Pylance docs, refactoring, profiling, improving Pylance type-evaluation performance, and adding or dropping Python version support See the changelog for the latest release. Settings and Customization Pylance provides users with the ability to customize their Python language support via a host of settings which can either be placed in the settings.json file in your workspace, or edited through the Settings Editor UI. python.analysis.languageServerMode Offers predefined configurations to help users optimize Pylance's performance based on their development needs. It controls how many IntelliSense features Pylance provides, allowing you to choose between full language service functionality or a lightweight experience optimized for performance. Default value: default Available values: light default (default) full Description: default: Provides a balanced experience with many useful features enabled by default. It ensures that the language server delivers sufficient functionality for most users without overloading the system. Advanced features can be enabled as needed, allowing for further customization at the cost of performance. light: Designed for users seeking a lightweight, memory-efficient setup. This mode disables various features to make Pylance function more like a streamlined text editor. Ideal for those who do not require the full breadth of IntelliSense capabilities and prefer Pylance to be as resource-friendly as possible. full: Designed for users seeking the most extensive feature set. This mode enables most of Pylance's features, offering the richest IntelliSense experience. Ideal for those who want access to the full range of available functionality. Individual settings can be configured to override the defaults set by languageServerMode. Default settings based on mode are: Mode light default full python.analysis.exclude ["**"] [] [] python.analysis.useLibraryCodeForTypes false true true python.analysis.enablePytestSupport false true true python.analysis.indexing false true true python.analysis.userFileIndexFollowSymlinkedFolders true true true python.analysis.autoImportCompletions false false true python.analysis.showOnlyDirectDependenciesInAutoImport false false true python.analysis.packageIndexDepths See settings below python.analysis.regenerateStdLibIndices false false true python.analysis.userFileIndexingLimit 2000 2000 -1 python.analysis.includeAliasesFromUserFiles false false true python.analysis.inlayHints.functionReturnTypes false false true python.analysis.inlayHints.pytestParameters false false true python.analysis.supportRestructuredText true true true python.analysis.supportDocstringTemplate false false false python.analysis.nodeExecutable "" "" "auto" python.analysis.typeCheckingMode Used to specify the level of type checking analysis performed. Default: off. Note that the value of this setting can be overridden by having a pyrightconfig.json or a pyproject.toml. For more information see this link. Available values: off: Most type-checking diagnostics are disabled; unresolved imports/variables diagnostics are produced. basic: All rules from off + basic type checking rules. standard: All rules from basic + standard type checking rules. strict: All rules from standard + strict type checking rules. You can refer to pyright documentation to reference the default type checking rules for each of the type checking modes. Performance Consideration: Setting python.analysis.typeCheckingMode to off can improve performance by reducing diagnostic checks, especially in large codebases. python.analysis.diagnosticMode Used to allow a user to specify which files receive full diagnostics. Available values: workspace openFilesOnly (default) Performance Consideration: Setting python.analysis.diagnosticMode to openFilesOnly limits full diagnostics to open files, reducing checking in large workspaces. Imported dependencies ca
Read the full README on GitHub

What Hacker News says

3 sources
> why this exists https://docs.basedpyright.com/v1.40.2/type-server/ > The "type server protocol" is a desperate attempt from microsoft to prevent pylance from becoming obsolete by outsourcing its type checking to other language servers like basedpyright, ty or pyrefly -- while continuing to keep certain language server features exclusive to pylance. > This protocol benefits nobody except microsoft. It adds needless complexity to any language server that chooses to support it. Basedpyright does not support it and strongly advises other language servers to avoid supporting it as well. > For more info see here https://github.com/microsoft/pylance-release/discussions/718... and here https://github.com/astral-sh/ty/issues/1190#issuecomment-337...
In Type Server Protocol

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.