New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error on some tooltips in shell - inspect.getfullargspec needed(?) #941

vbr opened this Issue Jul 24, 2018 · 0 comments


None yet
1 participant
Copy link

vbr commented Jul 24, 2018

I noticed a ValueError in wx Shell, when some calltips should be shown;
the error message (emited from the standard library ...\lib\ suggests, that the a newer API should be used, it is:
line 178 ( in version '4.0.4a1.dev3916+9577c312 msw (phoenix) wxWidgets 3.0.5')
argspec = inspect.getfullargspec(obj)
to be changed to:
argspec = inspect.getfullargspec(obj)

This simple replacement in the source seems to solve this problem (for the cases I noticed), however, I can't judge possible corner cases or further dependencies in other code.

I use Win 10 64bit, python 3.6.3 32bit, wxpython '4.0.4a1.dev3916+9577c312 msw (phoenix) wxWidgets 3.0.5'

The error occurs if tooltips of some modules should be displayed, which aparently use a newer format of function annotations. e.g. json.dump( .

The error traceback is shown below - it is redirected to a dialog in my script, hence the unusual formatting.

 Function has keyword-only parameters or annotations, use getfullargspec() API which can support them 
[<FrameSummary file ...\Python36-32\lib\site-packages\wx\py\, line 495 in OnChar>, 
<FrameSummary file ...\Python36-32\lib\site-packages\wx\py\, line 1194 in autoCallTipShow>, 
<FrameSummary file ...\Python36-32\lib\site-packages\wx\py\, line 156 in getCallTip>, 
<FrameSummary file ...\prog\Python36-32\lib\site-packages\wx\py\, line 178 in getCallTip>, 
<FrameSummary file ...\prog\Python36-32\lib\, line 1072 in getargspec>]

Thanks and regards,

@mesalu mesalu referenced this issue Jul 25, 2018


Fix 941 #942

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment