Skip to content

Conversation

@takluyver
Copy link
Member

Extends #6566 with a couple of fixes that have been holding it up from getting merged.

@takluyver
Copy link
Member Author

ping @jdfreder @jasongrout @SylvainCorlay - I think we had decided that this made sense, but that's not recorded on #6566.

@jdfreder
Copy link
Contributor

I'm taking a look...

@jdfreder
Copy link
Contributor

Straight forward, looks good to me. 👍

@Carreau
Copy link
Member

Carreau commented Dec 18, 2014

+1. The logic seem repeated. Should/Could it be moved to DOMWidget ? (does it make sens)

@SylvainCorlay
Copy link
Member

+1. I agree that in most cases, value= is only noise.

@jdfreder
Copy link
Contributor

Should/Could it be moved to DOMWidget ? (does it make sens)

This is what I originally suggested. @SylvainCorlay and I discussed it at the Bloomberg hackathon NY and he convinced me, because not all DOM widgets have value (even the builtin ones), it doesn't feel right to move it into the base.

jdfreder added a commit that referenced this pull request Dec 18, 2014
Widget values as positional arguments
@jdfreder jdfreder merged commit e3f7b02 into ipython:master Dec 18, 2014
@minrk minrk modified the milestone: 3.0 Jan 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants