rope needs a fix for Python 3.14

[penguinpee]

Fedora is preparing the next release (F43) for inclusion of Python 3.14 (scheduled to be released later this year). It turns out there is an issue with rope due to ast._const_node_type_names being dropped from Python 3.14. More details in rope's issue tracker: python-rope/rope/issues/810.

This appears to be trivial to fix. However, it needs fixing upstream and a new release. Upstream appears to be rather inactive. Last release 15 months ago, last commit seven months and no response in the ticket for over three months now.

Since Spyder directly uses rope in its own code, with the issue not being taken care of, it will affect Spyder users once they switch to Python 3.14. What are the options here other than limiting the supported Python versions¹?

Footnotes

1. Not an option for Fedora. ↩

[ccordoba12]

Hey @penguinpee, thanks for reporting. Is it not possible for you to apply the patch you submitted in python-rope/rope#818 when building the Rope package for Fedora?

[penguinpee]

Of cours we can apply the patch downstream. But that wouldn't help anyone installing Spyder directly as per the instructions you provide. For that rope needs to be patched upstream.

[ccordoba12]

Sure, I understand that. But since you said you were looking for a solution specific to Fedora, then I had to ask.

[penguinpee]

That's a misunderstanding. My concern was for Spyder. Along the lines: Are you aware that rope is currently unmaintained and will affect Spyder's user base starting with Python 3.14? What are possible ways forward for Spyder?

[ccordoba12]

Are you aware that rope is currently unmaintained and will affect Spyder's user base starting with Python 3.14? What are possible ways forward for Spyder?

Thanks for your concern but:

1. Spyder doesn't use any functionality that relies on rope at the moment.
2. Rope is an optional dependency of python-lsp-server. So, given that it's unmaintained at the moment, we can simply drop it by not requiring all its optional dependencies in our setup.py.
3. We're always one or two Python versions behind the latest one due to this kind of issues. I guess only Linux distros package Spyder for the latest one, and I'd prefer at some point they'd stop doing it (sorry, I don't want to be dismissive of your work, it's just that it introduces an additional burden for us for very little gain given that now we distribute our own Linux installers).

[penguinpee]

I apologize if I gave the impression at any point that this matter was urgent and required immediate attention. Let me respond point by point:

1. I skimmed through the code and what I found suggested otherwise. I saw rope being imported and even some internal patch for rope. I may have missed that rope is disabled by default in my first pass.
2. Agreed. That would be the easiest path forward. Though, it may require some code clean up (see point 1).
3. It is certainly not our intention to cause extra work for upstream. The objective in opening this bug was to create awareness of the issue. While Conda may be perfectly suitable for many users, it does not fit everybody's taste. Packaging Spyder (and its dependencies) allows us to address those concerns¹. Regardless of installation method, the issue described would need to be addressed at some point. Raising awareness was the least we could do in this case.

As things stand, I intent to patch rope downstream, so we can move forward.

Footnotes

1. One of those concerns meanwhile has its own dedicated xkcd comic: https://xkcd.com/1987/ ↩

[lieryan]

I've just released Rope 1.14, which includes the fix for Python 3.14 contributed by @penguinpee. Thanks for looking into this issue @penguinpee.

[penguinpee]

Thanks for the update @lieryan. Much appreciated. I've tested it downstream against Python 3.14 and 3.13 and all looks good.