[
https://issues.apache.org/jira/browse/BEAM-10764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenneth Knowles updated BEAM-10764:
-----------------------------------
Resolution: Fixed
Status: Resolved (was: Resolved)
Hello! Due to a bug in our Jira configuration, this issue had status:Resolved
but resolution:Unresolved.
I am bulk editing these issues to have resolution:Fixed
If a different resolution is appropriate, please change it. To do this, click
the "Resolve" button (you can do this even for closed issues) and set the
Resolution field to the right value.
> Make is_in_ipython robust
> -------------------------
>
> Key: BEAM-10764
> URL: https://issues.apache.org/jira/browse/BEAM-10764
> Project: Beam
> Issue Type: Improvement
> Components: runner-py-interactive
> Reporter: Ning Kang
> Assignee: Ning Kang
> Priority: P2
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> `is_in_ipython` determines if current code execution is within an IPython
> environment by attempting to fetch an IPython kernel through
> `IPython.get_ipython()`.
> If IPython dependency is not available or a `None` is fetched, the result
> would be False.
> We've been seeing some users using corrupted IPython dependency in their code
> base.
> If an IPython dependency is present but throws a non ImportError exception,
> it will break the Beam usage.
> I assume the similar errors would happen if the user uses an IPython
> dependency outside the range of versions in setup.py.
> I decide to make the function best effort so that it always returns False
> when errors occur.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
