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

nbagg issues with ipython 3.0 #3606

Closed
1 of 2 tasks
tacaswell opened this issue Oct 2, 2014 · 7 comments
Closed
1 of 2 tasks

nbagg issues with ipython 3.0 #3606

tacaswell opened this issue Oct 2, 2014 · 7 comments
Milestone

Comments

@tacaswell
Copy link
Member

This is on both py2k and py3k

  • double clicking kills the interaction
  • the icons are empty blocks

I am having issues down grading to ipython 2.2.0 to see if this is an issue with 3.0 on their side, but am getting 404 errors I don't understand...

@tacaswell tacaswell added the Release critical For bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions. label Oct 2, 2014
@tacaswell tacaswell added this to the v1.4.1 milestone Oct 2, 2014
@tacaswell
Copy link
Member Author

cc @pelson

@tacaswell tacaswell modified the milestones: v1.4.x, v1.4.1 Oct 2, 2014
@tacaswell tacaswell changed the title nbagg is broken nbagg is broken with ipython 3.0 Oct 2, 2014
@tacaswell
Copy link
Member Author

This seems to be issues added on the ipython side. I can reproduce this issue with ipython master branch + 1.4.0, but it works correctly with 2.2.0 + 1.4.x

cc @takluyver

3.0 (master branch) + 1.4.0

ip_nbagg

2.2.0 + 1.4.x (current maintenance branch)

ip_nbagg1

@tacaswell tacaswell changed the title nbagg is broken with ipython 3.0 nbagg issues with ipython 3.0 Oct 2, 2014
@tacaswell
Copy link
Member Author

It seems in all cases if you click fast enough things grow confused.

@tacaswell tacaswell removed the Release critical For bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions. label Oct 2, 2014
@takluyver
Copy link
Contributor

The buttons look like our toolbar buttons, so I'm guessing that some changes to the css are involved. I think we also upgraded the version of fontawesome we use for the button icons, and that necessitated changing the icon names specified in the html. @minrk or @Carreau should be able to give you more details.

Carreau added a commit to Carreau/matplotlib that referenced this issue Oct 2, 2014
@Carreau
Copy link
Contributor

Carreau commented Oct 2, 2014

Took a stab at it in #3607.

@pelson pelson mentioned this issue Oct 2, 2014
@pelson
Copy link
Member

pelson commented Oct 2, 2014

It seems in all cases if you click fast enough things grow confused.

That seems possible (if you have a high latency IPy instance I imagine it is even more pronounced). Does IPy 3 make the situation worse though @tacaswell?

@pelson
Copy link
Member

pelson commented Oct 2, 2014

P.S. #3609.

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 a pull request may close this issue.

4 participants