Transition plan

[krassowski]

Items based on @ccordoba12's palantir/python-language-server#901 (comment):

• move this repo under python-lsp/python-lsp-server
• rename the package to python-lsp-server (PR: Rename namespace to pylsp and package to python-lsp-server #10)
• remove versioneer (PR: Rename namespace to pylsp and package to python-lsp-server #10)
• rewrite the Readme to remove references to VSCode (its client hasn't received any update in ages) (PR: Remove references to VSCode in Readme #11)
• get a new version on PyPI.
• Release a new version of python-lsp-jsonrpc (PR: Update package name, remove Python 2 compatibility and update CIs python-lsp-jsonrpc#2).

My wishlist:

• rewrite the readme to markdown (Rewrite README from rst to md #6)
• remove Python 2 support (PR: Rename namespace to pylsp and package to python-lsp-server #10)
• update copyrights notices; the last commit under Palantir was in December 2020, so we can update them all to 2020 (currently are all at 2017) and add Copyright 2021 Python Language Server Contributors in addition to the old Palantir notices, which would be unambiguous (PR: Rename namespace to pylsp and package to python-lsp-server #10)

[ccordoba12]

rewrite the readme to markdown

Agreed.

remove Python 2 support

I think we shouldn't mix renaming the package and getting it off the ground with this task. So for now we should just make sure everything is working fine after the rename.

update copyrights notices

Agreed.

[frenzymadness]

If I might add a point: It would be nice to add Python 3.9 and 3.10 (alpha 6 currently) to the CI.

[krassowski]

Note on PyPI package: python-ls is already taken (https://pypi.org/project/python-ls/) and does not seem as a good target for PEP 541 procedure (as it has some users and was active within last 2 years); it might be easier to reclaim pyls using PEP 541 (which would need to be reported here https://github.com/pypa/pypi-support/issues and seem to take a long time anyways). Probably another (temporary?) name might be needed.

[ccordoba12]

Probably another (temporary?) name might be needed.

Yeah, I agree with that. What about pyls-server?

[xrogaan]

If you have trouble finding a proper name, I would suggest yet another python-language-server, or yapls for short. (And it rolls off the tongue!) apls is sadly already taken.

[bnavigator]

yapyls

Turkish yapılış: https://translate.google.com/?sl=tr&tl=en&text=yapilis&op=translate

[bnavigator]

Any news? With Python 3.9 the pressure increases to update Jedi from 0.17.2. pyls is one of the show stoppers to do so.

[ccordoba12]

We will put resources to make this transition a reality most probably during April. But we can't commit to do it before that time.

[xiaoxiae]

Other names (taken from "Python Language Server") that sound decent are PLanS and PyLaSer.

[marimeireles]

PyLaSer is really cool.
Also, hope I can help around a bit! :)

[marimeireles]

Note on PyPI package: python-ls is already taken (https://pypi.org/project/python-ls/) and does not seem as a good target for PEP 541 procedure (as it has some users and was active within last 2 years); it might be easier to reclaim pyls using PEP 541 (which would need to be reported here https://github.com/pypa/pypi-support/issues and seem to take a long time anyways). Probably another (temporary?) name might be needed.

Hey @krassowski :)
I didn't find an issue there, do you mind if I open one?
Also, how can I help with the pypi release? Should we complete this list first?

[ccordoba12]

Hey @marimeireles, @andfoy is working on that in PR #10.

[douglasdavis]

After #10 is the "official" new name for the executable pylsp? (asking to help transition https://github.com/emacs-lsp/lsp-mode/)

[ccordoba12]

The name of the module, you mean?

[douglasdavis]

I mean the entry point in setup.py:

python-lsp-server/setup.py

Line 72 in 0a3352d

'pylsp = pylsp.__main__:main',

[ccordoba12]

Yep, that's the new name.

[andfoy]

We have our first release officially on PyPI! https://pypi.org/project/python-lsp-server/, thanks for your help with the transition

[bnavigator]

What's next? Migrate spyder and all the plugins?

[andfoy]

Yes, also we need to publish new conda-forge packages, as well opening issues in all known pyls plugins to inform their maintainers that they should update to use the new package