question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Change Spyder-Kernels version designation on Spyder version bump

See original GitHub issue

So, 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:closed
  • Created 3 years ago
  • Comments:6 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
mrclarycommented, Sep 24, 2020

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!

0reactions
ccordoba12commented, Sep 24, 2020

It seems to me that there could be potential issues if users run Spyder’s release version with release versions of pyls and spyder-kernels, when the Spyder release version was only tested with (potentially updated) subrepo versions.

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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

spyder-kernels problem with Spyder 5 · Issue #15091 - GitHub
It'll be fixed in our next version, to be released in a couple of days. I just want to report I have the...
Read more >
Common Illnesses — Spyder 5 documentation
Spyder requires a supported version of the spyder-kernels package to be present in the working environment you want to run your console in....
Read more >
spyder-kernels - PyPI
Package that provides Jupyter kernels for use with the consoles of Spyder, the Scientific Python Development Environment. These kernels can launched either ...
Read more >
Not able to update the spyder-kernel - Stack Overflow
Your Python environment or installation doesn't have the spyder‑kernels module or the right version of it installed (>= 2.0.1 and < 2.1.0).
Read more >
spyder - OpenPorts.se | The OpenBSD package collection
BROKEN: needs updating for Python 3.10 · Version: 3.3.3, Package name: spyder3-3.3. · Flavors (export FLAVOR=xyz, setenv FLAVOR xyz):. python3 · Description Spyder...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found