UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc2 in position 0: unexpected end of data about vim-plugins HOT 5 OPEN

This seems to be a problem with the Python interface rather than our plug-in. Our plug-in creates a data structure containing a string '\xc2' somewhere, which is a perfectly valid operation in VimScript. On the other hand, the UnicodeDecodeError seems very common in Python (which has probably something to do with the "Very High Level Embedding" and the fact that you have to serialize all data to transfer it into the Python state.)

Could you please name some of the plug-ins causing these problems? I would like to get a better overview of the issue.

from vim-plugins.

This is the only one which raise the error.

I try the following commands, and they appear to be collect.

:py3 vim.command('let g:abc="\xc2"')
:py3 print(vim.eval('g:abc'))

So, I think there is some other problem in the plugin. Beside, I grep the code with '\xc2' and 'Â' in the repository, but nothing found. Could you tell me the full path of the structure ?

from vim-plugins.

Sorry, a lot to do recently. Let me come back to this.

Could you please name some of the plug-ins causing these problems? I would like to get a better overview of the issue.

What I meant by this is:

Which plug-ins are using the call python3 vim.eval('extend(g:, {})')? I would like to learn more about this issue, therefore I would like to study these plug-ins.
I would suspect that transferring the whole global namespace (g:) of Vim is unnecessary in most situations, but I might be wrong. Only transferring parts of it would avoid this problem, but maybe some plug-ins actually depend on doing this.

from vim-plugins.

This should be addressed by this branch:
https://github.com/WolfgangMehner/vim-plugins/tree/template-dev
I'll merge it into the master at some point.

from vim-plugins.

The fix is now also included in the main branch.

from vim-plugins.