Fix #719: Scraper produces incorrect output for the Anaconda 2X builtin

[AlexanderSher]

Also:

• fixed messaging for relative imports that go beyond top-level
• made amount of tasks in PythonAnalyzer dependent on the number of CPU cores

[jakebailey]

So with my example without an __init__.py, this now works:

However, if you type from . you don't get any completion for B. (It also shows the same unresolved-import message with an empty string like in #722, but I'm not sure if that's in scope.)

[AlexanderSher]

No, the change was for the cases like from ..abc in the root.

[jakebailey]

You're right, my example works in master. Sorry for the noise.

[jakebailey]

This is likely also out of scope, but the exception that gets thrown when you do something like from ..B import b otu of the root gets eaten completely. It ends up causing an exception over in the indexer. Do we know why we're eating these exceptions?

[AlexanderSher]

I'm not sure I understand what exception do you mean. Analysis error is shown in UI (red squiggles are from pylint):

[jakebailey]

I mean before this patch, on master. If you were to write that same code, then an exception is thrown somewhere and never logged, and then causes exceptions elsewhere.