@techee > OK, I didn't think about this and yes, I can imagine it could get quite > annoying (plus possibly slow) seeing calltips when writing your own __init__ > functions (I don't think invoking __init__() directly is common in Python).
`__init__()` needs to be manually called on super classes inside derived class `__init__()`s, but thats the only common case of explicit call AFAIK. But if the tooltip on typing `__init__(` either as definition or call was a list of all the `__init__()` functions in all global tags it will be pretty much useless anyway, so its not much of a loss. > So yeah, I'm now leaning towards dropping __init__ from the tag file, > applying this patch and also modifying the calltip code to show the class > name instead of __init__. What do you think? Well, the tooltip is supposed to be helpful, so showing the list of `__init__()`s as a list of constructors looks like what the user should type, but more important is being consistent, both global tags classes and runtime parsed classes should show the same. The symbols in the sidebar will still show `__init__()`s for open files, so they are not lost. So would agree. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3334#issuecomment-1320998072 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany/pull/3334/[email protected]>
