[Python-porting] Py_TPFLAGS_HAVE_{WEAKREFS,ITER} in Python 3
Barry Warsaw
barry at python.org
Fri Apr 27 19:06:52 CEST 2012
More information about the Python-porting mailing list
Fri Apr 27 19:06:52 CEST 2012
- Previous message: [Python-porting] Py_TPFLAGS_HAVE_{WEAKREFS,ITER} in Python 3
- Next message: [Python-porting] Py_TPFLAGS_HAVE_{WEAKREFS,ITER} in Python 3
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Apr 27, 2012, at 05:48 PM, Amaury Forgeot d'Arc wrote: >This is correct. I checked that everywhere Py_TPFLAGS_HAVE_ITER is used in >Python2.7, the corresponding code in Python 3 does as if this flag is always >set. > >So you could either #ifdef its usage, or simply put in some compatibility >header file: >#if PY_MAJOR_VERSION >=3 ># define Py_TPFLAGS_HAVE_ITER 0 >#endif Thanks for the confirmation. I've been wondering if Benjamin might be interested in contributions to `six` that address C compatibility. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: <http://mail.python.org/pipermail/python-porting/attachments/20120427/14dc3ed7/attachment.pgp>
- Previous message: [Python-porting] Py_TPFLAGS_HAVE_{WEAKREFS,ITER} in Python 3
- Next message: [Python-porting] Py_TPFLAGS_HAVE_{WEAKREFS,ITER} in Python 3
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-porting mailing list