[PYTHON MATRIX-SIG] Ruminations on SIGFPE

Konrad Hinsen hinsen@ibs.ibs.fr
Wed, 18 Sep 96 10:32:50 +0100


> So for the moment I'm stuck on Part B.  I need to understand the
> requirements of Python numerical users better, and I need to understand
> the context in which the current Python signal handling model was
> developed - what is sacred, etc. I am probably limited by my lack of
> knowledge or imagination in solving this problem.  In any case, I would
> appreciate hearing from the Matrix SIG and Python developers about
> this matter.

I don't know much about how Python handles signals, but I do know that
as a user I'd vastly prefer a Python exception to both NaNs and core
dumps.

If I understand you correctly, there would be no problem in having
Python raise an exception at the end of the next virtual instruction,
which would be sufficient for operations that don't take much time.
Maybe potentially costly operations (such as matrix inversions) ought
to provide their own exception handlers.

Konrad.
-- 
-------------------------------------------------------------------------------
Konrad Hinsen                          | E-Mail: hinsen@ibs.ibs.fr
Laboratoire de Dynamique Moleculaire   | Tel.: +33-76.88.99.28
Institut de Biologie Structurale       | Fax:  +33-76.88.54.94
41, av. des Martyrs                    | Deutsch/Esperanto/English/
38027 Grenoble Cedex 1, France         | Nederlands/Francais
-------------------------------------------------------------------------------

=================
MATRIX-SIG  - SIG on Matrix Math for Python

send messages to: matrix-sig@python.org
administrivia to: matrix-sig-request@python.org
=================