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

Use numpy from pip rather than brew. #15

Merged
merged 1 commit into from
Oct 23, 2015
Merged

Conversation

hawesie
Copy link
Contributor

@hawesie hawesie commented Oct 14, 2015

This fixes #14

This also includes the short-term fltk fix for #12

@hawesie hawesie changed the title Use numpy from pip rather than brew. This fixes #14 Use numpy from pip rather than brew. Oct 14, 2015
@hawesie hawesie mentioned this pull request Oct 14, 2015
@hawesie
Copy link
Contributor Author

hawesie commented Oct 14, 2015

Rebased on master.

@mikepurvis
Copy link
Owner

Okay, I think we should get this in so that El Cap is unbroken. When I have a chance, I'll run some experiments per the discussion in #14 and see if it would make sense to move to bottled versions of the big python packages.

Going to merge as-is, then re-remove the PCL build from source (isn't necessary any more).

mikepurvis added a commit that referenced this pull request Oct 23, 2015
Use numpy from pip rather than brew.
@mikepurvis mikepurvis merged commit b62cb96 into mikepurvis:master Oct 23, 2015
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.

numpy brew vs pip
2 participants