#197 Show error if import in shell does not work

[Tim Diggins]

if you have a forced builtin which has an error on import this is likely to be an important problem and may result in plenty of code completion errors for modules which rely on that builtin - however the fact that the particular forced-builtin module failed to import successfully is not displayed and it appears that a stub module is in its place in the code completion - possibly the last successful shell-import of this module.

The only way to find out that it is not being imported is to create a shell and try to import the module (that's if you work out what the problem is).

[Tim Diggins]

Logged In: YES
user_id=263040
Originator: YES

additionally (just discovered) it appears that even if you remove the forced builtin, pydev appears to continue using the last shell-imported structure rather than the parsed structure (ie. changes to the previously forced builtin don't seem to have an effect) -- and this seems to endure across eclipse restarts - perhaps some cached workspace file isn't being removed? (maybe this only occurs when there's some kind of import error with the forced builtin module?)

[Tim Diggins]

Logged In: YES
user_id=263040
Originator: YES

arg! sorry for the noise - no this phenomenon does NOT persist across eclipse updates (but it does appear that you need to restart eclipse after removing a module from the forced builtins - a dialogue would be helpful here).

[Fabio Zadrozny]

Logged In: YES
user_id=617340
Originator: NO

Actually, when you add/remove something from the forced builtins, it should clear up the cache without needing to restart eclipse (works here ate least)

Still, yeah, if it does not find the module (or is not able to import it), it will not say so, and will simply return no tokens for that module.

So, I'm changing it to a feature request: show error if import in shell does not work.