Slow startup due to missing imports?

[indigoviolet]

When I run with --verbose, I see a number of logs like

Could not import 'StringIO' in file '/Users/venky/dev/plus/python/.venv/lib/python3.11/site-packages/urllib3/packages/six.py'
  Looking in stubPath 'file:///Users/venky/dev/plus/python/typings'
  Attempting to resolve stub package using root path 'file:///Users/venky/dev/plus/python/typings'
  Attempting to resolve using root path 'file:///Users/venky/dev/plus/python/typings'
  Looking in root directory of execution environment 'file:///Users/venky/dev/plus/python'
  Attempting to resolve stub package using root path 'file:///Users/venky/dev/plus/python'
  Attempting to resolve using root path 'file:///Users/venky/dev/plus/python'
  Finding python search paths
  Executing interpreter: '/Users/venky/dev/plus/python/.venv/bin/python'
  Skipping '/Users/venky/.rye/py/cpython@3.11.3/install/lib/python311.zip' because it is not a valid directory
  Received 6 paths from interpreter
    file:///Users/venky/.rye/py/cpython%403.11.3/install/lib/python3.11
    file:///Users/venky/.rye/py/cpython%403.11.3/install/lib/python3.11/lib-dynload
    file:///Users/venky/dev/plus/python/.venv/lib/python3.11/site-packages
    file:///Users/venky/dev/plus/python/pdf-anonymizer/src
    file:///Users/venky/dev/plus/python/protoapp/src
    file:///Users/venky/dev/plus/python
  Looking in python search path 'file:///Users/venky/.rye/py/cpython%403.11.3/install/lib/python3.11'
  Attempting to resolve stub package using root path 'file:///Users/venky/.rye/py/cpython%403.11.3/install/lib/python3.11'
  Attempting to resolve using root path 'file:///Users/venky/.rye/py/cpython%403.11.3/install/lib/python3.11'
  Looking in python search path 'file:///Users/venky/.rye/py/cpython%403.11.3/install/lib/python3.11/lib-dynload'
  Attempting to resolve stub package using root path 'file:///Users/venky/.rye/py/cpython%403.11.3/install/lib/python3.11/lib-dynload'
  Attempting to resolve using root path 'file:///Users/venky/.rye/py/cpython%403.11.3/install/lib/python3.11/lib-dynload'
  Looking in python search path 'file:///Users/venky/dev/plus/python/.venv/lib/python3.11/site-packages'
  Attempting to resolve stub package using root path 'file:///Users/venky/dev/plus/python/.venv/lib/python3.11/site-packages'
  Attempting to resolve using root path 'file:///Users/venky/dev/plus/python/.venv/lib/python3.11/site-packages'
  Looking in python search path 'file:///Users/venky/dev/plus/python/pdf-anonymizer/src'
  Attempting to resolve stub package using root path 'file:///Users/venky/dev/plus/python/pdf-anonymizer/src'
  Attempting to resolve using root path 'file:///Users/venky/dev/plus/python/pdf-anonymizer/src'
  Looking in python search path 'file:///Users/venky/dev/plus/python/protoapp/src'
  Attempting to resolve stub package using root path 'file:///Users/venky/dev/plus/python/protoapp/src'
  Attempting to resolve using root path 'file:///Users/venky/dev/plus/python/protoapp/src'
  Looking in python search path 'file:///Users/venky/dev/plus/python'
  Attempting to resolve stub package using root path 'file:///Users/venky/dev/plus/python'
  Attempting to resolve using root path 'file:///Users/venky/dev/plus/python'
  Looking for typeshed stdlib path
  Looking for typeshed stdlib path
  Attempting to resolve using root path 'file:///Users/venky/.cache/pyright-python/1.1.365/node_modules/pyright/dist/typeshed-fallback/stdlib'
  Typeshed path not found
  Looking for typeshed third-party path
  Looking for typeshed stubs path
  Typeshed path not found

It seems (purely guessing based on the printing of these logs) that this phase takes a bunch of time and then the "analysis" is fast. Are there any suggestions or opportunities to improve this?

[erictraut]

Unless you're seeing thousands of failed imports, it's unlikely to be contributing to a significant slowdown.

If you run pyright with the --stats option, you should see a breakdown of time by analysis phase, including the "Resolve Imports" phase. It's rare for the import resolution portion to account for more than 5% of overall time unless you're running on really slow disks, and the OS's file system cache has not yet cached the relevant parts of the file system in memory. If you run with the --stats option multiple times in a row, the timing for disk-related phases ("Find Source Files", "Read Source Files" and "Resolve Imports") should drop to close to zero. The "Check" phase is almost always the one that takes the most time, and you can typically isolate that to a handful of source files using --stats in combination with --verbose.