Revision history [back]
If you're not debugging or working in the Python Shell, Wing is using only static analysis to offer completion, and the code where it's failing is created dynamically in a way that resists static analysis. You can get Wing to also use dynamic/runtime analysis by setting a breakpoint and running to it, or working interactively in the Python Shell. That way it should be reporting what is actually there at runtime, as does any shell like iPython.
If you're not debugging or Are you working in the Python Shell, Wing's editor? If so, Wing is using only static analysis to offer completion, and my guess is the code where it's failing is created dynamically in a way that resists static analysis. You can get Wing to also use dynamic/runtime analysis by setting a breakpoint and running to it, or working interactively in the Python Shell. That way it should be reporting what is actually there at runtime, as does any shell like iPython.runtime.