-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Daily build fails at "import matplotlib.pyplot as plt" #3568
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
Comments
@tonysyu - obviously the stylelib folder isn't there - but I wouldn't expect it to have to be there. Any thoughts? |
I suspect that this is related to the changes made to play nice with pyfreeze. How did you install mpl? Is this from @takluyver 's ppa? The debian meta-data might need some updating. |
Yes I am using @takluyver 's ppa. Since adding it about a year ago I never changed anything anymore. |
I'm happy to update that if it needs changes - I don't really pay much attention to it except when I get failure notifications. Or if someone else wants to update it, the packaging information is stored here: https://code.launchpad.net/~takluyver/matplotlib/debian-daily (You can make merge proposals, which are the LP equivalent of pull requests) |
Specifically, I suspect that #3390 is the source of the change that broke the daily build. |
I am going to close this as this is a downstream(?) problem. @spiessbuerger Also make fully remove the current installation and try re-installing, some files got moved around, it is possible some deleted files got left behind and are now messing you up. |
I've copied across a fix from the main Debian packaging: hopefully this will fix the problem when it rebuilds some time in the next 24 hours. http://bazaar.launchpad.net/~takluyver/matplotlib/debian-daily/revision/33 |
@takluyver , @tacaswell, @pelson - Everything works again. Thanks to all of you! |
You're welcome. Thanks for bringing the issue to my attention. I don't |
I currently get an error when running "import matplotlib.pyplot as plt". Can't really track down the cause.
In Python 2:
In Python 3:
The text was updated successfully, but these errors were encountered: