You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a build for the ScipySuperpack, so I am using a script that has successfully built working packages every 2 weeks or so until now. I also tried using the instructions in README.osx, with the same result.
Thanks for the diagnostic information. This is probably related to the migration from 2to3 to six (the relevant commit is f4adec7), but I could be wrong. As a test, would you mind seeing if you are able to successfully build with Xcode 5 using the patch in #2433? If so, I'll close this issue. If not, then that means there's something funky going on.
Can you provide a full script that reproduces the error? (Or point to one of our examples that fails?) I'm unable to reproduce (once #2433 is applied, now merged to master).
Yes - I build with the latest xcode - so I guess this isn't an issue.
The build logs from matplotlib-wheels give the full output if anyone
wants to check.
FWIW, whenever I get this, it is because I have old .pyc files in my source checkout. We moved axes.py to axes/__init__.py and any lingering pyc files can get really messed up.
Activity
dmcdougall commentedon Sep 23, 2013
Looks like you're building from
master. Are you able to successfully buildv1.3with Xcode 5?fonnesbeck commentedon Sep 23, 2013
I get a different error when running a build of 1.3:
This occurs when pylab is imported.
fonnesbeck commentedon Sep 23, 2013
OK, I got a build to work using the 1.3 release. No crash.
dmcdougall commentedon Sep 23, 2013
Thanks for the diagnostic information. This is probably related to the migration from
2to3tosix(the relevant commit is f4adec7), but I could be wrong. As a test, would you mind seeing if you are able to successfully build with Xcode 5 using the patch in #2433? If so, I'll close this issue. If not, then that means there's something funky going on.fonnesbeck commentedon Sep 24, 2013
This patch does not fix the issue. Same behavior results.
mdboom commentedon Sep 24, 2013
Can you provide a full script that reproduces the error? (Or point to one of our examples that fails?) I'm unable to reproduce (once #2433 is applied, now merged to master).
fonnesbeck commentedon Sep 24, 2013
Any plotting will cause the failure. This does it for me every time:
If I roll back to the 1.3 release, the problem disappears. I will try again from master incase I made a mistake in testing the patch.
mdboom commentedon Sep 30, 2013
Make sure you remove the build directory before rebuilding to ensure a complete rebuild of the C++ code.
fonnesbeck commentedon Sep 30, 2013
This is automated in my build script, so that is not the issue.
tacaswell commentedon Aug 17, 2014
@fonnesbeck Is this still an issue?
@matthew-brett Do you build with a version of xcode?
matthew-brett commentedon Aug 21, 2014
Yes - I build with the latest xcode - so I guess this isn't an issue.
The build logs from matplotlib-wheels give the full output if anyone
wants to check.
tacaswell commentedon Aug 21, 2014
I am going to close this then.
@fonnesbeck ping to have this re-opened if you still have issues.
pelson commentedon Sep 30, 2014
FWIW, whenever I get this, it is because I have old
.pycfiles in my source checkout. We movedaxes.pytoaxes/__init__.pyand any lingeringpycfiles can get really messed up.