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

Issue1799 durack1 update scipy 0.16.1 to 0.17.0 #1816

Merged
merged 1 commit into from Feb 4, 2016

Conversation

Projects
None yet
3 participants
@durack1
Member

durack1 commented Feb 4, 2016

Fix #1799 - Update scipy 0.16.1 to 0.17.0

doutriaux1 added a commit that referenced this pull request Feb 4, 2016

Merge pull request #1816 from UV-CDAT/issue1799_durack1_UpdateScipy0.…
…16.1To0.17.0

Issue1799 durack1 update scipy 0.16.1 to 0.17.0

@doutriaux1 doutriaux1 merged commit 7e4660b into master Feb 4, 2016

4 of 6 checks passed

cont-int/LLNL/Darwin-Mac (FULL) 'In Queue: 5' (Wed Feb 3 21:35:22 2016)
Details
cont-int/LLNL/Darwin-Mac (NOGUI) 'In Queue: 5' (Wed Feb 3 21:35:22 2016)
Details
cont-int/LLNL/Linux-RH6 (MESA) 'ctest -j12 -D Exper' (Thu Feb 4 00:51:43 2016)
Details
continuous-integration/kitware-buildbot/uvcdat-garant-linux-release/ Build done.
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details

@doutriaux1 doutriaux1 deleted the issue1799_durack1_UpdateScipy0.16.1To0.17.0 branch Feb 4, 2016

@aashish24

This comment has been minimized.

Contributor

aashish24 commented Feb 4, 2016

@durack1 it would be nice if you can provide a summary of what new things we are pulling in by these new tarballs.

@durack1

This comment has been minimized.

Member

durack1 commented Feb 4, 2016

@aashish24 most of these are bugfix updates, so squash and correct little (or sometimes large in the case of numpy 1.10.0 -> 1.10.1 for e.g.) bugs and problems.. Not sure how verbose or how much duplication is required here, often the release notes detail alot of these optimisations..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment