#DBRX, a new general-purpose LLM, is now available on Databricks Marketplace!
Enterprises can use DBRX in RAG apps or to build a DBRX-style MoE model with their own data. Check it out to advance your AI initiatives. https://t.co/BPe8oFcsHz
Wow, @ProjectJupyter is the winner of the White House OSTP "Technical Advancement to Enable Open Science" category.
Amazing to see recognition of the project at a national level! Makes me proud of the ecosystem of interconnected tools we've built.
https://t.co/EQapI37In7
@akshaykagrawal This is a pretty old issue, I believe stemming from changes to support top-level await (every module level statement now runs in it's own function). Also ran into it when trying to improve support for pdb in ipyflow. It doesn't manifest for breakpoints inside of functions.
Excited that interactive dataflow and reactivity continue to gain traction with interfaces for data and scientific computing! Amazing how fast the folks at @marimo_io have made their tool one of the best out there for Python; lots of lessons to bring to https://t.co/XTvzI4fm6d
We've added an inspiration section to our README: https://t.co/6JFLGHS8hc
@marimo_io was inspired by @PlutoJL, which in turn was inspired by @observablehq. We've also remixed ideas from other reactive programming tools like @stephen_macke's ipyflow and @streamlit.
@davidbrochart I like the black background and incorporating brackets and/or an execution counter somewhere, but I think filling the space at the top and bottom adds too much noise. What do you think about [jp]term?
Also in the same session at 10:30, @sh_reya and @stephen_macke will present their work on making computational notebooks more production-ready, by applying program slicing techniques. Now you don’t need to compromise between experimentation and rigor. Take note, notebook cos.!
I have a feeling these three sentences are not enough to prevent some nasty bugs.
If you don't save a reference to an asyncio Task it could disappear at any time. Your code would stop running, but likely only when your app is under real load.
Good luck figuring that out.
📣 Introducing Ponder: Run #pandas on 1TB+ DIRECTLY in your data warehouse 🚀
Learn more below! 🧵[1/N]
https://t.co/LgowCiNQId
#python#datascience#AI#database
@sh_reya@drewmikehead@sarahchasins@adityagp@sh_reya I still remember when you noticed the opportunity to improve notebook slicing by leveraging the runtime session information and how mind blown I was by the initial results. A simple idea with fantastic execution, and I couldn't be prouder to have been part of it.
Notebook ML workflows have a lot of exploration & data wrangling, mixed w/modeling. Relevant artifacts (dataframe, model) are only a sliver of the workflow. So @stephen_macke & I developed nbslicer, a dynamic slicer for Python notebooks, built on ipyflow (https://t.co/BRiKz5DyfL)
ipyflow 💖 ipywidgets
Just put the finishing touches on the integration and really happy about how it turned out.
Always felt like ipywidgets should be able to trigger cell execution in response to, e.g., slider adjustments -- with https://t.co/XTvzI4fTVL, it's finally here!
This demo https://t.co/KjlEFQ6BM2 blows my mind:
It stores the entire execution/dependency graph of variables in a notebook and snapshots it according to your specifications.
It think that this could be used to build a better notebook that allows for instant time travel etc.
@benjamin_bolte Nope but definitely agree that we're long overdue for a copilot-like experience for open source Jupyter notebooks / lab. A direction I'm really interested is to include the runtime dataflow state in the LM prompt to see if it improves code suggestions...