-
Notifications
You must be signed in to change notification settings - Fork 1.1k
update to numpy-1.12.0 #830
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
Merged
Merged
Changes from 1 commit
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
update what's new to require numpy >= 1.12.0
- Loading branch information
commit 69f6da278ae0d8f4ea76dee3a59500012cb21320
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why add this new section for numpy but not include python or pandas? I'm not opposed to the section, just looking for consistency.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I was just looking for examples of a section that talked about the changes in requirements, I copied this from v0.4 requirements which was the only example I could find. I only addressed numpy because that's what's in #830.
Does v0.7 also change pandas requirments? There's already a section in bold at the top which states the Python, Pandas, and NumPy requirements, but I'm happy to repeat it down here too or just remove this section if it's redundant? I don't know what's best, so if you have a strong opinion, I happy with whatever you would like to see here. Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, they've all changed which is why they are up there in bold. But it seems that we need to do a better job of making that clear. pandas puts dependency changes like these in warning boxes. I don't know if that's overdoing it or not. Maybe something like "pandas requirement increased to" would be more clear than "pvlib now requires"?
I don't have a strong opinion other than we should be consistent within this file. And the bikeshed should be white.