Files
cpython/Python
Barry Warsaw 98b6246c0c Several changes that Python carry on in the face of errors in the
initialization of class exceptions.  Specifically:

init_class_exc(): This function now returns an integer status of the
class exception initialization.  No fatal errors in this method now.
Also, use PySys_WriteStderr() when writing error messages.  When an
error occurs in this function, 0 is returned, but the partial creation
of the exception classes is not undone (this happens elsewhere).

Things that could trigger the fallback:

    - exceptions.py fails to be imported (due to syntax error, etc.)

    - one of the exception classes is missing (e.g. due to library
      version mismatch)

    - exception class can't be inserted into __builtin__'s dictionary

    - MemoryError instance can't be pre-allocated

    - some other PyErr_Occurred

newstdexception(): Changed the error message.  This is still a fatal
error because if the string based exceptions can't be created, we
really can't continue.

initerrors(): Be sure to xdecref the .exc field, which might be
non-NULL if class exceptions init was aborted.

_PyBuiltin_Init_2(): If class exception init fails, print a warning
message and reinstate the string based exceptions.
1998-09-14 18:51:11 +00:00
..
1996-10-25 14:44:06 +00:00
1994-08-29 10:43:12 +00:00
1996-10-25 14:44:06 +00:00
1997-07-19 19:48:41 +00:00
1996-10-25 14:44:06 +00:00
1997-09-05 07:33:22 +00:00
1997-07-19 19:48:41 +00:00
1997-07-19 19:48:41 +00:00
1998-04-09 21:39:57 +00:00
1996-08-29 18:10:41 +00:00
1996-08-29 18:10:30 +00:00
1996-08-19 22:12:39 +00:00
1997-11-22 21:53:48 +00:00