This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author roger.serwy
Recipients Roy.Fox, ned.deily, python-dev, roger.serwy, terry.reedy
Date 2012-06-05.16:03:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1338912215.29.0.240832535541.issue12510@psf.upfronthosting.co.za>
In-reply-to
Content
Callable instances now return a call tip. Good!

I agree with your analysis of the issue raised by Stephen. The get_argspec function will not fail unexpectedly.

> but typing list.append( resulting in weird behavior: something flashed and the typed text moved down a line.

I get "L.append(object) -> None -- append object to end" as the call tip on Linux. I'm not sure why it didn't work on Win 7. Could an unintentional enter key-press be the culprit?


> A different question is whether the default for callables (as opposed to non-callables) should be nothing or something like 'args unknown' or 'see docs'.

I agree that if the argspec string has no contents after all the code in get_argspec, then it should have a message added. Perhaps the following would be sufficient:

    if hasattr(ob, '__call__'):

        [truncated]

        if not argspec:
            argspec += "Arguments unknown. See docs."
    return argspec
History
Date User Action Args
2012-06-05 16:03:35roger.serwysetrecipients: + roger.serwy, terry.reedy, ned.deily, python-dev, Roy.Fox
2012-06-05 16:03:35roger.serwysetmessageid: <1338912215.29.0.240832535541.issue12510@psf.upfronthosting.co.za>
2012-06-05 16:03:34roger.serwylinkissue12510 messages
2012-06-05 16:03:34roger.serwycreate