You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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?
The text was updated successfully, but these errors were encountered: