Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Adding arguments to classes would make calltips look different for user-written code and global tags which I think is confusing.
Yes. I didn't even realize the difference but yes, other users might notice and be confused.
On the other hand we could change the calltip code to show the class name instead of __init__ (and attach the arguments from __init__ to it) which would make it consistent for users the other way round.
When requesting the calltip for the class itself, yes. If you are requesting the calltip for an init method, all signatures of all known init are shown and this is what I were referring to.
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).
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?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.