Autocomplete with metaclasses in debug probe

I generally write code while stopped on a breakpoint, so that Wing is able to inspect the runtime state of my code to provide autocomplete. However, I've noticed that if I'm using a custom metaclass, Wing's autocomplete seems to have difficulty. For example:

class Meta(type):

class A(metaclass=Meta):
    a_long_name = 1

class B(A):
    another_long_name = 2


In the above, while stopped at the breakpoint I get autocomplete for B.another_long_name, but not B.a_long_name when I type them in the debug probe. If I make A a regular class, autocomplete works for both names. Interestingly, both names autocomplete when I type them in the editor window, regardless of the metaclass.Why is this? Is there something I can add to my metaclass to facilitate Wing's autocomplete?

I'm using the Wing 7 alpha, but I believe I've seen the same behaviour in Wing 6.

Tom's avatar
asked 2018-08-14 02:08:00 -0500
Wingware Support's avatar
Wingware Support
updated 2020-01-22 19:55:28 -0500
edit flag offensive 0 remove flag close merge delete


I can reproduce it and will look into fixing it, probably in the next 6.1 and 7 releases.  Note that autocompletion of instance attributes seem to work properly, the problem is with attributes on the class instance.

Wingware Support's avatar Wingware Support (2018-08-15 04:48:00 -0500) edit
add a comment see more comments