Change Spyder-Kernels version designation on Spyder version bump
See original GitHub issueSo, one issue for building the Spyder standalone Mac application is that after it’s built with the subrepos of python-language-server and spyder-kernels, it is unclear which version of these packages is used.
When Spyder gets a version bump, the version designation is set, e.g. version_info = (4, 1, 5)
, and is associated with a known commit.
The problem for the standalone app is that probing the internal console for spyder-kernels will only reveal '1.10.0.dev0'
, which is virtually meaningless.
While it is possible to explicitly build with the release versions of the subrepos, in which case the exact commit for these packages can be known, this may not be the best solution since Spyder release versions are tested with the existing subrepo state, whatever commit that may be.
One solution may be to only use release version states in the subrepos. Another may be to bump the package versions in conjunction with Spyder version bumps. Or maybe there are other solutions…
@ccordoba12 , What do advise?
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Okay, I see. It’s not so convoluted, now that I understand what’s going on. I see that Spyder’s 4.1.4 and 4.1.5 were using spyder-kernels=1.9.4 and python-language-server=0.34.0 release versions in the subrepo. I was under the (erroneous) impression that the subrepos were updated more frequently to include commits between release versions of these packages. My apologies!
I understand your concerns, but before every Spyder release, I also release new versions of those two packages (if necessary) and update our requirements on them to ensure everything works together.
I know it seems convoluted to someone not very familiar with our development process, but it’s the best way I’ve found to develop such a tight integration between Spyder, spyder-kernels and python-language-server.