pylance-release
vscode-cpptools
pylance-release | vscode-cpptools | |
---|---|---|
50 | 62 | |
1,655 | 5,351 | |
0.4% | 0.5% | |
9.0 | 9.3 | |
9 days ago | 7 days ago | |
Python | TypeScript | |
Creative Commons Attribution 4.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pylance-release
-
Open source versus Microsoft: The new rebellion begins
One of the things that comes to mind here is the fact that the default Python extension for VS Code is, perhaps surprisingly to many, not open source. https://github.com/microsoft/pylance-release
While it's possible to fork VS Code, it is not possible to fork VS Code and provide a seamless onramp towards a Python editing experience that is fully open source, because users are used to the nuances of the closed-source Pylance experience in VS Code proper. You could use the minified/compiled Pylance plugin in your fork, but you'd have no way to expand its capabilities to new hooks your fork provides. Microsoft's development process would always be able to move faster than a fork, because it could coordinate VS Code internal API development with its internal Pylance team, and could become incompatible with forks at any time.
It's worth re-reading the quote from J Allard in https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis... with this modern example in mind.
(Also worth mentioning https://github.com/detachhead/basedpyright?tab=readme-ov-fil... which is a heroic effort to derisk this, but it's an uphill battle for sure!)
- Help! Connection to server got closed error
-
Pylance is not working on my vscode
Anyone know how can we fix this issue if we build the vscode locally
-
VSCode adding exactly one space to all my new lines??
Do any of these issue tickets explain the behaviour you're seeing? https://github.com/microsoft/pylance-release/issues/4341, https://github.com/microsoft/pylance-release/issues/4071
- Pylance: String literal is unterminated
- What do you expect when renaming an import?
-
Writing Python like it's Rust
Maybe they "are the same thing" in terms of behavior (I don't know), but "A uses B" doesn't mean that "A is B".
One important difference in this case is that while "Pylance leverages Microsoft's open-source static type checking tool, Pyright" [1], Pylance itself is not open source. In fact, the license [2] restricts you to "use [...] the software only with [...] Microsoft products and services", which means that you are not allowed to use it with a non-Microsoft open source fork of VS Code, for example.
The license terms also say that by accepting the license, you agree that "The software may collect information about you and your use of the software, and send that to Microsoft" and that "You may opt-out of many of these scenarios, but not all".
[1] https://github.com/microsoft/pylance-release
[2] https://marketplace.visualstudio.com/items/ms-python.vscode-...
-
Any must-have extensions for working with Python in VSCode/VSCodium?
There's this one: https://github.com/microsoft/pylance-release/issues/4174 (rules don't apply properly, and ovverrides don't work even after being set, this is especially for the more generic ones like )
-
MSFT is forcing Outlook and Teams to open links in Edge and IT admins are angry
The example is not .NET in general, but that specific event when Microsoft reneged on open development tooling[1]. For some people, that was the moment they stopped trusting "new Microsoft" to keep their word (though for me, it was when the Python language server was replaced with a DRM-locked, LSP-noncompliant one[2] a bit before that; unlike .NET hot reload, they didn't backtrack there). I can think the company makes great open .NET tools and at the same time not trust them to close it down on a whim.
Does anyone know where the open xlang reimplementation of MIDL went[3], by the way? (Unlike 1990s MIDL, you can't reimplement this one from the language grammar in the docs, because there is no language grammar in the docs.)
[1] https://dusted.codes/can-we-trust-microsoft-with-open-source and links there
[2] https://github.com/microsoft/pylance-release/issues
[3] https://github.com/microsoft/xlang/pull/529
- Import ... could not be resolved
vscode-cpptools
-
🚀 Exciting New Feature Proposal for C++ Developers: "Add Similar Function" in IntelliSense! 🚀
🔗 Link to GitHub Issue: Add Similar Function - https://github.com/microsoft/vscode-cpptools/issues/11477
-
How to enable pretty printers?
According to this: https://github.com/microsoft/vscode-cpptools/issues/3423 it seems to be at least somewhat possible to reuse natvis files from Visual Studio, but I have not tested that. Never really had the need to look at any non-vector container in the debugger.
-
How to Debug C/C++ with Visual Studio Code (From a Microsoft Software Engineer)
Thank you for the feedback! Perf is always an ongoing issue for us but I can say that we’ve recently allocated one of our senior engineers to take on more perf related issues. Something that really helps us out is if you could file reproducible steps that lead to your performance issue. This allows us to address the issues more readily. Please file your issues here: https://github.com/microsoft/vscode-cpptools/issues
-
How to Setup VSCode for C/C++ Programming (From a Microsoft Software Engineer)
Yes, see this github issue for an example: Add Ada to supported languages for debugging · Issue #10475 · microsoft/vscode-cpptools (github.com)
-
Me after trying to use Git with Eclipse
Nope https://github.com/microsoft/vscode-cpptools/issues/16
- [Vscodium] L'extension C / C ++?
- εχει τρεξει κανεις cuda σε visual studio code ;
-
I can't properly use "Run C/C++ file"
and finally, it you're not happy using the extension I provided you, try fo contact the C/C++ Extension repo on GitHub, they'll help you out with your issue. Here's the link: https://github.com/microsoft/vscode-cpptools
-
[Vscode] VSCode me donnant une erreur lorsque j’utilise le débogueur : "launch: program enter name n’existe pas"
Vous devez définir le nom de votre exécutable dans launch.json. Ils expliquent ce qu'il faut faire et comment ici : https://github.com/Microsoft/vscode-cpptools/blob/master/launch.md
- Need help debugging c++
What are some alternatives?
pyright - Static Type Checker for Python
CodeLLDB - A native debugger extension for VSCode based on LLDB
jedi-language-server - A Python language server exclusively for Jedi. If Jedi supports it well, this language server should too.
vscode-clangd - Visual Studio Code extension for clangd
vscodium - binary releases of VS Code without MS branding/telemetry/licensing
emacs-jedi - Python auto-completion for Emacs
vscode-lldb - A native debugger extension for VSCode based on LLDB [Moved to: https://github.com/vadimcn/codelldb]
neovim - Vim-fork focused on extensibility and usability
nvim-dap - Debug Adapter Protocol client implementation for Neovim
nvim-lspconfig - Quickstart configs for Nvim LSP
Bear - Bear is a tool that generates a compilation database for clang tooling.