That line for Python dependencies means that it wants 0.7.0 and has 0.7.1. For some reason Spyder wants a specific version of that package, not >= like for most of its deps. I'm guessing that later versions of parso repeatedly broke their code, so they started requiring a known-compatible version for each release.
It may still work with such a close version, but if you want to downgrade, you can pull the previous version from the Arch Linux Archive,
sudo pacman -U
https://archive.archlinux.org/packages/p...kg.tar.zst
and then disable automatic upgrades by uncommenting the IgnorePkg line in /etc/pacman.conf and adding python-parso:
IgnorePkg = python-parso
Background reading on downgrading:
https://wiki.manjaro.org/index.php?title...g_packages
https://wiki.archlinux.org/index.php/Arch_Linux_Archive
The 'downgrade' program is not yet available for aarch64, but python-parso is an 'any' arch package so it can still be had from the Arch Linux Archive.
Some Manjaro packages are unmodified Arch packages, some are modified, and some are new with no equivalent in Arch.
We can check the Manjaro gitlab for python-parso,
https://gitlab.manjaro.org/explore?utf8=...ivity_desc
There is no project by that name, so I'm not expecting needing a modified package.
To see everything that may be affected by the downgrade, do 'pactree --reverse python-parso' and 'pactree --reverse --sync python-parso' to show the full tree of dependency relationships, first for installed packages, then for the distribution as a whole. With few exceptions it's things required by spyder, so I'm not expecting it to be a high-risk downgrade.