summaryrefslogtreecommitdiff
path: root/numpy/polynomial/laguerre.py
Commit message (Collapse)AuthorAgeFilesLines
* DOC: Add missing bracket (gh-16051)Chunlin2020-04-251-4/+4
| | | Add missing closing brackets, script to generate the list in the PR gh-16051.
* DOC: Refactor `np.polynomial` docs using `automodule` (#15662)Ross Barnowski2020-03-121-35/+52
| | | * DOC: Refactor polynomial docs using automodule.
* MAINT: Clean up, mostly unused imports.Warren Weckesser2020-01-231-1/+0
|
* MAINT: Remove unnecessary 'from __future__ import ...' statementsJon Dufresne2020-01-031-2/+0
| | | | | As numpy is Python 3 only, these import statements are now unnecessary and don't alter runtime behavior.
* MAINT: polynomial: Add an N-d vander implementation used under the hood of ↵Eric Wieser2019-09-141-2/+2
| | | | | | | | 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.
* MAINT: Replace integers in places where booleans are expectedMSeifert042019-07-011-4/+4
|
* DOC: fix some more See Also issuesRalf Gommers2019-04-141-2/+1
| | | | These ones just generated warnings, not build failures
* DOC: fix doc formatting issues exposed by numpydoc 0.9.0rc1Ralf Gommers2019-04-141-2/+2
|
* ENH: rotate companion matrix for all polynomial basesTyler Moncur2019-04-081-1/+2
|
* MAINT: Unify polynomial power functionsEric Wieser2019-03-161-18/+1
| | | | | | These power functions are all the same - the algorithm used does not care about the basis. `polypow` and `chebpow` have some optimizations in their versions, which this maintains
* DEP: polynomial: Be stricter about integral argumentsEric Wieser2019-03-161-17/+8
| | | | | | | | | | | | | | | | | | | This changes the behavior for: * The `deg` and `axis` arguments of `<type>der` * The `deg` and `axis` arguments of `<type>int` * The `deg` argument of `<type>gauss` * The `deg` argument of `<type>vander2d` * The `deg` argument of `<type>vander3d` The old behavior was: * Raise `ValueError` if the argument is a float, but not an integral one * Allow a float like `1.0` to mean `1`. This is inconsistent with most other integer-accepting APIs in numpy, which require these to be actual integers, and raise TypeError when they are not. The new behavior is: * Raise `TypeError` if the argument is a float, but not an integral one * Emit a `DeprecationWarning` if a float like `1.0` is passed, continuing to allow it its old meaning.
* MAINT: Unify polynomial fitting functionsEric Wieser2019-03-151-75/+1
| | | | | | | | | | These fitting functions are all the same - the algorithm used does not care about the basis. This was done using: * A regex find / replace on all but poly and cheb * A manual diff showing that cheb differed only by whitespace * A manual diff showing that poly differed in `deg.ndim == 1` vs `deg.ndim > 0`. Given that this function only allows `deg.ndim <= 1`, and `ndim >= 0`, these two comparison are equivalent.
* MAINT: Unify polynomial addition and subtraction functionsEric Wieser2019-03-141-19/+2
| | | | These functions are all the same - the algorithm used does not care about the basis.
* MAINT: Unify polynomial division functionsEric Wieser2019-03-121-20/+1
| | | | | | These division functions are all the same - the algorithm used does not care about the basis. Note that while chebdiv and polydiv could be implemented in terms of this function, their current implementations are more optimal and exploit the properties of a multiplication by a basis polynomial.
* MAINT: Unify polynomial valnd functionsEric Wieser2019-03-121-24/+4
| | | | No point writing the same function 12 times, when you can write it once
* MAINT: Move duplicate implementations of ABCPolyBase._fromroots into polyutilsEric Wieser2019-03-111-15/+1
| | | | | | Every implementation is the same right now, other than calling different line / mul functions. Found by LGTM.
* MAINT: Merge duplicate implementations of `*vander2d` and `*vander3d` functionsEric Wieser2019-03-021-23/+2
| | | | | | | Every implementation is the same right now, other than calling a different `*vander` function. Merging these into a single private function taking a callback results in significant deduplication. Found by LGTM.
* TST, DOC: enable refguide_checkTyler Reddy2018-12-141-15/+15
| | | | | | | | * ported the refguide_check module from SciPy for usage in NumPy docstring execution/ verification; added the refguide_check run to Azure Mac OS CI * adjusted NumPy docstrings such that refguide_check passes
* DOC: add examples and extend exisiting dos for polynomial subclassesJeffrey Yancey2018-08-261-6/+11
|
* ENH: Add support for ipython latex printing to polynomialEric Wieser2018-08-121-0/+1
| | | | | | | | | | | | | | | Choices made, and the alternatives rejected (for no particularly strong reason): 1. Show terms in ascending order, to match their internal representation * alternative: descending, to match convention 2. Shows 0 terms in gray * alternative: omit entirely * alternative: show normally to aid comparison 3. Write each term as `basis(ax + b) * alternative: write as `basis(u) ... where u = ax + b` * alternative: show the normalized polynomial In future it would perhaps make sense to expose these options to the end user
* HTTP -> HTTPS, and other linkrot fixesMike Toews2018-06-161-1/+1
|
* MAINT: Add parameter checks to polynomial integration functions.Charles Harris2017-10-261-1/+5
| | | | | | | It was not being checked that the `lbnd` and `scl` parameters were scalars as required. Closes #9901.
* DOC: Fix incorrect comments that claim 0d arrays failEric Wieser2017-10-211-2/+2
|
* DOC: Fix inline "math" directives [skip ci]Michael Seifert2017-09-121-1/+1
|
* DOC: Add whitespace after "versionadded::" directiveMichael Seifert2017-09-121-9/+9
| | | | | | so it actually displays in the docs [skip ci]
* MAINT: Use moveaxis instead of rollaxis internally (#9475)Nico Schlömer2017-08-101-5/+5
| | | | | Also add a hint to the documentation advising the use of moveaxis over rollaxis. Tests for rollaxis are left alone.
* BUG: KeyboardInterrupt is swallowed all over the placeEric Wieser2017-06-031-2/+2
| | | | Bare except is very rarely the right thing
* MAINT: Use normalize_axis_index in all python axis checkingEric Wieser2017-02-201-8/+3
| | | | | | | As a result, some exceptions change from ValueError to IndexError This also changes the exception types raised in places where normalize_axis_index is not quite appropriate
* Applied same fix as 1695458be to remaining 5 polynomial typesTom Boyd2017-02-011-1/+1
| | | | | | - Fixes documentation of polynomial types `*vander2d()` methods to give the correct last index of the pseudo-Vandermonde matrix returned expressed in terms of x and y.
* DEP: Fix escaped string characters deprecated in Python 3.6.Charles Harris2016-12-141-4/+4
| | | | | | | In Python 3.6 a number of escape sequences that were previously accepted -- for instance "\(" that was translated to "\\(" -- are deprecated. To retain the previous behavior either raw strings must be used or the backslash must be properly escaped itself.
* DOC: change version references from x.y to x.y.zPierre de Buyl2016-09-071-1/+1
|
* DOC: change Numpy to NumPy in dosctrings and commentsPierre de Buyl2016-09-061-1/+1
| | | | The strings in error messages were left untouched
* ENH: Add stacklevel to all (or almost all) our function callsSebastian Berg2016-09-021-1/+1
|
* MAINT: Refactor polynomial leastsquares fits.Charles Harris2016-01-191-21/+16
| | | | | | | * Rewrite the documentation for `deg`. * Check that the passed degrees are int and raise if not. * Do not accept `deg` arguments that do not convert as 0-D or 1-D. * Sort passed degree terms for repeatability.
* ENH: Allow specification of terms to fit in lagfitJonathan Underwood2016-01-181-5/+34
| | | | | | | | | | The argument `deg` is enhanced to allow an array_like argument to past which specifies which terms to include in the fit. The returned coef array is exapnded to have entries of 0 for all coefficients which were not included in the fit.
* MAINT: improve laguerre and legendre efficiencyalex2015-06-191-2/+1
|
* MAINT: Remove unused variables and imports in numpy/polynomial/*.py.Charles Harris2014-07-291-1/+0
| | | | Detected by pyflakes.
* STY: PEP8 fixes for files in numpy/polynomial.Charles Harris2014-07-291-59/+59
| | | | | The rather lax standards used in scipy were used to identify the needed style fixups.
* Merge pull request #4566 from juliantaylor/na-docCharles Harris2014-03-281-5/+0
|\ | | | | DOC: remove obsolete NA reference from polyfit docs
| * DOC: remove obsolete NA reference from polyfit docsJulian Taylor2014-03-281-5/+0
| |
* | DOC: Fixup documentation for new way of generating classes.Charles Harris2014-03-261-4/+30
| | | | | | | | | | | | | | | | | | | | Move the class documentation to the place of definition in the appropriate module. This allow for documenting the specific series kind along with the series specific default domains and windows Remove template placeholders from the ABCPolyBase class documention. General fixup of documentation that rendered poorly.
* | ENH, MAINT: Use an abstract base class for the polynomial classes.Charles Harris2014-03-261-3/+22
|/ | | | | | | | The new base is ABCPolyBase and is intended to replace the use of the polytemplate string. In this way the need to compile the polynomial classes on import is avoided. Closes #634. Closes #3639.
* STY: Giant comma spacing fixup.Charles Harris2013-08-181-5/+5
| | | | | | | Run the 2to3 ws_comma fixer on *.py files. Some lines are now too long and will need to be broken at some point. OTOH, some lines were already too long and need to be broken at some point. Now seems as good a time as any to do this with open PRs at a minimum.
* BUG: Campanion Matrix was scalar, not matrix for degree 1.Charles Harris2013-06-201-1/+1
| | | | | | | | The companion matrices returned by the various polynomial types was a scalar in the degree one case instead of a 2-D array. Fix that and add a test to check for that result. Closes #3459.
* 2to3: Apply `print` fixer.Charles Harris2013-04-061-1/+1
| | | | | | | Add `print_function` to all `from __future__ import ...` statements and use the python3 print function syntax everywhere. Closes #3078.
* Merge pull request #460 from endolith/regex_formattingCharles Harris2013-04-031-2/+2
|\ | | | | DOC: Formatting fixes using regex
| * DOC: Used regex to find colons missing spaces which render wrong online, ↵endolith2013-03-191-2/+2
| | | | | | | | also other spacing or formatting mistakes
* | 2to3: Use absolute imports.Charles Harris2013-03-281-4/+4
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The new import `absolute_import` is added the `from __future__ import` statement and The 2to3 `import` fixer is run to make the imports compatible. There are several things that need to be dealt with to make this work. 1) Files meant to be run as scripts run in a different environment than files imported as part of a package, and so changes to those files need to be skipped. The affected script files are: * all setup.py files * numpy/core/code_generators/generate_umath.py * numpy/core/code_generators/generate_numpy_api.py * numpy/core/code_generators/generate_ufunc_api.py 2) Some imported modules are not available as they are created during the build process and consequently 2to3 is unable to handle them correctly. Files that import those modules need a bit of extra work. The affected files are: * core/__init__.py, * core/numeric.py, * core/_internal.py, * core/arrayprint.py, * core/fromnumeric.py, * numpy/__init__.py, * lib/npyio.py, * lib/function_base.py, * fft/fftpack.py, * random/__init__.py Closes #3172
* 2to3: apply exec fixer results.Charles Harris2013-02-281-1/+1
| | | | This changes the `exec` command to the `exec` function.
* MAINT: Use a better method to detect complex arrays.Charles Harris2013-01-241-1/+1
| | | | | | | | | | Instead of if lhs.dtype.char in np.typecodes['Complex']: use if issubclass(lhs.dtype.type, np.complexfloating):
View Lorry Controller Status