[Python-Dev] Should PY_SSIZE_T_CLEAN break Py_LIMITED_API?
Nick Coghlan
ncoghlan at gmail.com
Tue Jul 12 11:34:16 EDT 2016
More information about the Python-Dev mailing list
Tue Jul 12 11:34:16 EDT 2016
- Previous message (by thread): [Python-Dev] Should PY_SSIZE_T_CLEAN break Py_LIMITED_API?
- Next message (by thread): [Python-Dev] PyPI index deprecation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 12 July 2016 at 23:21, Daniel Holth <dholth at gmail.com> wrote: > I was using Py_LIMITED_API under 3.5 and PY_SSIZE_T_CLEAN was set, this > causes some functions not in the limited api to be used and the resulting > extension segfaults in Linux. Is that right? No, it suggests there's a bug in the way some of the #ifdef's are interacting. Regards, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message (by thread): [Python-Dev] Should PY_SSIZE_T_CLEAN break Py_LIMITED_API?
- Next message (by thread): [Python-Dev] PyPI index deprecation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list