Feature or enhancement

Proposal:

ImportErrors are very common, and almost always dependent on the interpreter initialization and/or environment setup. There are many common issues we could try to detect, and give users hints on the possible cause.

• Failing to load native modules when a module for a different ABI is available
  • Eg.Environment colision between regular and free-threaded builds when using the Windows installer #127294 (comment)
    • A.cp313t-win_amd64.pyd module is available, but we were looking for.cp313-win_amd64.pyd
• Failing to import a non-stdlib module with thesite initialization disabled (-S)
• Failing to import a module available in the user site-packages with the usersite initialization disabled (-s)
• Failing to import a module available in. withPYTHONSAFEPATH/-P enabled
• Failing to import a module when ignoringPYTHON* environment variables (-E) butPYTHONPATH orPYTHONHOME are set (which users might be relying on)
• (suggest more!)

Has this already been discussed elsewhere?

No response given

Links to previous discussion of this feature:

No response