Would this be called a bug in inspect ?



hello,


I'm not familiar with inspect,
but I get an error (see below) in
getmembers ( wx )

Of course this is bug in wx .

But would you also call this a bug in inspect ?
(inspect crashes and doesn't continue with th rest of the code, nor it returns the already gathered data)

thanks,
Stef

>>> import wx
>>> wx.version()
'2.8.7.1 (msw-unicode)'
>>> from inspect import *
>>> getmembers(wx)
Traceback (most recent call last):
File "<interactive input>", line 1, in <module>
File "<from <Rpyc.Connection.Connection(<Channel(<SocketStream(127.0.0.1:1184)>)>)>>", line 517, in pphook
File "P:\Python\Lib\pprint.py", line 55, in pprint
printer.pprint(object)
File "P:\Python\Lib\pprint.py", line 106, in pprint
self._format(object, self._stream, 0, 0, {}, 0)
File "P:\Python\Lib\pprint.py", line 129, in _format
rep = self._repr(object, context, level - 1)
File "P:\Python\Lib\pprint.py", line 195, in _repr
self._depth, level)
File "P:\Python\Lib\pprint.py", line 207, in format
return _safe_repr(object, context, maxlevels, level)
File "P:\Python\Lib\pprint.py", line 283, in _safe_repr
orepr, oreadable, orecur = _safe_repr(o, context, maxlevels, level)
File "P:\Python\Lib\pprint.py", line 283, in _safe_repr
orepr, oreadable, orecur = _safe_repr(o, context, maxlevels, level)
File "P:\Python\Lib\pprint.py", line 292, in _safe_repr
rep = repr(object)
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(True))
File "P:\Python\lib\site-packages\wx-2.8-msw-unicode\wx\_gdi.py", line 230, in Get
return _gdi_.Colour_Get(*args, **kwargs)
TypeError: in method 'Colour_Get', expected argument 1 of type 'wxColour *'

.



Relevant Pages

  • Re: [PATCH -v2] memdup_user(): introduce
    ... Bug. ... or copy_from_useris incorrect in this ... context. ... buf = kmalloc; ...
    (Linux-Kernel)
  • Re: Programatically Adding Document Library Webpart
    ... It does sound like a bug, I'll look into it further and see if we are ... For ages I thought it was some odd bug, ... I put it into a webpart it just wouldn't work. ... some code to check the list existed in the area I had context to and I could ...
    (microsoft.public.sharepoint.portalserver.development)
  • Re: hardware errors, do C and Forth need different things in hardware?
    ... The context of each question was clearly stated as whether it ... to trap and fix without any other context. ... do what the comment says or it is a bug that *always* needs fixing ... maybe even needing hardware traps?" ...
    (comp.lang.forth)
  • [patch 08/21] aio: fix buggy put_ioctx call in aio_complete - v2
    ... An AIO bug was reported that sleeping function is being called in softirq ... See report: http://marc.theaimsgroup.com/?l=linux-kernel&m=116599593200888&w=2 ... flush_workqueueis not allowed to be called in the softirq context. ...
    (Linux-Kernel)
  • [patch] aio: fix buggy put_ioctx call in aio_complete - v2
    ... An AIO bug was reported that sleeping function is being called in softirq ... See report: http://marc.theaimsgroup.com/?l=linux-kernel&m=116599593200888&w=2 ... flush_workqueueis not allowed to be called in the softirq context. ...
    (Linux-Kernel)