Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Plugin using the legacy Python CLI, not Go #132

Closed
IsaccBarker opened this issue Mar 13, 2022 · 1 comment
Closed

Plugin using the legacy Python CLI, not Go #132

IsaccBarker opened this issue Mar 13, 2022 · 1 comment

Comments

@IsaccBarker
Copy link

Just did a full system update on my Linux box, that brought Python from 3.7 to 3.10, where the Python legacy CLI longer works. It appears that this plugin doesn't use the new Go CLI. Is there a reason for this?
@IsaccBarker
Copy link
Author

Nevermind, it appears that when the Go CLI isn't present, it falls back to the legacy python one. This should probably be documented. I'll submit a PR.

This was referenced Mar 13, 2022
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

README now includes warning about CLI fallback IsaccBarker/vim-wakatime
1 participant
@IsaccBarker