##// END OF EJS Templates
Clear filter
Show hidden
Commit Message Age Author Refs
load previous
r29568:1dcf40e3
Mask issue cause by new langchain-core
krassowski
0
r29567:62943a74
Make the test work with actual buffer
krassowski
0
r29566:0eac64cf
Make the test fail if there are spurious new lines at the end
krassowski
0
r29561:f3e796c8
Add changelog for 8.35 and before (#14868)
Michał Krassowski
merge
0
r29560:ae05af76
Grammar
Michał Krassowski
0
r29559:58079e0b
Add changelog for 8.35 and before
krassowski
0
r29557:37b41f5e
back to dev
krassowski
0
r29556:f9097f68
release 9.1.0
krassowski
0
r29555:d1d12413
IPython 9.1 release notes (#14862)
Michał Krassowski
merge
0
r29553:035b18eb
Grammar, wording
krassowski
0
r29552:c680afe8
No need for bullet with two points
krassowski
0
r29551:9d983628
IPython 9.1 release notes
krassowski
0
r29550:d66c4569
Fix typos in tips (#14859) There were some typos, grammatical slips, and inconsistent styling in the tips. (Thank you for this project, I am using it right now to teach some new Pythonistas, and happened to notice the "view it's source" typo.)
Michał Krassowski
merge
0
r29549:48df9a3c
Fix typos
Matt Hall
0
r29548:b554fdea
Enhance `%notebook` to save outputs, including MIME types and exceptions (#14780) ### Description: This PR implements an enhancement to the `%notebook` magic command, enabling it to optionally save the output, including the MIME types and exceptions. ### Changes: Introduced two new dictionaries, `output_mime_bundles` and `exceptions` in history manager, to store output MIME types and exceptions separately. This prevents inflating the history. When the `%notebook` command is invoked, the code extracts MIME types and exceptions from the `history_manager` and appends them to the respective output cells in the generated notebook. ### Feedback Request: Currently, we are using `mime_obj.get_figure()` to retrieve the MIME data for Matplotlib objects. However, this approach only works for the figure object. Are there any other approaches to capture MIME data ? I am using `VerboseTB` to get a structured traceback. While this works for most errors, it doesn't handle syntax errors and some other edge cases very well. In `interactiveshell.py`, different types of errors are handled by using different traceback formats. Should we take the same approach here to handle different types of exceptions? It might result in some repetition, but it could improve error reporting for edge cases.
Michał Krassowski
merge
0
r29547:71862afd
Patch the `write` method instead to fix downstream tests
krassowski
0
r29546:116ee9e5
Fix typo in `tips.py` (#14856)
Michał Krassowski
merge
0
r29545:ea34a1a8
Typo in `tips.py`
carschandler
0
r29544:eb6a602e
reset-execution-count-to-1
Darshan808
0
r29543:0587325e
reset-color-to-nocolor
Darshan808
0
load next
< 1 .. 4 5 6 7 8 .. 1393 >
showing 20 out of 27849 commits