Skip to content

fix setup tools deprecation pkg_resource warning manging Jedi/Emacs communication#372

Open
plandes wants to merge 2 commits into
tkf:masterfrom
plandes:master
Open

fix setup tools deprecation pkg_resource warning manging Jedi/Emacs communication#372
plandes wants to merge 2 commits into
tkf:masterfrom
plandes:master

Conversation

@plandes
Copy link
Copy Markdown

@plandes plandes commented Dec 2, 2023

After installing Python 11 and installing the latest setup tools, Emacs JEDI stopped working because a warning message mangled the JEDI/Emacs communication.

The setuptools under version 69.0.2 has deprecated the pkg_resources module and produces this warning when loading jediepcserver.py:

DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html

This pull request simply adds a warning ignore to suppress it matching on the category and error message. Per the URL given, it will need to be replaced with importlib at some point, but this at least this fixes it for the short term.

@plandes
Copy link
Copy Markdown
Author

plandes commented Dec 2, 2023

The maintainer of jedi responded and mentioned the aforementioned sys_path was taken out and replaced with the jedi.Project API instead in this issue.

Would creating a pull request that makes these changes be helpful?

Thanks in advance
-Paul

@gopar
Copy link
Copy Markdown

gopar commented Nov 7, 2024

Can we get this merged in the meantime? Seeing the same issue on my end.

@glyph
Copy link
Copy Markdown
Contributor

glyph commented Jun 1, 2025

A real fix will be needed, as the date described in #375 is drawing very close and this will be permanently broken in a few months.

@plandes
Copy link
Copy Markdown
Author

plandes commented Jun 1, 2025

This project appears to be abandoned. It seems like it's time for it to be forked and maintained by someone else. I can't do it as I currently do not have the time for it.

However, I am willing any maintainer as I do believe this is a great library.

@immerrr
Copy link
Copy Markdown
Collaborator

immerrr commented Jun 2, 2025

I'm sorry for your experience with this, folks. I have volunteered to keep the lights on for this project so to speak, but recently haven't had the time or energy to do it.

Regarding a fork, you are absolutely free to do that, but maybe you could try reaching out to @tkf first to see if he'd like to accept some help here. That's what I did few years ago.

In the meanwhile, I'm happy to get in some PRs with the changes that are needed ASAP, I don't have admin rights to add people to the repo, but I still can accept the changes. If not I'll see if I can squeeze out a bit of time this week, but no promises.

Hope it helps

@plandes
Copy link
Copy Markdown
Author

plandes commented Jun 2, 2025

@immerrr How do we reach out to him? I do not see an email address listed.

@glyph
Copy link
Copy Markdown
Contributor

glyph commented Jun 2, 2025

@immerrr

I'm sorry for your experience with this, folks. I have volunteered to keep the lights on for this project so to speak, but recently haven't had the time or energy to do it.

No worries. Your existing maintenance over many years is much appreciated, and does not obligate you to do this forever. No worries for @tkf either; sometimes life gets in the way, a friendly fork to take over the project is a normal and healthy evolution; it would be nice if @tkf could bless it just to make the namespace migration easier, but continuity of open source maintenance is a tough problem.

That said, I do really appreciate the updates, it's great to know that I don't need to immediately go out and set up an LSP, and I can keep using emacs-jedi for a while longer, as I actually quite prefer it still :)

@immerrr
Copy link
Copy Markdown
Collaborator

immerrr commented Jun 2, 2025

@plandes i may have reached out to the email he had specified in his git commits, but it's been a while and i don't remember it very clearly

@plandes
Copy link
Copy Markdown
Author

plandes commented Jun 4, 2025

@immerrr Re idea of using email used in git commits: great idea. I have sent him email. Fingers crossed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants