-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Progress for migrating to python 3.8 #2417
Comments
I suppose you can never let all plugins, which are not in the LSP organization, update and release at the same time. Thus, some must be broken. The best we can do is to inform them or even create a PR for them, maybe set a timeline, and let them break. Or py38 will never happen. |
Would be possible if you make one big monorepo with all 😆. |
@deathaxe I know that LSP-astro tries to follow the server version releases. |
Version numbers are not too important. |
@silverwind: Monorepos are not really an option due to how packages are installed by Package Control, without introducing extra complexity to pre-create and deploy packed sublime-package files. see also: wbond/package_control#1230 |
LSP-* packages in the SublimeLSP org are released :) There are LSP-* packages outside of the SublimeLSP that haven't merged or created a release for Python 3.8: I will close this issue, |
Personal note:
|
This issue is mostly a way to track the progress:
The format is the following:
- [] PACKGE_NAME(MAINTAINER) CURRENT_TAG -> NEW_TAG
4070-1.29.0 -> 4070-2.0.0
v2.2.2 -> v2.3.0
2.8.4 -> 2.9.0
2.0.29 -> 2.1.0
1.0.2 -> 1.1.0
v1.0.1 -> v1.1.0
1.3.2 -> 1.4.0
1.5.0 -> 1.6.0
1.1.0 -> 1.2.0
1.1.4 -> 1.2.0
1.0.1 -> 1.1.0
1.0.4 -> 1.1.0
v1.2.8 -> v1.3.0
0.6.22 -> 0.7.0
v2.0.3 -> v2.1.0
1.7.2 -> 1.8.0
v1.0.3 -> v1.1.0
v1.0.2 -> v1.1.0
v1.15.0 -> v1.16.0
v0.1.4 -> v0.2.0
v1.2.6 -> v1.3.0
1.3.4 -> 1.4.0
v1.0.38 -> v1.1.0
v2.3.0 -> v2.4.0
1.17.1 -> 1.18.0
v1.4.4 -> v1.5.0
v1.3.3 -> v1.4.0
2.0.1 -> 2.1.0
0.31.2 -> 0.32.0
3.4.2 -> 3.5.0
v1.0.10 -> v1.1.0
v1.1.0 -> v1.2.0
1.0.0 -> 1.1.0
v1.0.11 -> v1.1.0
v1.2.0 -> v1.3.0
2.18.0 -> 2.19.0
1.2.80 -> 1.3.0
v0.1.1 -> v0.2.0
1.0.0 -> 1.1.0
1.0.19 -> 1.1.0
v1.9.3 -> v1.10.0
1.0.2 -> 1.1.0
2.1.0 -> 2.2.0
v3.0.2 -> v3.1.0
0.0.20 -> 0.1.0
1.4.9 -> 1.5.0
1.1.1 -> 1.2.0
v2.9.0 -> v2.10.0
v2.6.5 -> v2.7.0
v2.2.3 -> v2.3.0
v0.4.19 -> v0.5.0
Deps
The text was updated successfully, but these errors were encountered: