Potential method to shorten evaluation time for certain packages

[rchiodo]

See this comment here:
#7159 (comment)

After some investigation I found that sympy is just evaluating a lot more types. This change allows a limit be set for expanding types. Internally in Pylance I was thinking we'd have a setting like so:

"python.analysis.minimizedPackages": ["sympy"]

This would be applied to the type argument on the filter to see what module the type comes from. If a package is in this list, the user will still get some information, but the package will analyze much faster.

The alternative would be to provide type stubs for these packages, but that can take a long time. This is more like a shortcut for when we know certain packages are slow to analyze.

[rchiodo]

After using this setting for sympy, sympy analysis times are back to what they were before 6753a5d

[github-actions]

According to mypy_primer, this change doesn't affect type check results on a corpus of open source code. ✅

[erictraut]

Please DO NOT commit this change. This will produce inconsistent and non-deterministic type evaluation results. I understand the desire to speed up sympy analysis, but this is NOT the right approach.

[rchiodo]

Okay I'll look into generating stubs instead.

[erictraut]

Stubs are one answer, but there might be other solutions. It sounds like you have done some analysis on the problem. If you're able to write up the notes about what you've found and include them in this issue, I might be able to suggest other potential solutions. I haven't had time to do an in-depth analysis of the problem yet (and probably won't have time in the near future), but if you've already done the analysis, we might be able to tag-team.

[rchiodo]

Thanks. I did add some comments but I'll try to add some more detail.