While we're on the subject of Python 3000, what's the
chance that reference counting when calling C
functions from Python will go away?
To me this is one of the few annoyances I have with
Python. I know that Ruby somehow gets around the need
for ref. counting.
__
Well, it's fixed now. Thanks to whomever took care of
it.
--- Nick Jacobson <[EMAIL PROTECTED]> wrote:
> At the www.python.org/peps page, PEP 281 is
> erroneously listed in the "Finished PEPs (done,
> implemented in CVS)" section.
>
>
_
At the www.python.org/peps page, PEP 281 is
erroneously listed in the "Finished PEPs (done,
implemented in CVS)" section.
Yahoo! Sports
Rekindle the Rivalries. Sign up for Fantasy Football
http://football.fantasysports.yahoo
Raymond Hettinger wrote:
<< Will mull it over for a while. My first impression is that try/finally
is a better tool for the scenario you outlined. >>
You're right. try/finally takes care of my sample scenario. There may
still be a case to be made for atexit.unregister()
t would probably be better to expose the stack of registered
functions. That way you can manually unregister functions you've
registered.
--Nick Jacobson
_
Express yourself instantly with MSN Messenger! Download today - it's
ee_resource(y)
#unregister the functions, so that you don't try to free the resources
twice!
atexit.unregisterall()
Alternatively, it would be great if there were a way to view the stack of
registered functions, and delete them from there.
--Nick Jacobson
___
