Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Backports for 1.9.1 #5234

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 2 commits into from
Oct 26, 2014
Merged

Conversation

juliantaylor
Copy link
Contributor

backports of gh-4982 and gh-5186

WarrenWeckesser and others added 2 commits October 26, 2014 12:54
* Previous expected behavior was that the gradient is computed using central
  differences in the interior and first differences at the boundaries.

* gradient was updated in v1.9.0 so that second-order accurate calculations are
  done at the boundaries, but this breaks expected behavior with old code, so
  `edge_order` keyword (Default: 1) is added to specify whether first or second
  order calculations at the boundaries should be used.

* Since the second argument is *varargs, in order to maintain compatibility
  with old code and compatibility with python 2.6 & 2.7, **kwargs is used, and
  all kwargs that are not `edge_order` raise an error, listing the offending
  kwargs.

* Tests and documentation updated to reflect this change.

* Added `.. versionadded:: 1.9.1` to the new optional kwarg `edge_order`
  documentation, and specified supported `edge_order` kwarg values.

* Clarified documentation for `varargs`.

* Made indentation in docstring consistent with other docstring styles.

* Examples corrected
@juliantaylor
Copy link
Contributor Author

after this I'll still add the masked array fix and then create the rc1 binaries

juliantaylor added a commit that referenced this pull request Oct 26, 2014
@juliantaylor juliantaylor merged commit c6900b2 into numpy:maintenance/1.9.x Oct 26, 2014
@juliantaylor juliantaylor deleted the backports-1.9.1 branch October 26, 2014 14:15
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.

2 participants