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.

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

Does Python coverage require a Vim with Python support? #47

Open
jwodder opened this issue Oct 18, 2021 · 1 comment
Open

Does Python coverage require a Vim with Python support? #47

jwodder opened this issue Oct 18, 2021 · 1 comment

Comments

@jwodder
Copy link

jwodder commented Oct 18, 2021

I'm having trouble getting this plugin to work with a Python project on my MacBook, and I'm wondering if it may be due to it requiring a version of Vim that was built with Python support, which the pre-supplied Vim on macOS lacks. Is this the case? The documentation doesn't mention that. If it is the case, would it be reasonable to add support for non-integrated Pythons?

@dbarnett
Copy link
Contributor

Short answer: yes, it does depend on the vim python interface. It's a little strange that it'd be that out-of-the-way to have vim installed with python support on macOS, especially for folks working with python developer tools.

In theory it would be possible to set up a little standalone python script as an alternative to load coverage files and spit out a JSON structure or something to feed to vim, but that raises another layer of compatibility concerns finding the right installed python to invoke that'll have the right version of coverage.py installed to read the given coverage data files.

On a somewhat related note, there was some discussion in google/vim-maktaba#249 about detecting and using poetry or pipenv settings from project directories, that might be something to keep in mind if anyone is fiddling with the current mechanism of launching via maktaba#python#Eval.

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

No branches or pull requests

2 participants