openvsx
openvsx copied to clipboard
eclipse
Python extension version at 2020.10.332292344
I understand that Jupyter's binary is proprietary, and if we upgrade, we would not have the python extension usable because of dependency.
Is there a way to remove the dependency in openvsx? Fixed at this version for one year or so is fine. But if we got fixed for too long, this extension will become obsolete.
No, Open VSX cannot know whether an extension dependency is a technical necessity or just used to automatically install the other extension, too.
One thing you could do is fork the Python extension, remove the dependency and publish it under a different namespace.
Could someone explain in more detail what is going on with the python extension? I got so far that MS split the python and jupyter extensions but the python extension requires the jupyter extension.
While people already complained, MS seems to stick with the current behavior. Don't know if this will change any time soon.
So either one could fork the python extension and remove the jupyter stuff, or open-vsx also provides the jupyter extension. This is currently not the case and in the issue description is noted that the jupyter binary is proprietary.
My question is, why is the jupyter binary proprietary? Isn't jupyter open source, too? Or is it distributed as a precompiled binary from a MS server?
It's not that Jupyter is proprietary, but that the Jupyer "adapter/extension" to VS Code is proprietary. They also made a proprietary tool called Pylane.
We have long seen the trend of companies like MS contributing to an "open source" tool and make some of the most useful features as moving proprietary parts. Thus locking users into the "open source" platform. It is the one of open source community engaging strategies commonly applied nowadays.
It has advantages and disadvantages. In one way, users are more centralized, contribution and dev will have a synergized movement, product will evolve faster. On the other side, it is hard to have forked project being successful, like what we saw for all the Linux distros. But we also avoid all the tool nightmare such as snap vs flatpak vs appimage.
It's not that Jupyter is proprietary, but that the Jupyer "adapter/extension" to VS Code is proprietary.
Maybe I miss something, but the license I see for vscode-jupyter is MIT. I would like to nail down what exactly the problematic component is.
Looks like jupyter is now optional https://github.com/microsoft/vscode-python/pull/16267
