Chad Dombrova

I think the `name` option is a sound strategy for resolving this issue, however, I had a few more thoughts/concerns. The root concern is that I'm not sure what's the...

Hi @bintoro Any updates on this issue? I'm hoping that you have a fix stashed away on a development branch. Otherwise I can try my hand at it. I ran...

Hi all, I lurk on this project and poke my head in periodically. Here are some thoughts. > So, if the methods are going to stay, then I think we...

I tinkered with some custom objects a bit and I see your point about the `keys` attribute: if it exists and it's not a proper method, `dict(myobject)` breaks. How about...

> The motivation for dropping the current keys() method was mainly so that models could then freely define a keys field. Now you're saying it should be prevented. Why? I...

@bintoro, looks like a safe and sound solution given the constraints. There's are two other solution to this problem that we haven't discussed. They're a bit obvious, and divergent from...

@lkraider, @bintoro's concerns with removing `keys()` in favor of `(name, value)` iteration is that the user can break `dict(instance)` behavior by adding a `keys` field to their model. From earlier...

hey @bintoro, no worries, just glad to have you back :) Is your model api branch ready to test? Also, if there are any tasks on the road to 2.0...

> Actually you can already do this in some sense. There is a hidden (or rather just not advertised as official) hot key Ctrl+Shift+Y that will launch a script at...

Hi Ivan! > Btw, now that we have 300-500ms mypy daemon response time (even for huge code bases), this looks like a reasonable feature to have. I'm finally on the...