1.2.8

• chore: update basedpyright 1.15.0

1.2.7

• chore: update basedpyright 1.14.0

1.2.6

• chore: update basedpyright 1.13.3
• fix: ignore REPL views (sublimelsp/LSP-pyright#343)

1.2.5

• chore: update basedpyright 1.13.2
• refactor: python executable search order: py -> python3 -> python

1.2.4

• chore: update basedpyright 1.13.1

1.2.2

• chore: update basedpyright 1.13.0

1.2.0

New Features

• Allow users to decide the order of strategies finding venv

  Previously, this is hard-coded. Now the user can specify the order of strategies in the settings.
  By default, a .venv or venv directory under the workspace project is prioritized.

  {
    "settings": {
      "venvStrategies": [
        "local_dot_venv",
        "env_var_conda_prefix",
        "env_var_virtual_env",
        "rye",
        "poetry",
        "pdm",
        "hatch",
        "pipenv",
        "pyenv",
        "any_subdirectory",
      ],
    }
  }

• Templated status bar text

  If a venv is detected, its information will be shown in that status bar.
  The user can customize the status bar text with Jinja2 template grammar.

  {
    "settings": {
      "statusText": "{% if venv %}venv: {{ venv.venv_prompt }}; py: {{ venv.python_version }}; by: {{ venv.finder_name }}{% endif %}",
    }
  }

Minors

• chore: update basedpyright 1.12.6
• fix: update_schema.py doesn't work due to upstream changes
• refactor: use boot.py and plugin/ structure

1.1.10

• chore: update basedpyright 1.12.5

1.1.9

• fix: local venv is not used under some circumstances

E.g.,

1. There is an ".python-version" file but no "pyenv" is installed.
2. "pyenv which python" will raises an exception.
3. python_path is an empty string and None is returned.

But actually we want to test all direct subdirs later and shouldn't return None here.

1.1.8

• fix: cannot get python path when there are both Pipfile and .env (sublimelsp/LSP-pyright#332)