On Aug 1, 6:42 pm, John K Masters <[EMAIL PROTECTED]> wrote: > To suggest that, because the autocompletion worked on one method of a > module and not on another was because I had not configured the > PYTHONPATH properly is at least insulting.
We certainly didn't intend to be insulting. This it the most common cause of auto-completion problems but you are right that it's a mis-diagnosis on our part if it was just one method. We respond to sometimes hundreds of emails a day ,so we do make mistakes. It may be solved by using Reanalyze File from the right-click context menu on the editor but there's no gaurantee. This is incredibly complex code with many layers of highly optimized tokenizing, analysis, inference, caching, and then display in the various tools in Wing so it often takes a bit more time to find where the bug is. By the way, Wing 3.0 beta1 fixes a number of bugs that would lead to bad analysis, including missing methods as a result of failure to track edits in a file properly. It also improves reading completion info out of extension modules and properly handles several forms of import where it fell on its face previously. Hope that's useful... please let me know if not. - Stephan -- http://mail.python.org/mailman/listinfo/python-list
