Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Embeding working with performance == 1 or 2 #18

Merged
merged 2 commits into from
Mar 21, 2017

Conversation

jeammimi
Copy link
Contributor

No description provided.

@maartenbreddels
Copy link
Collaborator

Nice that it's working, could you make sure that the previous value is set by putting it in a try/finally block:

try:
  ....
finally:
  pass # this code will execute whatever happens

@maartenbreddels
Copy link
Collaborator

👍

@coveralls
Copy link

Coverage Status

Coverage increased (+0.08%) to 79.441% when pulling 722ff51 on jeammimi:Embeding2 into e3fbe36 on maartenbreddels:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.2%) to 80.586% when pulling f60eed9 on jeammimi:Embeding2 into e3fbe36 on maartenbreddels:master.

@maartenbreddels maartenbreddels merged commit a4f00eb into widgetti:master Mar 21, 2017
@maartenbreddels
Copy link
Collaborator

maartenbreddels commented Mar 21, 2017

merged, thanks again!

@jeammimi
Copy link
Contributor Author

You are wellcome! Now you can set performance == 1 by default :)

@maartenbreddels
Copy link
Collaborator

I think that is true actually!
Also, the performance = 2 case will be supported for the next release of ipywidgets, jupyter-widgets/ipywidgets#1194 got merged. So then we can have sequences with non-constant length arrays. Not sure what we need to do with performance == 2, then, maybe just remove the performance stuff, and by default try to send it as binary.

mpu-creare pushed a commit to mpu-creare/ipyvolume that referenced this pull request Mar 26, 2018
Embeding working with performance == 1 or 2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants