3 ms·
That would be wonderful. A lot of the arguments are just imports, and these would have probably have the largest upside. It would be great if there was a constr
by sixo 1y ago
That would be wonderful. A lot of the arguments are just imports, and these would have probably have the largest upside. It would be great if there was a construct like
import numpy
@app.cell
def my_cell(np: types.ModuleType[numpy]):
... editor treats np like `import numpy as np` ...
I do not use Python enough to know if something like this can be hacked together. But if not, I imagine could be PIPed into the standard library if a convincing case were made for it.
- dmadisetti 1y agoWe've addressed this too by allowing a setup cell: ... with app.setup: import numpy as np @app.cell def cell_uses_np(): # no np needed in signature result = np.... The best part about this pattern is that it enables "pure" (only dependent on setup cell) functions to be addressable: with app.setup: from typing import Optional, Any @app.function def my_fn(arg: Optional[Any]) -> Any: ... but nice convergent design :) glad to see to see we're addressing pain points
- sixo 1y agoah, I recall seeing that feature but had not taken a look at it for imports. Imports ARE the case where untyped cell arguments are most annoying, but of course it would be nice to get it for free in all cases.