Better error messages for unsupported features

[strokirk]

Hi! pylyzer sounds like a very interesting project. However, when I tried it out on a very small program, I got a number of false positives (for the stdlib), and slow performance (for 3rd party libs).

To make the experience better for first-time users, how about exiting early from unimplemented checks, with a debug warning that that feature is not ready?

For example:

• checking whole directories
• checking pip-installed libraries
• checking certain parts of the stdlib

[mtshiba]

Analysis of third-party libraries is, in fact, one of the experimental features. This feature is supposed to apply only to the beta version, but was inadvertently enabled in v0.0.30 and has been disabled in v0.0.31. You can try it by building with the experimental feature flag.

One reason it is slow is that pylyzer does not yet support parallel analysis (now I'm working on this).

And I'm also in the process of fixing the problem of false positive errors.

IAC, this tool has just been released and is still in its infancy. Please wait a little longer until it is ready for real world use.