[
https://issues.apache.org/jira/browse/BEAM-6417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17122148#comment-17122148
]
Kenneth Knowles commented on BEAM-6417:
---------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Option to not fork DirectRunner
> -------------------------------
>
> Key: BEAM-6417
> URL: https://issues.apache.org/jira/browse/BEAM-6417
> Project: Beam
> Issue Type: Improvement
> Components: beam-model
> Reporter: Thomas Deegan
> Assignee: Ahmet Altay
> Priority: P3
> Labels: stale-assigned
>
> Hi. When using a python debugger, it would be nice to be able to debug ops as
> they are run locally by --runner DirectRunner however it seems that Beam
> forks the process to actually run the ops. Unfortuatnely most python
> debuggers (mine is pydevd) don't support following forks. It it possible to
> add a flag to DirectRunner to keep the DIrectRunner in-process?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
