LSP-basedpyright
Python support for Sublime's LSP plugin provided through DetachHead/basedpyright.
Details
Installs
- Total 1K
- Win 406
- Mac 304
- Linux 431
Jun 7 | Jun 6 | Jun 5 | Jun 4 | Jun 3 | Jun 2 | Jun 1 | May 31 | May 30 | May 29 | May 28 | May 27 | May 26 | May 25 | May 24 | May 23 | May 22 | May 21 | May 20 | May 19 | May 18 | May 17 | May 16 | May 15 | May 14 | May 13 | May 12 | May 11 | May 10 | May 9 | May 8 | May 7 | May 6 | May 5 | May 4 | May 3 | May 2 | May 1 | Apr 30 | Apr 29 | Apr 28 | Apr 27 | Apr 26 | Apr 25 | Apr 24 | Apr 23 | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Windows | 2 | 3 | 0 | 1 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 5 | 2 | 3 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 2 | 2 | 0 | 0 | 3 | 0 | 1 | 1 | 2 | 2 | 4 | 2 | 1 | 1 | 0 | 0 | 0 |
Mac | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 3 | 2 | 2 | 1 | 4 | 1 | 0 | 2 | 1 | 0 | 1 | 0 | 0 | 1 | 3 | 3 | 3 | 0 | 2 | 1 | 1 | 1 | 4 | 2 | 1 | 2 | 2 | 0 | 0 | 3 | 0 | 1 | 0 | 1 | 0 | 0 |
Linux | 1 | 2 | 2 | 1 | 0 | 2 | 2 | 2 | 4 | 0 | 0 | 0 | 0 | 4 | 1 | 7 | 4 | 1 | 1 | 3 | 1 | 0 | 0 | 2 | 3 | 1 | 3 | 3 | 0 | 1 | 3 | 0 | 3 | 0 | 1 | 2 | 0 | 1 | 1 | 3 | 3 | 1 | 0 | 1 | 0 | 3 |
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.