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 mutkuk
Date 2005-05-05.16:55:31
SpamBayes Score
Marked as misclassified
Logged In: YES 

Uploaded new patch unchanged.

Extension case:
This func categorizes with PyThreadSatate_*. For debugger
implementors(generally implmented as extension) it is
invaluable. Indeed that's the reason I needed it in the
first place.

>1: I see your reasoning, but I disagree as when the
>developer pokes around the headers it will be more useful
>for it, the typedef, to be around the *only* call that the.... 

Not worth to remove it  IMHO just feels OK

>2. Oh, yeah the NULL check is there just in case someone
>gets smart and tries to start running Python calls before
>Python is initialized(ala Py_InitializeEx()). Besides that
>it, Py_FatalError should only be called once during the
>process lifetime, so the extra condition isn't really much
>of a performance issue.

Got it, agreed.
Date User Action Args
2007-08-23 15:42:53adminlinkissue1195571 messages
2007-08-23 15:42:53admincreate