-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Vim plugin doesn't work with statically compiled Python #116
Comments
I will need more info as I am using the plugin right now with no issues. If you do this in your Vim, what does it say:
|
This will likely match 3.6 since Vim could read the syntax of
This will likely tell us something strange. The thing is, Did you compile your own Python and your own Vim? If so, compile Python with |
That's right, vim is using
Here's the output of that print
Yep I'm using the default Arch versions for vim and python: https://gist.github.com/zsol/f211d2359f7cb9ecc830bff02b85a6c6 And yeah it looks like vim is not using libpython: https://gist.github.com/zsol/1c93e08858fd17ddfa9ab65909416f5a |
You could ask [email protected] why Python is statically linked. Maybe it's not deliberate? In the mean time, it looks like attrs has a workaround for this anyway: python-attrs/attrs@dc6040f#diff-a05bc174beb6d89fc8e65f812a3e9360 This isn't released yet so activate your .vim/black venv, uninstall attrs and install it from GitHub:
Let me know if attrs from master work around the issue. If not, I'll have to find a different workaround for people with statically compiled Python :( |
cc @hynek, when is the next attrs release coming along? |
We could use your help on python-attrs/attrs#361 which is the last blocker. |
This will be fixed by attrs 18.1. |
Or rather, "worked around". |
No bug and no accident, this is how vim works when both runtimes were enabled at the same time. There is nothing python related statically compiled into vim. Vim does not use the regular dynamic system linker to load both libpython on application start (hence no trace via ldd or readelf) but rather loads them fully dynamical from within the vim runtime by searching for |
Operating system: Arch
Python version: 3.6.4
Black version: master
Does also happen on master: yep
vim version: 8.0 - https://gist.github.com/zsol/9c3d853bebc66128f611ae5a4d9d4c69
full trace: https://gist.github.com/zsol/3b800e69ed8995252e8be368b962790e
The text was updated successfully, but these errors were encountered: