Hi,
Josiah Carlson <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
>>> strip
>> IMHO this should be left to hooker(apparerently not right word, but you
>> get the point :) ). If he allocates more mem. or does heavy stuff, that
>> will just fail. Anyway abort() is a failure too. Either a
Hi,
James William Pye <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
> On Tue, 2005-05-03 at 13:39 -0700, Josiah Carlson wrote:
>
>> If I'm wrong, I'd like to hear it, but I'm still waiting for your patch
>> on sourceforge.
>
> Well, if he lost/loses interest for whatever reason, I'd be
James William Pye <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
> On Wed, 2005-05-04 at 09:46 +0000, M.Utku K. wrote:
>> The reinit. issue: The old way of returning old callback when a new
>> callback is set sounds OK. Or better way: there may be an array to hold
Hi all,
> strip.
> What if more than one extension needs it ?
> Curently Im doing
>
> callback_type SetCallBack(callback_type newfunc)
>
> This will set the callback to newfunc and return the old one. Extension
> developer may discard or call them at his own will. What do you think?
>
> __
"M.Utku K." <[EMAIL PROTECTED]> wrote in news:Xns964CE11B16061token@
80.91.229.5:
> _Callback(PyFatalError_Func func) )
> is in "pyerrors.h" but implemenatiton is
> is in "Pythonrun.c". Is it OK? Im listening for more.
>
Hi,
Added the patch to the patch manager on SF.
Best regards.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.c
