-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Optional Inclusion of Jupyter Cell Outputs #119
Comments
Yes!! , It would help in give llms or users more context on how that "notebook" should work in first place, as when we see notebook , we see not only its code , but its outputs too , so I think we can try adding it , however I think it should be by default @cyclotruc , Because thats what Notebook are for (Better Understanding and working of code) !!! |
To provide further context __OUTPUT__TYPE__ = "execute_result"
"outputs": [
{
"data": {
"text/plain": [
"[<matplotlib.lines.Line2D at 0x24ee8f511d0>]"
]
},
"execution_count": 7,
"metadata": {},
"output_type": "execute_result"
} So in this case , execute_result should be parsed output= __OUTPUT__TYPE__ = "display_data"
"outputs": [
{
"data": {
"image/png": "B64 IMAGE DATA",
"text/plain": [
"<Figure size 640x480 with 1 Axes>"
]
},
"metadata": {},
"output_type": "<Figure size 640x480 with 1 Axes>"
} so in this case We don't need that image b64 value output= __OUTPUT__TYPE__ = "stream"
"outputs": [
{
"name": "stdout",
"output_type": "stream",
"text": [
"hello\n"
]
}
] from this output = __OUTPUT__TYPE__ = "error"
"outputs": [
{
"ename": "NameError",
"evalue": "name 'oxe' is not defined",
"output_type": "error",
"traceback": [
"\u001b[1;31m---------------------------------------------------------------------------\u001b[0m",
"\u001b[1;31mNameError\u001b[0m Traceback (most recent call last)",
"Cell \u001b[1;32mIn[9], line 1\u001b[0m\n\u001b[1;32m----> 1\u001b[0m \u001b[38;5;28mprint\u001b[39m(oxe)\n",
"\u001b[1;31mNameError\u001b[0m: name 'oxe' is not defined"
]
}
], we need output as Note: for example "outputs": [
{
"ename": "ValueError",
"evalue": "'text' is not a valid format string (unrecognized character 't')",
"output_type": "error",
"traceback": ["VERY","Verbose","traceback"]
},
{
"data": {
"image/png": "FILLER b64",
"text/plain": [
"<Figure size 640x480 with 1 Axes>"
]
},
"metadata": {},
"output_type": "display_data"
}
] so the expected output from this cell should be # * output *
# ValueError : 'text' is not a valid format string (unrecognized character 't')
# display_data : <Figure size 640x480 with 1 Axes> |
I will leave it up to @cyclotruc to decide about the default behaviour. @IsNoobgrammer: In the meantime, feel free to draft a PR (or I can also do it once my current priorities are completed.) |
We are considering a feature to optionally include the outputs of Jupyter code cells. When enabled, the tool would append the last output of each code cell (if any) directly below the cell's source code as a comment.
Proposed Solution:
Request for Feedback:
Please share your thoughts on the utility of this feature. Your feedback will help us prioritize new features based on actual user needs. Thank you!
The text was updated successfully, but these errors were encountered: