As anyone encountered the fact that `from flytekit...
# ask-the-community
As anyone encountered the fact that
from flytekit.models import task
results in broken stack traces in ipython? I'm digging in right now (before opening a ticket), but if anyone has seen it / has any idea what is going on please ping me.
further refined; it seems something is importing rich, or similar, when importing `flytekit.models.common`:
this stops the error:
Copy code
import os.environ

import flytekit
raise Exception("foo")
seems something about the way traceback.install() work breaks in a jupyter environment.
OK; if anyone encounters this in the future. Rich 13.1.0 fixes the issue. flytekit will install the latest rich by default, or in our case use the rich that was already in our environment which didn't have this fix in it.