> That's an interesting definition of crash. You're just like saying: "C > has crashed because I made a bug in my program". In this context, it is > your program that crashes, not python nor C, it is misleading to say so. > > It will be python's crash if: > 1. Python 'segfault'ed > 2. Python interpreter exits before there is instruction to exit (either > implicit (e.g. falling to the last line of the script) or explicit (e.g > sys.exit or raise SystemExit)) > 3. Python core dumped > 4. Python does something that is not documented
It seems to me to be a generally accepted term when an application stops due to an unhandled error to say that it crashed. Michael Foord http://www.ironpythoninaction.com/ -- http://mail.python.org/mailman/listinfo/python-list
