| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
* added tests for vander_nd in test_polyutils to cover some of the missed branches
* added tests to polyline and vander to improve branch coverage
* added tests to test_legendre.py to improve branch coverage
|
|
|
|
|
| |
Numpydoc format says that the colon need o be omitted if there is no
type, there were also some empty Examples Sections
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
... or when the input isn't/cannot be a set. I left a few usages, e.g.
in random sampling, where "set" is reasonable as informal description of
an array as the order doesn't matter; however, for e.g. np.gradient the
order of the returned list is clearly important, so "set" is wrong.
Also some other minor doc edits noticed during the grepping: using
`shape` instead of `form` in `cov` is consistent with most other places;
the wording in `Polynomial.trim` now matches other methods on the same
class.
|
|
|
|
|
| |
Single backticks default role is reference, while here it seem to be for
verbatim. Fix it in a couple of places.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This update a coupe of references (single backticks) that actually are not to
verbatim/code (double backticks); and a couple of verbatim to reference
when they do actually exists and can be resolved in context.
I probably missed other; and stayed simple but spoted a few other
inconsistencies that I did not fix:
- some ``...`` could actually be :math:`...` but not always clear if
it would be better.
- some intervals are [``...``], other are ``[...]``
I guess they could be discussed individually; it was mostly the failing
references that bothered me.
|
|
|
|
|
|
|
|
|
|
|
| |
Polynomial printing tests implicitly depended on calling
order, causing the test suite to fail when the test ordering was
randomized with the pytest-random plugin (gh-17954).
Two factors contributed to this:
* Improper setting of class-level test config and
* Poorly designed test that overrode an inherited class
variable.
|
| |
|
|
|
| |
* Removed "from" keyword and changed "raise e" to "raise"
|
|\
| |
| | |
DOC: Fix docstring cross-referencing
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
DOC: Increase guidance and detail of np.polynomial docstring
|
| |
| |
| | |
Co-authored-by: Melissa Weber Mendonça <melissawm@gmail.com>
|
| | |
|
| | |
|
| |
| |
| |
| | |
Emphasize that the class-based interface is preferred.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* MAINT: Remove nickname from polynomial classes.
The convenience classes derived from ABCPolyBase had a nickname
attribute that was only used internally in the previous
implementation of __str__. After the overhaul of __str__ in #15666,
this attr is no longer used.
* DOC: Add release note.
Add release note to notify users of removal of the abstract
property, and highlight users that may be affected by the
change.
* DOC: fixed rST in release note
|
| | |
|
|\ \
| | |
| | | |
DOC: only single-polynomial fitting in np.polynomial.Polynomial.fit()
|
| | |
| | |
| | | |
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
| | |
| | |
| | | |
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* DOC: Fixes for 18 broken links
This, with PR #16465, should fix nearly all the remaining broken links
on the site. 4 or 5 others should be easy to fix and just
need attention from someone more knowledgeable -- will
open an issue. For release notes with dead links,
I could usually find links on archive.org for roughly contemporary
versions.
* DOC: Update to "Fixes for 18 broken links #16472"
* Obsolete links, previously commented out, now deleted:
https://github.com/numpy/numpy/pull/16472#discussion_r433928958
* Semantic markup for reference to Python class:
https://github.com/numpy/numpy/pull/16472#discussion_r433553928
* Missing :ref: in internal link:
https://github.com/numpy/numpy/pull/16472#discussion_r433554484
Not included: Resolution on using external/internal doc link in .py:
https://github.com/numpy/numpy/pull/16472#discussion_r433554824
* DOC: Add internal link for 'Fixes for 18 broken links' PR #16472
Making reference [1] an internal link in function_base.py => numpy.vectorize.html
* DOC: Redirect 2 link fixes in PR #16472
* governance.rst link reverted
* ununcs.rst `overridden` link goes where it was meant to
per https://github.com/numpy/numpy/pull/16472#pullrequestreview-424666070
|
|\ \
| | |
| | | |
ENH: Improved `__str__` for polynomials
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Add a fallback for TypeErrors that are raised when attempting
to compare arbitrary elements (e.g. strings or Python complex)
to 0 in _generate_str.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Changes the printing style of instances of the convenience classes in
the polynomial package to a more "human-readable" format.
__str__ has been modified and __format__ added to ABCPolyBase, modifying
the string representation of polynomial instances, e.g. when printed.
__repr__ and the _repr_latex method (which is used in the Jupyter
environment are unchanged.
Two print formats have been added: 'unicode' and 'ascii'. 'unicode' is
the default mode on *nix systems, and uses unicode values for numeric
subscripts and superscripts in the polynomial expression. The 'ascii'
format is the default on Windows (due to font considerations) and uses
Python-style syntax to represent powers, e.g. x**2. The default
printing style can be controlled at the package-level with the
set_default_printstyle function.
The ABCPolyBase.__str__ has also been made to respect the linewidth
printoption. Other parameters from the printoptions dictionary are not
used.
Co-Authored-By: Warren Weckesser <warren.weckesser@gmail.com>
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
|
| |/
|/| |
|
| |
| |
| | |
Add missing closing brackets, script to generate the list in the PR gh-16051.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Organizational refactoring - the tests for the polynomial _repr_latex
method were originally defined in test_classes.py. Based on the
descriptions of the various test files, it is a better fit in
test_printing.py.
Updated docstring to reflect that _repr_latex is used in Jupyter
environments, not IPython terminals (by default).
|
|/
|
|
|
| |
types (#15816)
Cleanup from the dropping of python 2
|
|
|
| |
* DOC: Refactor polynomial docs using automodule.
|
|\
| |
| | |
MAINT: Updated polynomial to use fstrings
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* TST: refactor sorter tests, use proper ragged array creation syntax
* MAINT: code never hit the exception, but would error when iterating
* MAINT: pytest.mark.parametrize did not add much, removing (from review)
* MAINT: use asanyarray and generalize (from review)
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
|
|
|
|
|
|
|
| |
Inheriting from object was necessary for Python 2 compatibility to use
new-style classes. In Python 3, this is unnecessary as there are no
old-style classes.
Dropping the object is more idiomatic Python.
|
|
|
|
|
| |
As numpy is Python 3 only, these import statements are now unnecessary
and don't alter runtime behavior.
|
|
|
|
|
|
|
|
| |
the vander2d and vander3d functions
The generalization is not exposed in the public API yet, but it could be if the need arises.
The shape / dtype conversion logic is left as is for now, even if it might be broken.
|
|
|
|
| |
These deprecations already happen inside `vanderf`, so don't need to be repeated here.
|
| |
|
| |
|
| |
|
| |
|
| |
|