This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author nascheme
Recipients
Date 2002-04-09.20:29:15
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=35752

It might be a day or two before I get to this.

Regarding the type of tp_free, could we change it to be
something like:

  typedef void (*freefunc)(void *);
  ...
  freefunc tp_free;

and leave the type of tp_dealloc alone.  Maybe it's too
late now that 2.2 is out and uses 'destructor'.  I don't
see how this relates to binary compatibility though.
Why does it matter if the function takes a PyObject pointer
or a void pointer?  The worse I see happening is that people
could get warnings when they compile their extension
modules.
History
Date User Action Args
2007-08-23 15:12:08adminlinkissue540394 messages
2007-08-23 15:12:08admincreate