Shove `display` in builtins ?
See original GitHub issueDiscussed with @rgbkrk and @ivanov
We believe that the low usage of display
and of the rich display protocol is that display
is too hard to found. I think that it might be time to inject it into builtins as this will make it available; and will still allow any locally defined display function to overwrite it.
The drawback is that it will make exporting the notebook to a python script potentially invalid.
cc @fperez on this.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Snow Shovel Storage - Photos & Ideas | Houzz
Browse photos of snow shovel storage on Houzz and find the best snow shovel ... In this OmniTrack system, the versatility of each...
Read more >A Fresh New Look for Old Built-In Shelving - Apartment Therapy
Nicole filled the bottom shelves with matching gray baskets to maximize storage, and uses the top to display art and photos. It's also...
Read more >Home Display Ideas | Built in shelves living room ... - Pinterest
Built In Shelves Living Room, Living Room Tv Wall, Living Room Remodel, New ... Most current Screen transitional Fireplace Design Ideas Regardless of ......
Read more >Tag: closet builtins - With Love, Mercedes
You know the one, it's the shove-everything-in-here-and-close-the-door closet. The Monica closet. The previous owners used this closet as a second pantry, ...
Read more >"Layering" Furniture - Emily A. Clark
(If you don't want to invest in custom built-ins, a set–or two–of the ... Add height–and lots of storage/display–by filling the walls with ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The primary motivation for this is that a lot of spark documentation and other notebooks assume a global
display
function for displaying and manipulating data frames. It also tends to be very user focused.Our current
IPython.display.display
docstring is better for us as developers than users. If we expose a display function, we should make sure thatdisplay?
has more of a data scientist user focus, even if it defers toIPython.display.display
. 😄You’re wanting to expose
IPython.display.display
as the global then? I can open a separate issue if the global exposed isIPython.display.display
asdisplay
.