Description of problem: I'm using VSCode with Jupyter notebooks plugin for prototyping some math algorytms and found that after latest update of the VSCode and this plugin it stopped to work. It prints the following output on loading any notebook file: Warn 14:51:31: StdErr from Kernel Process [IPKernelApp] ERROR | Exception in message handler: Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/ipykernel/kernelbase.py", line 268, in dispatch_shell yield gen.maybe_future(handler(stream, idents, msg)) .... File "/usr/lib/python3.8/site-packages/jedi/api/__init__.py", line 725, in __init__ super().__init__(code, environment=environment, TypeError: __init__() got an unexpected keyword argument 'column' Googling for this error I've found these discussions: https://stackoverflow.com/questions/65843310/completion-in-ipython-jupyter-does-now-work-unexpected-keyword-argument-colu https://github.com/ipython/ipython/issues/12740 It is stated that "jedi (0.18) release is incompatible with IPython 7.19" and these are versions provided currently in MGA8. It's also stated that IPython 7.20 has a fix for jedi 0.18: https://github.com/ipython/ipython/blob/7.20.0/docs/source/whatsnew/version7.rst Version-Release number of selected component (if applicable): ipython-7.19.0-1.mga8, python3-jedi-0.18.0-1.mga8 How reproducible: always Steps to Reproduce: 1. 2. 3.
Some addition: installing newer IPython with the command $pip install -U "ipython>=7.20" allows to bypass the problem.
Thank you for the report and the various pointers; and the useful workaround. Trying to pin down the exact problem that you identified, and accepting that Jedi itself is not in our packages (apart from python3-jedi), it looks as if it comes down to needing 'ipython>=7.20'. We do have versions 7.20/21/22 in Cauldron. Assigning this to DavidG who committed two of those. If we do push as an update ipython 7.20.0, can you Oleg please confirm that it solves the Jedi problem.
Summary: jedi (0.18) release is incompatible with IPython 7.19 => jedi (0.18) release is incompatible with IPython 7.19; needs 7.20Assignee: bugsquad => geiger.david68210
(In reply to Lewis Smith from comment #2) > If we do push as an update ipython 7.20.0, can you Oleg please confirm that > it solves the Jedi problem. Yes :)
So after some months now it is :) please test upcoming ipython-7.20.0-1.mga8 in Core/Updates_testing repo!
Updated packages in core/updates_testing: ======================== ipython-7.20.0-1.mga8 ipython-doc-7.20.0-1.mga8 from SRPMS: ipython-7.20.0-1.mga8.src.rpm
Assignee: geiger.david68210 => qa-bugs
Using QARepo I get: ipython-7.20.0-1.mga8 not found in the remote repository ipython-doc-7.20.0-1.mga8 not found in the remote repository
CC: (none) => herman.viaene
CC: (none) => geiger.david68210Depends on: (none) => 29969
Bug 29969, validated yesterday, updated these to: ipython-7.31.1-1.mga8.noarch.rpm ipython-doc-7.31.1-1.mga8.noarch.rpm It looks to me like we have to try to re-create the reporters original issue to see if that update fixes his issue, too. Unfortunately, the whole jupyter thing is beyond my expertise. If we could get Oleg's help, it would be ideal.
CC: (none) => andrewsfarm
Using qarepo in a vbox guest, I downloaded everything from Bug 29969, bug 30699, and bug 31156, pending updates that concern Jupyter. Then I installed jupyter-notebook, which pulled in ipython-7.31.1-1, python3-jedi, and several others, including some I had just downloaded with qarepo. There were no installation issues. I used the command "juypter-notebook" to run it, which brought up a gui inside Firefox. And that was pretty much as far as I got. I don't know how to invoke the issue that Oleg saw, so I don't know if it's fixed or not. The more I find on the Web about this, the more I see it as is pretty solidly developer territory, and the last coding I did was over 25 years ago in Atari 8-bit BASIC on an Atari 130XE. Not much help in that experience for this. I'm willing to OK this on faith that a 7.31.version has all the fixes of a 7.20 version, and a clean install. If that's not enough someone else is going to have to look at it.
> If we could get Oleg's help, it would be ideal. I'm here, just a bit busy for now. I'll try to find some time to test updated packages today...
Well, a spoon is dear when lunch time is near... I have removed ipython installed with pip and can not reproduce the problem with current versions of python and jupyter VSCode plugins. Looks like they have reworked these plugins and the bug disappeared... Anyway, I've installed ipython package from updates_testing and it works normally with all Jupyter notebook files I have. I have tested my files in both VSCode and browser-based notebook: no problems detected, so I think the package is OK and can be promoted to updates.
Thank you, Oleg. Giving this an OK, and validating.
CC: (none) => sysadmin-bugsWhiteboard: (none) => MGA8-64-OKKeywords: (none) => validated_update
Keywords: (none) => advisoryCC: (none) => davidwhodgins
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2023-0018.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED