Skip to content
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

Make ropevim python3 compatible (for Debian) #63

Closed
bgribble opened this issue Mar 23, 2017 · 3 comments · Fixed by #76
Closed

Make ropevim python3 compatible (for Debian) #63

bgribble opened this issue Mar 23, 2017 · 3 comments · Fixed by #76

Comments

@bgribble
Copy link

bgribble commented Mar 23, 2017

For some time, Debian's vim has been built with +python3 -python. See this stackexchange question with an answer from the Debian vim maintainer. It appears to be a packaging issue rather than an ideological or technical choice.

I spent an hour or so last night trying to make ropevim work with either python 2 or 3, and made some headway but it's not there yet. I'll put up a PR if I get something working. If someone else wants to do it first be my guest!

@fdjcomp
Copy link

fdjcomp commented May 5, 2019

this is the reasaon packages get a bad reputation
I had a similar frustrating experience with no real luck to get it working
much of the pyhon code seems to be for pyhon2 (and thus fails in vim debian)
a warning to this effect is the minimum requirement

@soupytwist
Copy link
Contributor

I think python3 support in rope is in a much better state than it was. Can you share any specific errors? I'm curious what's lacking python3 support, not obvious from a quick look over the code.

@mcepl
Copy link
Contributor

mcepl commented Feb 3, 2020

I am actually running ropevim with python3 (3.7.3) in neovim (almost 0.5.0), and it works just fine. The only problem is variable :ropevim_prefer_py3 which has to be set. I will fix that momentarily.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants