Re: [Pydev-code] Has the analyze only open editors setting ever had a meaning?
Brought to you by:
fabioz
From: Fabio Z. <fa...@gm...> - 2014-09-26 10:58:07
|
On Wed, Sep 24, 2014 at 9:25 AM, Andreas Pakulat <an...@fr...> wrote: > Hi, > > I recently stumbled about the 'Builder' page and its 'Analyze only open > editors' setting. It sounded like disabling this would help one of our > customers who wanted to get completion for functions in modules that are > not > yet imported. Unfortunately it turns out this preference is not being used > anywhere in the codebase and looking at the existing pydev tags has never > been used. > > I'm wondering wether I'm missing something or wether this has really been > added (to the ui) and then never used (by the builder)? > > On a related note: Is there a way to get pydev to create completions for > functions/classes in files that haven't been opened yet (after starting > eclipse)? (i.e. where do I have to look into the codebase to find the > starting point) > > Hi Andreas, Actually, that's still used... if you take a look at the code, the getter which uses the ANALYZE_ONLY_ACTIVE_EDITOR constant is org.python.pydev.builder.PyDevBuilderPrefPage.getAnalyzeOnlyActiveEditor(). What it does is that if it's unchecked, we'll analyze all the files in the workspace when they're changed (by the pydev builder) and not only if there's an editor open for that file (so, usually it's not recommended as it can be a resource hog, but if you do have CPU/RAM to spare, it's still an option). As for getting completions for functions/classes that haven't been imported, I think I don't quite follow what you mean (you do have context-insensitive code-completion which would add the import and the token -- but apparently, that's not what you meant), so, can you rephrase that to explain better your use case? Cheers, Fabio |