Matthieu Thiboust

> hey @mthiboust this may have a bit of churn on the PR/review. it might be easier to make the more incremental fixes/changes (like the fallback mentioned [in this comment](https://github.com/marimo-team/marimo/issues/6940#issuecomment-3458818201))...

Looking at `marimo`'s internals to find the root cause, I think it is because of silently handled exceptions raised by `modulefinder.ModuleFinder(excludes=excludes).run_script(module.__file__)`. I ran into two kinds of exceptions: * `ImportError:...

Using: ```python fqname = module.__spec__.name if module.__spec__ else module.__name__ finder.import_hook(fqname) ``` instead of ```python finder.run_script(module.__file__) ``` seems to solve the relative import issue. WDYT?

> Instead of replacing `run_script`, can we fallback to `import_hook` in certain cases? Sounds reasonable. BTW, I ran into another issue: only the updated files are reloaded, not the modules...

I didn't know about `ruff analyze graph --direction dependents`. It is very efficient and supports both absolute/relative imports. However, it seems to only works with files from the current project,...

A quick summary of current status. After experimenting a bit more, I am not able to reproduce a simple MWE having the `ImportError: relative importpath too deep` error. I had...

> Not sure if it is the right place to ask, but how can we pass data from the top-level app to embedded apps? I have the same question.