LSP-basedpyright
Python support for Sublime's LSP plugin provided through DetachHead/basedpyright.
Details
Installs
- Total 578
- Win 212
- Mac 156
- Linux 210
Nov 21 | Nov 20 | Nov 19 | Nov 18 | Nov 17 | Nov 16 | Nov 15 | Nov 14 | Nov 13 | Nov 12 | Nov 11 | Nov 10 | Nov 9 | Nov 8 | Nov 7 | Nov 6 | Nov 5 | Nov 4 | Nov 3 | Nov 2 | Nov 1 | Oct 31 | Oct 30 | Oct 29 | Oct 28 | Oct 27 | Oct 26 | Oct 25 | Oct 24 | Oct 23 | Oct 22 | Oct 21 | Oct 20 | Oct 19 | Oct 18 | Oct 17 | Oct 16 | Oct 15 | Oct 14 | Oct 13 | Oct 12 | Oct 11 | Oct 10 | Oct 9 | Oct 8 | Oct 7 | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Windows | 1 | 2 | 0 | 1 | 4 | 1 | 1 | 0 | 0 | 0 | 0 | 2 | 2 | 0 | 0 | 3 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 4 | 1 | 3 | 1 | 1 | 1 | 0 | 0 | 1 | 2 | 1 | 3 | 1 | 2 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 4 | 3 |
Mac | 0 | 0 | 0 | 0 | 1 | 1 | 2 | 0 | 0 | 0 | 2 | 2 | 3 | 0 | 1 | 2 | 0 | 3 | 2 | 0 | 0 | 2 | 1 | 2 | 0 | 0 | 1 | 1 | 2 | 0 | 1 | 0 | 0 | 2 | 0 | 2 | 1 | 2 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 0 |
Linux | 0 | 0 | 1 | 2 | 1 | 0 | 2 | 0 | 0 | 0 | 0 | 0 | 2 | 4 | 1 | 0 | 1 | 6 | 0 | 0 | 0 | 2 | 0 | 1 | 0 | 1 | 2 | 2 | 1 | 1 | 2 | 1 | 0 | 1 | 3 | 2 | 1 | 1 | 2 | 1 | 0 | 2 | 1 | 2 | 0 | 1 |
Readme
- Source
- raw.githubusercontent.com
LSP-basedpyright
Python support for Sublime's LSP plugin provided through DetachHead/basedpyright, which basically includes all Pyright features and some exclusive Pylance features such as semantic highlighting and inlay hints.
Installation
- Install LSP and LSP-basedpyright via Package Control.
- (Optional but recommended) Install the LSP-file-watcher-chokidar via Package Control to enable functionality to notify the server about new files.
- Restart Sublime.
- (Optional) Configure basedpyright for your
virtualenv
.
The Node.js is required by this server. If
node
is not in your$PATH
, this package will suggest to install a local Node.js runtime automatically. If you instead decide to usenode
that is already installed on your system, make sure that it's at least a version 14.
Configuration
TIP: It's recommended to additionally install the
LSP-json
package which provides validation and auto-complete forLSP-basedpyright
settings and thepyrightconfig.json
configuration file.
Here are some ways to configure the package and the language server.
- From
Preferences > Package Settings > LSP > Servers > LSP-basedpyright
- From the command palette
Preferences: LSP-basedpyright Settings
- Project-specific configuration
From the command palette run
Project: Edit Project
and add your settings in:
{
"settings": {
"LSP": {
"LSP-basedpyright": {
"settings": {
// Put your settings here
}
}
}
}
}
- Various options can only be configured through a
pyrightconfig.json
configuration file (check configuration for more info)
Provided Command Palette commands
Command | Description |
---|---|
LSP-basedpyright: Create Basedpyright Configuration File |
Creates a pyrightconfig.json file in the root of the project with basic options. Opens the configuration file if it already exists. |
Virtual environments
The plugin attempts to resolve the virtual environment automatically from well-known environment variables and workspace files.
This behavior can be disabled by explicitly setting the python interpreter in the python.pythonPath
setting.
If you want to overwrite the virtual environment, the pyrightconfig.json
file must be present at the root of your project.
This configuration file, at a minimum, should define where your Python virtualenvs are located, as well as the name of the one to use for your project:
{
"venvPath": "/path/to/virtualenvs/",
"venv": "myenv"
}
For example, if you have created a virtual environment inside the directory .venv
within the project directory then you would use:
{
"venvPath": ".",
"venv": ".venv"
}
Note that the venv
option is only supported in the pyrightconfig.json
file. The venvPath
option can also be specified in your .sublime-project, in case you don't want to hard-code a system-specific path in a shared project.