You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Plugin fails to load on ST 4215 (Python 3.14): cannot import name 'notification_handler' from 'lsp_utils' #2
LSP-pyvoice 0.1.4 does not load on Sublime Text build 4215 (Python 3.14): ImportError: cannot import name 'notification_handler' from 'lsp_utils'.
Steps
Fresh portable Sublime Text build 4215 (plugins run on Python 3.14 there, even with .python-version 3.8).
Install LSP and LSP-pyvoice from Package Control, run Package Control: Satisfy Libraries until it says all libraries are satisfied (installs lsp_utils 3.7.6 and sublime_lib 2.1.0).
Look at the console.
Result
reloading plugin LSP-pyvoice.plugin
Traceback (most recent call last):
File "...LSP-pyvoice.sublime-package\plugin.py", line 12, in <module>
from lsp_utils import notification_handler
ImportError: cannot import name 'notification_handler' from 'lsp_utils' (...\Lib\python314\lsp_utils\__init__.py)
The plugin never registers, so no Python file gets the language server.
Cause dependencies.json does not pin lsp_utils, so Package Control installs the current 3.7.6. Its __init__.py has no notification_handler, and lsp_utils.pip_client_handler (PipClientHandler, imported on the next line) is not in 3.7.6 either (it exports UvRunner/UvVenvManager instead). I checked the listed exports in the installed library; I did not check whether an older lsp_utils still exists for Python 3.8.
I have not tested on a 4200 install with the 3.8 host, so this report is only for build 4215 / Python 3.14.
Confirmed independently today (2026-11-07) on a clean portable ST 4215 / Python 3.14.6, and two things to add to the original report.
1. It fails twice, and the first failure masks the second
On a fresh rig with only the package installed, two of its plugins die immediately because LSP is imported but not in dependencies.json (which lists only lsp_utils, sublime_lib, multiprocessing):
reloading plugin LSP-pyvoice.listener
File "...LSP-pyvoice.sublime-package\listener.py", line 10, in <module>
ModuleNotFoundError: No module named 'LSP'
reloading plugin LSP-pyvoice.plugin
File "...LSP-pyvoice.sublime-package\plugin.py", line 10, in <module>
ModuleNotFoundError: No module named 'LSP'
Only after installing LSP by hand does the deeper error from the original report appear:
ImportError: cannot import name 'notification_handler' from 'lsp_utils'
2. notification_handler is gone from every lsp_utils available today
That name is not in the tree of lsp_utils v3.7.6 (lsp_utils/__init__.py is 1165 bytes, no notification_handler, and no module by that name) and Package Control currently satisfies the dependency with 4.0.1, so there is no version of the library that this import can succeed against any more. Pinning lsp_utils to whatever version last had it, or moving to the current lsp_utils API, is what unblocks this.
3. Cosmetic, same file set
All three entries in LSP-pyvoice.sublime-commands say LSP-pycoice ("coice"), so the command palette shows LSP-pycoice: Get Spoken, LSP-pycoice: Quick Install Grammars and Preferences: LSP-pycoice Settings.
Activity
dpc00 commentedon Nov 7, 2026
Confirmed independently today (2026-11-07) on a clean portable ST 4215 / Python 3.14.6, and two things to add to the original report.
1. It fails twice, and the first failure masks the second
On a fresh rig with only the package installed, two of its plugins die immediately because
LSPis imported but not independencies.json(which lists onlylsp_utils,sublime_lib,multiprocessing):Only after installing
LSPby hand does the deeper error from the original report appear:2.
notification_handleris gone from everylsp_utilsavailable todayThat name is not in the tree of
lsp_utilsv3.7.6 (lsp_utils/__init__.pyis 1165 bytes, nonotification_handler, and no module by that name) and Package Control currently satisfies the dependency with 4.0.1, so there is no version of the library that this import can succeed against any more. Pinninglsp_utilsto whatever version last had it, or moving to the currentlsp_utilsAPI, is what unblocks this.3. Cosmetic, same file set
All three entries in
LSP-pyvoice.sublime-commandssayLSP-pycoice("coice"), so the command palette showsLSP-pycoice: Get Spoken,LSP-pycoice: Quick Install GrammarsandPreferences: LSP-pycoice Settings.