Changes by James William Pye :
--
nosy: -jwpye
___
Python tracker
<http://bugs.python.org/issue1195571>
___
___
Python-bugs-list mailing list
Unsubscribe:
James William Pye added the comment:
I guess it seemed so unlikely that (C) extensions should be installing the
callback that installation should be restricted pre-Py_Initialize(); the area
completely controlled by the embedding app.
However, I have no strong attachment to that
James William Pye added the comment:
Would it be possible to require the embedding application to define the
Py_FatalError symbol?
Admittedly, it would be nice to not have the callback installation code. =\
--
___
Python tracker
<h
James William Pye added the comment:
Seeing this in 3.1 when I try to compile with mingw32 under wine:
"error: Unable to find vcvarsall.bat"
--compiler=mingw32 works in 3.0. I assume it's related to this bug?
--
nosy: +jwp
versio
James William Pye added the comment:
I tested the attached script against v2.
It further identifies consistencies between nested with-statements and
nested() that should exist(and do in v2). It answers the question: what
is the effect of a SkipStatement exception on another, outer CM?
with
James William Pye added the comment:
Just downloaded v2 and tried it out against Python 2.7a0 (trunk:70381M,
Mar 14 2009, 23:12:51).
output of the "nested_issue.py" script with patch:
j...@torch[]:org/python/trunk 0% /src/build/py/bin/python ./nested_issue.py
()
[try_with_nested
New submission from James William Pye :
I found this bug by misplacing a line of a code. Yes, I was doing
naughty things, but in the case of the class that led to the discovery,
it was inadvertent. :P
class something_else(object):
pass
class foo(object):
def __del__(self):
self.__class__
James William Pye added the comment:
I had actually forgotten that this was still open. Anything I can do to
help speed this along?
In case nobody remembers, the purpose of this was to provide a facility
to embedded applications that allows for a more graceful shutdown in
fatal error
New submission from James William Pye :
Basically, nested() doesn't seem to be consistent with explicitly nested
with-statements when an exception is thrown in a CM's __enter__.
Consider a pair of nested CMs, the inner __enter__ raises an exception
trapped by the outer. In the si
