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

Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/06/05 00:30:29 UTC

[GitHub] [beam] damccorm opened a new issue, #21609: Decouple interactive Beam from Jupyter

damccorm opened a new issue, #21609:
URL: https://github.com/apache/beam/issues/21609

   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 _explicitly_ 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).
   
   Imported from Jira [BEAM-14515](https://issues.apache.org/jira/browse/BEAM-14515). Original Jira may contain additional context.
   Reported by: bhulette.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org