Lennart Regebro regebro at gmail.com
Tue Mar 15 16:10:17 CET 2011

• Previous message: [Python-Dev] public visibility of python-dev decisions "before it's too late" (was: PyCObject_AsVoidPtr removed from python 3.2 - is this documented?)
• Next message: [Python-Dev] public visibility of python-dev decisions "before it's too late"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Mon, Mar 14, 2011 at 19:22, Reid Kleckner <reid.kleckner at gmail.com> wrote:
> I don't know how your code works, but handling either type from C
> seems very straightforward to me.  You can simply use #ifdef
> Py_COBJECT_H to see if the cobject.h header was pulled into Python.h.
> Similarly for Py_CAPSULE_H.  All you lose is that if you do get a
> PyCObject, there is no way of knowing if the void pointer is of the
> right type.

Good to know.

>> **We can't deprecate an API in one version and drop the API in the
>> next. This is not acceptable. The deprecation period must be much
>> longer!**
>
> Surely, you must be joking.

No.

//Lennart

---

• Previous message: [Python-Dev] public visibility of python-dev decisions "before it's too late" (was: PyCObject_AsVoidPtr removed from python 3.2 - is this documented?)
• Next message: [Python-Dev] public visibility of python-dev decisions "before it's too late"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list