You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Brian Hulette (Jira)" <ji...@apache.org> on 2022/05/25 23:39:00 UTC

[jira] [Commented] (BEAM-14515) Decouple interactive Beam from Jupyter

    [ https://issues.apache.org/jira/browse/BEAM-14515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542278#comment-17542278 ] 

Brian Hulette commented on BEAM-14515:
--------------------------------------

This came up on SO: https://stackoverflow.com/a/71758395

> Decouple interactive Beam from Jupyter
> --------------------------------------
>
>                 Key: BEAM-14515
>                 URL: https://issues.apache.org/jira/browse/BEAM-14515
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-py-interactive
>            Reporter: Brian Hulette
>            Priority: P2
>
> Some aspects of interactive Beam (e.g. triggering execution with ib.collect) make sense to use outside of a Jupyter notebook. We should make sure that use-cases like this are possible, and we only require a notebook if it's actually necessary. In my mind that should just be features that are _excplicitly_ integrating with Jupyter, like side panels, custom magics, etc...
> Things like caching and plotting tools even make sense to use outside of Jupyter (a plotting tool can return a handle that the user could use to save the plot as an image).



--
This message was sent by Atlassian Jira
(v8.20.7#820007)