fix setup tools deprecation pkg_resource warning manging Jedi/Emacs communication#372
fix setup tools deprecation pkg_resource warning manging Jedi/Emacs communication#372plandes wants to merge 2 commits into
Conversation
|
The maintainer of jedi responded and mentioned the aforementioned Would creating a pull request that makes these changes be helpful? Thanks in advance |
|
Can we get this merged in the meantime? Seeing the same issue on my end. |
|
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. |
|
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. |
|
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 |
|
@immerrr How do we reach out to him? I do not see an email address listed. |
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 :) |
|
@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 |
|
@immerrr Re idea of using email used in git commits: great idea. I have sent him email. Fingers crossed! |
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_resourcesmodule and produces this warning when loadingjediepcserver.py: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
importlibat some point, but this at least this fixes it for the short term.