-
-
Notifications
You must be signed in to change notification settings - Fork 10.9k
test python3.5 32 bit debug with gcc 5 #5772
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
Conversation
e634f3f
to
f0af1a1
Compare
good idea. doesn't seem too bad. The errors on
look like an issue with this particular Python 3.5 build, those modules aren't removed. |
yes those are most likely packaging errors, I'll take care of it. |
Think so, but I'll double check tonight (not in front of that laptop now). What issue does it cause, and where is that merge happening (and guess that was always the case then)? |
would fail as it has an stderr error message in the version string. |
It's indeed mixing stderr and stdout; warning does go to stderr:
|
Looks to me like it's not distutils, but this: https://github.com/numpy/numpy/blob/master/numpy/distutils/exec_command.py#L436 Comment right above:
And docstring of |
|
@juliantaylor Mind if I close this? |
no, though we need an issue for the remaining gzip issue |
Could you open an issue then and close this. I'm in a housecleaning mode... |
cf86549
to
cbe02b4
Compare
not merge material, but lets see what breaks with new stuff
current master + #6018 is 3.5 clean AFAICT -- should we clean this up and merge it after all, or...? |
probably not, your nightly variant with allowed failure is probably better for merging |
☔ The latest upstream changes (presumably #6018) made this pull request unmergeable. Please resolve the merge conflicts. |
@juliantaylor Still want to keep this open? |
Closing this. @juliantaylor Feel free to reopen if you still want it. |
not merge material, but lets see what breaks with new stuff