-
Notifications
You must be signed in to change notification settings - Fork 128
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
Automatically import marimo as mo on markdown fail? #1164
Comments
You'll need to |
Ah, excellent! From an engineering perspective, it makes a lot of sense to have all cells be Python.
|
(Feel free to close if you think no more work is needed here 👍 ) |
I suppose one thing we could do is automatically add a cell that imports marimo as mo, if marimo hasn't already been imported. |
Should this functionality be extended to import any module on |
Maybe. I think any auto-importing may be too magical though; even auto-importing marimo. |
Most IDEs have an auto-import feature (mine auto-imports on save), I don't think it is too magical, especially for |
Okay yea mine does too, good point. Where would the import go, new cell at the bottom of the file? |
Bottom of the file and new cell would be my opinion. I thought trying to merge with existing imports, but could cause noisy/unwanted re-renders. |
Describe the bug
Environment
Code to reproduce
No response
The text was updated successfully, but these errors were encountered: