Autocomplete with metaclasses in debug probe

asked 2018-08-14 02:08:00 -0500

Tom gravatar image

updated 2019-03-15 10:03:11 -0500

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):
    pass

class A(metaclass=Meta):
    a_long_name = 1

class B(A):
    another_long_name = 2

breakpoint()

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.

edit retag flag offensive close merge delete

Comments

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 gravatar imageWingware Support ( 2018-08-15 04:48:00 -0500 )edit