On Jul 22, 2010, at 12:00 AM, Stephen J. Turnbull wrote:
My understanding of OSError is that the OS is saying sorry, what you
tried to do is perfectly reasonable under some circumstances, but you
can't do that now. ENOMEM, EPERM, ENOENT etc fit this model.
RuntimeError OTOH is basically
Glyph Lefkowitz wrote:
The selection of RuntimeError in this particular case seems somewhat random and
ad-hoc,
Indeed -- usually a RuntimeError indicates that something
concerning the internals of Python itself is screwed up,
e.g. attempting to execute invalid bytecode.
The fact that it
Greg Ewing writes:
Glyph Lefkowitz wrote:
The selection of RuntimeError in this particular case seems
somewhat random and ad-hoc,
Well, I guess we'd have to catch the person who wrote the code and
ask.
Maybe this is something that could be considered in the
exception hierarchy
Greg Ewing writes:
Scott McCarty wrote:
All, I have searched everywhere (mostly the code and a little google)
and I cannot understand where the SIGKILL signal gets checked when it is
set as a handler.
Possibly it's not being checked at all by Python, but
is being rejected by
All, I have searched everywhere (mostly the code and a little google) and I
cannot understand where the SIGKILL signal gets checked when it is set as a
handler. I have scoured the Modules/signalmodule.c only to find two
instances of the RuntimeError exception, but I cannot understand how python
Hello.
We'are sorry but we cannot help you. This mailing list is to work on
developing Python (fixing bugs and adding new features to Python itself); if
you're having problems using Python, please find another forum. Probably
python-list (comp.lang.python) news group/mailing list is the best
I apologize if this is the wrong place to ask questions about Python C code,
but I didn't know where else to turn. I don't think the regular user group
will be technical enough to find this, am I wrong?
There is no forum for something this in depth. This is not a usage problem,
I want to know
On Mon, Jul 19, 2010 at 01:09:36PM -0400, Scott McCarty wrote:
I apologize if this is the wrong place to ask questions about Python C code,
but I didn't know where else to turn. I don't think the regular user group
will be technical enough to find this, am I wrong?
I am sure there are quite
We'are sorry but we cannot help you. This mailing list is to work on
developing Python (fixing bugs and adding new features to Python itself); if
you're having problems using Python, please find another forum. Probably
python-list (comp.lang.python) news group/mailing list is the best place.
On 7/19/2010 11:08 PM, average wrote:
We'are sorry but we cannot help you. This mailing list is to work on
developing Python (fixing bugs and adding new features to Python itself); if
you're having problems using Python, please find another forum. Probably
python-list (comp.lang.python) news
On Tue, Jul 20, 2010 at 12:29 AM, Steve Holden st...@holdenweb.com wrote:
Another potential developer walks away feeling unwanted?
Let just kill this thread here. SIGKILL can't be caught. :)
(I had sort of assumed that Marcos was being ironic).
Schiavo
Simon
Scott McCarty wrote:
All, I have searched everywhere (mostly the code and a little google)
and I cannot understand where the SIGKILL signal gets checked when it is
set as a handler.
Possibly it's not being checked at all by Python, but
is being rejected by the system call. The Darwin man
page
On Mon, Jul 19, 2010 at 12:11 PM, Scott McCarty scott.mcca...@gmail.com wrote:
All, I have searched everywhere (mostly the code and a little google) and I
cannot understand where the SIGKILL signal gets checked when it is set as a
handler. I have scoured the Modules/signalmodule.c only to find
On 7/19/2010 6:08 PM, average wrote:
We'are sorry but we cannot help you. This mailing list is to work on
developing Python (fixing bugs and adding new features to Python itself); if
you're having problems using Python, please find another forum. Probably
python-list (comp.lang.python) news
14 matches
Mail list logo
