platformio-vscode-ide
pylance-release
platformio-vscode-ide | pylance-release | |
---|---|---|
8 | 50 | |
1,153 | 1,655 | |
1.7% | 0.4% | |
7.3 | 9.0 | |
3 months ago | 9 days ago | |
JavaScript | Python | |
Apache License 2.0 | Creative Commons Attribution 4.0 |
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.
platformio-vscode-ide
-
VSCodium – Free/Libre Open Source Software Binaries of VS Code
There is a workaround for PlatformIO that I use to get it to work in VSCodium: https://github.com/platformio/platformio-vscode-ide/issues/1...
-
Extensions are not automatically found within VS Code when using Arch Linux
The PlatformIO extension currently requires Microsoft's proprietary C/C++ extension, so it can't (officially) be used in the Arch community build. Here's a feature request to remove the dependency on the C/C++ extension: https://github.com/platformio/platformio-vscode-ide/issues/1802
-
Extensions not showing up in the marketplace? Arch Linux
There is an open issue on their repo, it seems the ms-vscode.cpptools extension which it depends on isn't open source so it can't be published on Open VSX (the marketplace used by OSS builds of VSCode) until they manage to use the open source alternative as a replacement llvm-vs-code-extensions.vscode-clangd
- Firmware cannot compile. Was working earlier yesterday but now nothing works
-
Help with firmware troubles!!!
You might be experiencing a problem that has plagued a lot of people, which is explained in the GitHub issue report. If this is indeed the problem, there are workarounds for it. Good luck!
-
VS Code update 1.56 breaks PlatformIO compile and upload functionality
Thanks for the provided information. There is a reported issue https://github.com/platformio/platformio-vscode-ide/issues/2554 and we work on reproducing. Please follow issue #2554.
-
PIO Home server won't start | Where is the 'PlatformIO IDE Terminal'?
I'm trying to install platformio on vscode, but I keep getting this error: Could not start PIO Home server: Error: timeout . It leads you this github page where you are prompted to open the PlatformIO IDE Terminal, but no matter which terminal I open (powershell, cmd, bash) the command is not recognised. What should I do?
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
What are some alternatives?
BIGTREETECH-SKR-mini-E3 - BIGTREETECH SKR-mini-E3 motherboard is a ultra-quiet, low-power, high-quality 3D printing machine control board. It is launched by the 3D printing team of Shenzhen BIGTREE technology co., LTD. This board is specially tailored for Ender 3 printer, perfectly replacing the original Ender3 printer motherboard.
pyright - Static Type Checker for Python
openvsx - An open-source registry for VS Code extensions
jedi-language-server - A Python language server exclusively for Jedi. If Jedi supports it well, this language server should too.
picovoice - On-device voice assistant platform powered by deep learning
vscodium - binary releases of VS Code without MS branding/telemetry/licensing
icestudio - :snowflake: Visual editor for open FPGA boards
emacs-jedi - Python auto-completion for Emacs
pigpio - pigpio is a C library for the Raspberry which allows control of the General Purpose Input Outputs (GPIO).
neovim - Vim-fork focused on extensibility and usability
johnny-five - JavaScript Robotics and IoT programming framework, developed at Bocoup.
nvim-lspconfig - Quickstart configs for Nvim LSP