Re: [Python-Dev] Missing PY_ prefixes in structmember.h

2016-10-03 Thread Serhiy Storchaka
On 03.10.16 16:37, Skip Montanaro wrote: I'm sure this has a simple explanation (and is probably only of historical interest at this point), but ... While starting to port the Python Sybase module to Python 3, among other hurdles, I noticed that RO is no longer defined. Looking in structmember.h

Re: [Python-Dev] Missing PY_ prefixes in structmember.h

2016-10-03 Thread Guido van Rossum
But they most certainly are documented! So Skip's point is valid. MvL's suggestion for how to evolve this API is still the best IMO. On Mon, Oct 3, 2016 at 10:27 AM, Alexander Belopolsky wrote: > > On Mon, Oct 3, 2016 at 1:11 PM, Skip Montanaro > wrote: >> >> Why didn't these flags >> (and the T

Re: [Python-Dev] Missing PY_ prefixes in structmember.h

2016-10-03 Thread Naitik Chandak
hello Members, If any one is working AIML library for Python 3.5/3.6 version? Please let me know about it, thanks On Mon, Oct 3, 2016 at 10:50 PM, Guido van Rossum wrote: > Sounds like an oversight in a backwater of a header file. We should add > the PY symbols and deprecate the others. > > --

Re: [Python-Dev] Missing PY_ prefixes in structmember.h

2016-10-03 Thread Alexander Belopolsky
On Mon, Oct 3, 2016 at 1:11 PM, Skip Montanaro wrote: > Why didn't these flags > (and the T_* flags in structmember.h) get swept up in all the hubbub > around the grand renaming. > Note that structmember.h is semi-private - it is not included in Python.h. See discussion at

Re: [Python-Dev] Missing PY_ prefixes in structmember.h

2016-10-03 Thread Guido van Rossum
Sounds like an oversight in a backwater of a header file. We should add the PY symbols and deprecate the others. --Guido (mobile) On Oct 3, 2016 10:17 AM, "Skip Montanaro" wrote: > Thanks, Victor, but that's not quite what I was asking. Replacing "RO" > with "READONLY" is clearly no big deal. M

Re: [Python-Dev] Missing PY_ prefixes in structmember.h

2016-10-03 Thread Skip Montanaro
Thanks, Victor, but that's not quite what I was asking. Replacing "RO" with "READONLY" is clearly no big deal. My question was more wondering why I didn't find myself replacing PY_RO with PY_READONLY". Both names were part of the Public API in the early 90s, I suspect, and one of that set of flags

Re: [Python-Dev] Missing PY_ prefixes in structmember.h

2016-10-03 Thread Victor Stinner
2016-10-03 15:37 GMT+02:00 Skip Montanaro : > While starting to port the Python Sybase module to Python 3, among other > hurdles, I noticed that RO is no longer defined. Looking in structmember.h, RO was an alias to READONLY. READONLY still exists in Python 3, just use this name. You might create

[Python-Dev] Missing PY_ prefixes in structmember.h

2016-10-03 Thread Skip Montanaro
I'm sure this has a simple explanation (and is probably only of historical interest at this point), but ... While starting to port the Python Sybase module to Python 3, among other hurdles, I noticed that RO is no longer defined. Looking in structmember.h, I see that most of the macros defined the

[Python-Dev] Need a review on a patch related to weak references and the garbage collector

2016-10-03 Thread Victor Stinner
Hi, Can someone please review the patch attached to: http://bugs.python.org/issue26617 The patch seems safe and well defined, but it would be nice to have more reviews on it. It's a crash (assertion error) in Python >= 3.4 which occurs "sometimes" in asyncio. Victor