In ST 4200, PC 4.2.2, when installing LSP 2.6.0 The library "bracex" is not available for Python 3.8

[Iceman9]

Cleanly installed ST 4200 (on RHEL, purged ~/.cache ~/.config), with PC 4.2.2 I cannot install LSP package 2.6.0 as it fails to install the dependency "bracex".

I do not know how to have a dev installation of package control, so I do not know where the problem arises, but I see that the channel v4 has bracex described for Python 3.8... The only message in sublime console, even with debug set to true for package control, I see is:

Package Control: The library "bracex" is not available for Python 3.8

I have tested the default configuration for channel (always purging ~/.cache before running sublime) and then manually setting to v4. No yield.

Any idea? I didn't do Safe mode as I read that PC 4 can't be tested in safe mode due to restart. However using v3 (and effectively Python 3.3 plugin ecosystem) LSP plugin and dependencies are installed.

[Iceman9]

I see that there is a new commit for the channel. Is that it? (packagecontrol/channel@00f80d2)

[deathaxe]

This was caused by packagecontrol/channel#66 specifying invalid versions to pin python 3.8 related releases. Those have been reverted and new channel was created. It should appear soon in official packages.sublimetext.io channel.

[Iceman9]

The official channel still haven't been updated yet.

[deathaxe]

It certainly is up-to-date. https://packages.sublimetext.io/channel.json contains releases for all supported python hosts.

However provided version 2.5.post1 might not be installed by Package Control unless #1717 is merged.

Without it .post releases are treated development or beta releases, which are ignored for libraries.

We'll have to wait for someone with write access to this repo to fix the issue.

[Iceman9]

I should've re-phrased to that installation still fails. Got it. Again, if I could have an editable Package Control mode of the plugin I could pinpoint better (or not) what's failing. I searched the docs and found nothing on this. I suppose I simply unzip, modify, rezip and run sublime?

[Iceman9]

Which is what I did. Applying #1717 fixed the issue.