abdelmaged

Results 8 comments of abdelmaged

I've installed python with following configurations: ``` '--prefix=~/bin/python/3.12.4' '--with-openssl=~/lib/openssl-3.0.0' '--with-openssl-rpath=auto' '--enable-shared' ``` And installed vim with following configurations: ``` env LDFLAGS="-rdynamic" ./configure --prefix=~/bin/vim/9.1.0558 --enable-python3interp=yes ```

I've just tried changing python version to 3.10.14, and no error was produced when importing socket or traceback python modules. It seems to me that vim is incompatible with newer...

What was the build for configurations for vim/python ? I just tried as well with Vim 9.1.0452 and python 3.12.4, got same errors from socket & traceback modules

I tried to build vim following configuration instead: ``` ./configure --prefix=~/bin/vim/9.1.0558 --enable-python3interp=dynamic ``` Difference is setting `--enable-python3interp` to `dynamic` instead of `yes` like it was configured in Fedora build.log This...

Fixed when using vsim + python version 3.10.14 instead of python 3.12.4

I think the problem could be in vim itself rather than ycm. Issue appears when using importing traceback on vim without ycm. I've opened this issue on vim https://github.com/vim/vim/issues/15212

It's working when building `vim` with `--enable-python3interp=dynamic` It seems I was using `--enable-python3interp=yes`, which produced the errors