Also definitely not tied to using serdes. Was more for a prototype.

Why don't we special case default checks for the scalar types? I think that would snag an entire class of errors.

my initial reaction is negative - ill think about it some more

rebase

rebase

@schrockn and I doubled up a bit here. Once his revision goes through, I will rebase, so ignore the whitelist for serdes changes. I am leaving them in so that this can remain a working revision.

rebase

!@$)*&@$)&!% Helm

up

up

I would still prefer a generalized place for internal modules that are only used at development time rather than bin.

Actually one more thing: Why don't we special case default checks for the scalar types? I think that would snag an entire class of errors.

don't feel too good about copying and pasting that cloudpickle ish for this. why is that needed?

use native default values?

@schrockn thoughts on this? this isn't really a module, so I'm comfortable stashing these in bin/ - just doesn't feel right IMO to have this as a top-level thing in python_modules/

py3 type annotations? use native default values?

agree with alex. also I still need to see a proposal that is definitively better to be worth the thrash.

hmm this isnt too crazy - interested what other folks think

How do we feel about bundling this in with a crack at https://github.com/dagster-io/dagster/issues/1087

Add comment

Rebase