Closed AntoineD closed 11 years ago
Its not our task if they do it wrong. python 2.x and 3 are clearly almost different languages, because they are compatible to some extend only. For this reason it was wrong just providing upstream, without keeping an old version. The right way to do this would have been forking: provide old and new version or provide a configuration option within the plugin choosing one or the other implementation. The VAM maintainers fixing this is beyond our scope. A workaround would be you uploading an old version to github, and then it can be added and downloaded from there to support old python versions. However I think it should be discussed with the author and point him to this thread.
I agree with @MarcWeber. Upstream should put both versions in one archive or even in one file and not abuse the intended usage of vim.org downloads.
I'll upload an archive with both versions of python.vim at vim.org but in the meantime you can find both versions in the python.vim folder at github.com
@hdima : thanks !
@AntoineD Sorry for delay but I decided to do it properly and merged Python 2 and Python 3 script versions into the single python.vim script (Thanks @MarcWeber for the suggestion). It allows you to edit scripts for Python 2 and Python 3 in a single Vim session for example. Check the comments in python.vim header for details.
python3 variant of the vim script 790 is available (python%790 version 3.0.7) but not the python2, could you please add it?