-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test_vim: Failure with Python 3.13 #571
Comments
That seems fine to me. The stacktrace in all cases isn't particularly useful. @wookayin ? If it's not much trouble, maybe also check for |
Closed
@cryptomilk any chance you can send a PR? Then we'll do a release #577 (comment) |
The failing tests were written by me, I can send a PR very soon. |
wookayin
added a commit
to wookayin/pynvim
that referenced
this issue
Oct 31, 2024
Fixes neovim#571. Problem: The `test_python3_ex_eval` test fails on python3.13 because the format of stacktrace message has changed. Solution: Check for important lines only.
wookayin
added a commit
that referenced
this issue
Oct 31, 2024
Fixes #571. Problem: The `test_python3_ex_eval` test fails on python3.13 because the format of stacktrace message has changed. Solution: Check for important lines only.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I'm trying to fix pynvim with Python 3.13 which is in Fedora Rawhide (upcoming 41). The failure I get is:
The traceback looks different now.
My current fix is for Fedora is:
Not sure if this is how you would like to address this.
The text was updated successfully, but these errors were encountered: