Thank you Kenneth for the report.
Checking quickly whether 'jedi' & 'parso' really are omitted from 'spyder' dependencies, broadly, they are not:
 $ urpmq --requires spyder | grep jedi
python3dist(jedi)
 $ urpmq --requires spyder | grep parso
python3dist(parso)
so it is probably a question of exact versions, which the error messages rather imply:
> jedi  =0.17.2 : 0.18.0 (NOK)
> parso =0.7.0 : 0.8.1 (NOK)
python3-jedi is in python-jedi-0.18.0-1.mga8.src.rpm
python3-parso is in python-parso-0.8.1-1.mga8.src.rpm

(In reply to Kenneth Marcy from comment #0)
> I now also see an additional dialog
> box suggesting the user purchase additional products related to Spyder
> immediately after it has been launched.  This appears to me to be
> inappropriate behavior to occur within a new Mageia 8 installation.  Ads in
> a Mageia distro are unwanted.
You can be assured that Mageia is very careful about this sort of thing, and we certainly agree with your sentiments. How this arises may be beyond our control if we are (as it seems) offering a 'free' version of something which has commercial spinoffs. Doubtless the packagers will deal with this if they can.

'spyder' is officially with Philippe, so assigning this to him. CC'ing DavidG who has also dealt with it quite a lot.

Assignee: bugsquad => makowski.mageia
CC: (none) => geiger.david68210

Spyder migrated to 5.3.3 in cauldron. Feedback welcome.
I get a message that rtree should be at least in 0.9.7, but this is what we have.

Assignee: makowski.mageia => yves.brungard_mageia
CC: (none) => yves.brungard_mageia

There is a build in testing which relax dependencies requirements.
Please test:
spyder-4.2.1-1.4.mga8
python3-pyls-spyder-0.3.2-1.mga8
python-language-server-0.36.2-1.1

Sources:
python-pyls-spyder-0.3.2-1.mga8.src.rpm
spyder-4.2.1-1.4.mga8.src.rpm
python-language-server-0.36.2-1.1.mga8.src.rpm

Assignee: yves.brungard_mageia => qa-bugs

> I now also see an additional dialog box suggesting the user purchase additional products related to Spyder immediately after it has been launched.  This appears to me to be inappropriate behavior to occur within a new Mageia 8 installation.  Ads in a Mageia distro are unwanted.

I didn't get this message, can you be more explicit on this message to help to find where it is in the program.

It works in Cauldron, but I have the following errors at each launch: 
qdarkstyle >=3.0.2;<3.1.0 : 3.1 (NDK)
rtree >=0.9.7 : None (NDK)

So it seems that our version is too advanced for Spyder. Note that Fedora Rawhide still use qdarkstyle 3.0.2 (according to pkgs.org).

CC: (none) => cyril.levet0780

Loading into QArepo I get : "python-language-server-0.36.2-1.1 not found in the remote repository".
My guess: it should be python3-language-server-0.36.2-1.1, right???

CC: (none) => herman.viaene

Wrong guess, that isn't there either.

It should be:
python3-language-server+all-0.36.2-1.1
python3-language-server-0.36.2-1.1

@Yuusha
In cauldron, the message about qdrakstyle should be away.
The one about rtree is probably related to a packaging problem of rtree.

Sorry papoteur:
names should be:
python3-language-server+all-0.36.2-1.1.mga8
python3-language-server-0.36.2-1.1.mga8

No installation issues
Launched from CLI:
$ spyder
Update LANGUAGE_CODES (inside config/base.py) if a new translation has been added to Spyder
I've been able to completely run the "tour" around and run the hello world example from the build-in tutorial.
But just closing the spyder window does not free the CLI, with Ctrl-C I get 
Handling signal: 2
QProcess: Destroyed while process ("/usr/bin/python3") is still running.
I haven't a clue whther this is intended behavior or not, but otherwise it seems OK to me.
Plse delete the OK if above behavior is not correct.

Whiteboard: (none) => MGA8-64-OK

No, this is not intended behaviour.
I will look at that further.

Whiteboard: MGA8-64-OK => (none)

When closing, I get also this message two times:
QProcess: Destroyed while process ("/usr/bin/python3") is still running.
But the console is freed.
The tour is black at start behing the wizard, but I presume this is because I didn't enable transparency.
Other advices?

I never use transparency, I switch all effects off.
Maybe I didn't wait long enough to see the console being freed, this is a old slow laptop.
I will try to find time to repeat the test.

Repeated test, closing by either by "File - Quit" or by closing the window. In both cases the console is freed, although on this slow laptop, closing the window gives a noticeable longer reaction time to freen the console, but nothing really dramatic.
OK for me.

Whiteboard: (none) => MGA8-64-OK

Validating.

Keywords: (none) => validated_update
CC: (none) => andrewsfarm, sysadmin-bugs

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2022-0129.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED