-
Notifications
You must be signed in to change notification settings - Fork 92
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
Ibis expressions are eagerly evaluated #5499
Comments
Positron Version: 2024.12.0 (Universal) build 77 I confirmed the reprex is working, albeit with the slower speeds as @boshek indicates. I'm assuming that this is related to either the variables pane or Data Explorer eagerly evaluating Python objects. |
Thanks for opening this @jthomasmock. Also seeing #5544 which likely is a duplicate. |
… is True (#5625) Addresses #5499 by adding a custom inspector for Ibis expressions. This is very basic, and per #5573 should perhaps live eventually in Ibis itself. Ibis is a bit unusual in that its interactive mode causes computation to be executed when running the `__repr__` method, for nice interactivity in the console and in Jupyter notebooks. So here we avoid running the `__repr__` method so we don't accidentally fire off a BigQuery, Snowflake, or other query which might have unwanted costs or side effects. There is a unit test -- Ibis with DuckDB is a minor dependency to pull in relative to the rest of our test dependencies so I do not think this is too onerous.
Verified Fixed
Test scenario(s)Query in initial filing is very fast regardless of interactive setting: Link(s) to TestRail test cases run or created: |
@boshek -- do you want to try this out as well? Thanks! |
@jthomasmock - |
Can confirm that this fixes my issue. So grateful for this work. Genuine QOL improvement. |
reprex
Originally posted by @boshek in #4574
The text was updated successfully, but these errors were encountered: