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 does have a "PY_" prefix. Why didn't these flags (and the T_* flags in structmember.h) get swept up in all the hubbub around the grand renaming. Skip On Mon, Oct 3, 2016 at 10:39 AM, Victor Stinner wrote:

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 an alias in your code if it is missing:

#ifndef RO # define RO READONLY #endif

Victor

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.

--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. 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 does have a "PY_" prefix. Why didn't these flags (and the T_* flags in structmember.h) get swept up in all the hubbub around the grand renaming.

Skip

On Mon, Oct 3, 2016 at 10:39 AM, Victor Stinner wrote:

...

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 an alias in your code if it is missing:

#ifndef RO # define RO READONLY #endif

Victor

---

Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido% 40python.org

_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/ naitikchandak213%40gmail.com

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_* 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 http://bugs.python.org/issue2897.

_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido%40python.org

-- --Guido van Rossum (python.org/~guido)