Closed
Conversation
Author
|
ah looks like travis is unhappy too https://travis-ci.org/github/davidhalter/jedi-vim/jobs/735363787 maybe it needs switching to 3.9?? I'll have a hack about in the travis config, not sure if that's the right thing to do... |
Merged
I didn't inspected the whole thing, but can this be related Python 2? FWIW We have dropped support for 3.6< on Parso, and inlined the annotations (which was previously hold in external stub files). |
Author
|
@isidentical there's a PR open to upgrade jedi which drops python 2 support, may need to merge that first #1025 |
Author
|
closing in favour of #1025 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi! Just thought I'd give this a go. My plan is to update the submodules for
jediandparsoand then see if I can fix any errors the tests throw up.I've done a couple so far, only one left:
not sure if those errors saying
jedi-vim: Cannot open a new buffer, use:set hiddenor save your buffermatter? are they safe to ignore?