Minimum requried jedi version does not support Python 3.13

[hbibel]

jedi before 0.19.2 was incompatible with Python 3.13. This was fixed here.

To support Python 3.13, pylsp should require at least jedi 0.19.2.

[ccordoba12]

After thinking with care about this, I think it's not really necessary. People using 3.13 will probably install the latest Jedi to get support it.

In addition, this would make things harder for other projects that can be installed alongside python-lsp-server and also use Jedi (like IPython), in case they need to test or support older Jedi versions.

[hbibel]

Thank you for looking into this @ccordoba12

Since you released a new version of pylsp, this issue is resolved - at least for Neovim users. This is coincidentally, so if you're interested why I think my issue was still valid, read on. Maybe some other users still have that issue.

People using 3.13 will probably install the latest Jedi to get support it.

This is not always the case. I encountered the issue because I use Neovim (btw) and the usual way for Neovim users to install LSPs is through mason. Mason automatically manages LSPs following this process:

• It will create a venv at $HOME/.local/share/nvim/mason/packages/python-lsp-server/venv/ and install the pylsp package. jedi is simply pulled in as a dependency of pylsp using whichever version is compatible. In my case, this was jedi 0.19.1 since I last updated the LSP last year after pylsp 1.12.0 came out.
• Unless the language server is updated, there will not be any updates to packages in the virtual environment.
• If there is a new version of pylsp and the user decides to update, Mason will delete the venv and install it again. This is why the new release coincidentally fixed the issue, because now Mason users will automatically receive jedi 0.19.2.

If Mason ran pip install pylsp==1.12.2 without deleting the venv, jedi would not have been updated and the issue would persist.

[ccordoba12]

Sorry, that's related to the way Mason/Neovim handle LSP servers. And as you said, a new version auto-fixed it, so I think it's not worth it to bump Jedi due to that.