"from where?!? import what?!?"

on YouTube ↗29m

" summary

Shows how to find which file actually loads when imports misbehave: run python -m site to print sys.path entries, inspect module and module __spec__ to see on-disk origins, and use the CPython import-time timing/verbosity options to list implicit imports and import durations. Demonstrates when isolated mode or virtual environments with system site packages disabled remove surprising search paths, reproduces a real module shadowing bug where a local re.py breaks inspect and how the fix is verified.

AI-written summary · about

" chapters (11)

1. 0:00Welcome
2. 1:10Import system problems
3. 4:19Understanding sys.path
4. 10:15Module shadowing
5. 15:57Virtual environments limits
6. 18:35Import time side effects
7. 21:44Verbose import diagnostics
8. 24:47Exotic import pitfalls
9. 26:11Startup code side effects
10. 27:40Deeper exploration
11. 28:44Q&A

" related talks

• 45mWhat happens when you import a module?Reuven M. Lerner · PyCon Israel 2022
• 26mWhat happens behind execution of an `import` statement?Shivashis Padhi · PyConline AU 2020
• 21mHacking the Python Import SystemLiad Oz · PyCon Israel 2024
• 28mImport Deep DivePetr Viktorin · EuroPython 2015
• 30mImporting Without "import": Behind the Scenes of importlibBryce Beagle · PyCon Italia 2024
• 26mModules 101: how to avoid spaghetti, big balls of mud and houses of straw!Graeme Cross · PyCon Australia 2013
• 21mUnderstanding the Magic of Python Modules and PackagesSwastika Yadav · PyCon Italia 2024
• 27mNo time to idle about: Profiling import time in PythonDaniel Porteous · PyCon AU 2019