No way to force analysis on a project that's in-progress
Brought to you by:
fabioz
Menu
▾
▴
#1375 No way to force analysis on a project that's in-progress
When working on the sort of library that is difficult to statically analyze (i.e. the sort that you'd add to the "Forced Builtins" list), there's no way to direct PyDev to forcefully analyze the files in the project for completion information. It would be EXTREMELY useful for me to be able to add something like "#@ForceAnalysis" in the __init__.py files of such libraries, so that I could take advantage of code completion during development. If this is a task that can be time-consuming, maybe something like "#@ForceAnalysis:60", where 60 is the mininum number of seconds to wait between successive attempts at forcing analysis would be more appropriate.
The real problem in this approach is that while developing code you may have temporary code that's not supposed to be executed (i.e.: code that could deadlock, erase your hard-drive, show some UI, etc.), so, this is a dangerous solution...
Maybe there's a chance that the static code-analysis could recognize the patterns you're using (or maybe you could help it a bit with little effort)? Can you give examples on the code you're trying to analyze?