Elijah ben Izzy
Elijah ben Izzy
> Thank you guys. I appreciate your receptiveness and responsiveness. Take your time. > > A couple of notes just in case > > 1. For the function, consider leveraging...
> Here is a specific example > > ``` > @parameterize( > o1=dict(x=source('fun_x_input')), > ) > def fun(x: dict, i: int) -> dict: > return x > ``` > >...
> un' even though the generate Ahh, yes, sorry, didn't see that it was called `o1`, good point! It should look like this: ```python all_vars = dr.list_available_variables() o1_var, = [var...
> python, https://docs.python.org/3/library/functools.html#functools.update_wrapper. It does provide access to the wrap So I'm not 100% sure that these are analagous to standard decorators. The decorators actually all set an attribute on...
> > It should look like this: > > ```python > > all_vars = dr.list_available_variables() > > o1_var, = [var for var in all_vars if var.name == "o1"] > >...
> > So yeah, don't know your use-case/what you need -- my general skepticism is that the contract should be at the level of the graph, not the function. >...
To enable this, look at the files in this PR: https://github.com/DAGWorks-Inc/hamilton/pull/1173/files (a) the commented out tests (b) A few commented out code-blocks We've decided to leave this out to reduce...
Hey @jernejfrank -- we outlined in detail what would be involved -- it's nothing too complicated but you get a bit of a tour of Hamilton's inner workings. Feel free...
> Hi @elijahbenizzy , awesome! Super excited to look under the hood. > > Let me poke around a bit over the weekend and maybe we can meet Monday or...
> Some thoughts (no hard stance): > > * not ideal to have `.with_modules()` accept both `modules` and `functions` (that are not `ModuleType`) > * having two entrypoints `.with_modules()` and...