Closed farisachugthai closed 12 months ago
don't be too afraid to break 2.7 if there is clear benefit. pynvim 0.5 can be py3.5+ only if we want to.
Hahaha thanks for the tip! I wanted this refactored to a separate function so that if the decision to go pure py3 gets made we have the weird py2 / py3 thing contained to 1 function and can simply remove the except ImportError: import imp
malarky
I think it fixes my issue. https://github.com/neovim/pynvim/issues/478
The PR is completed?
I think compat.py
and scripts_host.py
needs to be changed.
I have imported your commit in https://github.com/neovim/pynvim/pull/486.
Since there are no reasonable alternatives to imp in python2.7, I figured it'd be the easiest to try importing python3 modules and if that fails, fall back to the previous method. However this will remove that annoying DeprecationWarning for everyone using python3.