Re: Would this be called a bug in inspect ?

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Stef Mientki

    Re: Would this be called a bug in inspect ?

    Terry Reedy wrote:
    Stef Mientki wrote:
    >
    > print getmembers ( wx )
    >crashes
    >>
    >but not always:
    > >>print getmembers (wx)
    >[('ACCEL_ALT', 1), ('ACCEL_CMD', 2), ('ACCEL_CTRL', 2),
    >('ACCEL_NORMAL ', 0), ('ACCEL_SHIFT', 4), ('ADJUST_MINSIZ E', 0), (
    >
    I suspect that wx has an erratic bug, which their tests do not catch.
    So I would send this off to them.
    I did, and the bug is already fixed,
    but I need some more time to update, while most of my programs crash
    with the newer version.

    But the real point is, should a module like inspect not be insensitive
    to these kind of errors ?

    cheers,
    Stef
    >
    > >>print getmembers (wx)
    >Traceback (most recent call last):
    > File "<interacti ve input>", line 1, in <module>
    > File "P:\Python\lib\ site-packages\wx-2.8-msw-unicode\wx\_gdi .py",
    >line 242, in __repr__
    > def __repr__(self): return 'wx.Colour' +
    >str(self.Get(T rue))
    > File "P:\Python\lib\ site-packages\wx-2.8-msw-unicode\wx\_gdi .py",
    >line 230, in Get
    > return _gdi_.Colour_Ge t(*args, **kwargs)
    >TypeError: in method 'Colour_Get', expected argument 1 of type
    >'wxColour *'
    >
    --
    http://mail.python.org/mailman/listinfo/python-list
Working...