RE: [PATCH] Use proper return type when handling python output

[Sean Estabrooks]

----------------------------------------
>
> Finally I get it =) Since vim may load libpython dynamically, 
> PY_SSIZE_T_CLEAN doesn't do its macro magic, namely it doesn't change 
> PyArg_ParseTuple symbol name to _PyArg_ParseTuple_SizeT (as You can see in 
> /usr/include/python*/modsupport.h).
>
> Now patch is a bit more complicated, please look attached py_sizet_syms.patch

Maxim,

You're on the right track obviously, but I don't really understand why the 
patch you've given is required.  How does loading libpython dynamically affect 
this sitation?  On line 45 of if_python.c we define PY_SSIZE_T_CLEAN just 
before including Python.h which will then subsequently load modsupport.h where 
the proper defines should happen.  Where does this fall down for you when 
you're compiling?

Sean

                                          

-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php