is_complete_request: Is Complete Handler

In JuniperKernel: Kernel for 'Jupyter'

Description

Handler for the is_complete_request Message Type

Usage

is_complete_request(request_msg)

Arguments

request_msg

A list passed in from doRequest representing the deserialized is_complete_request message JSON.

Value

A list having names msg_type and content. The msg_type is is_complete_reply, which corresponds to the is_complete_request message. The content field complies with the Jupyter wire message protocol specification for is_complete_reply messages.

Author(s)

Spencer Aiello

References

http://jupyter-client.readthedocs.io/en/latest/messaging.html#code-completeness

Examples

## Not run: 
  request_msg <- list(code="print(")  'incomplete'
  is_complete_request(request_msg)

## End(Not run)

## Not run: 
  request_msg <- list(code="print(5)")  # 'complete'
  is_complete_request(request_msg)

## End(Not run)

JuniperKernel documentation built on May 2, 2019, 4:35 a.m.