Execute_result and display_data message order
SylvainCorlay opened this issue · comments
As I was adding a code_display_data test to xeus-python and xeus-cling. I am seeing the following error:
AssertionError: 'execute_result' != 'display_data'It seems that xeus is sending execute_result before display_data and that jupyter_kernel_test is expecting display_data to come first. I don't think that the protocol imposes an order though.