Adds a keyword-only dtype parameter to correlate and coerrcoef to allow
user to specify the dtype of the output.

Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>

Same intent as PR numpy#17365 -- point "Installation" links to Hugo, start
page with "What is NumPy", let Hugo page link to
"Troubleshooting ImportError".

Only attempt to pull from refs/pull/xxxx/merge when pr is still
active.

To fix CircleCI fail; missed it in the c6dc9d6 commit.

CI: Make merge ref grabbing conditional on the PR being active

DOC: Display real license on license page

* Fix some links and typos
* Use the official website

Fixes the incompatible type comparison found in numpy#17490.

This also corrects the logic to not print the heading when only private/magic methods are present.

Since we no longer support Python 3.5 and below, this code is unreachable.

As with the rest of `py3k.py`, we leave behind the aliases to prevent breaking downstream code.

`Path` can now never be none, and `PurePath` is not used and not in `__all__`.

MAINT: Cleanup compatibility code for pathlib

DOC: Fix Boolean types in C functions

MAINT: Use utf8 strings in more of datetime

ENH: Pass optimizations arguments to asv build

The various character codes are for C types, which are all
platform-dependent.

Bumps [hypothesis](https://github.com/HypothesisWorks/hypothesis) from 5.37.0 to 5.37.1.
- [Release notes](https://github.com/HypothesisWorks/hypothesis/releases)
- [Commits](HypothesisWorks/hypothesis@hypothesis-python-5.37.0...hypothesis-python-5.37.1)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bumps [pydata-sphinx-theme](https://github.com/pandas-dev/pydata-sphinx-theme) from 0.4.0 to 0.4.1.
- [Release notes](https://github.com/pandas-dev/pydata-sphinx-theme/releases)
- [Changelog](https://github.com/pandas-dev/pydata-sphinx-theme/blob/master/docs/changelog.rst)
- [Commits](pydata/pydata-sphinx-theme@v0.4.0...v0.4.1)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bumps [mypy](https://github.com/python/mypy) from 0.782 to 0.790.
- [Release notes](https://github.com/python/mypy/releases)
- [Commits](python/mypy@v0.782...v0.790)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

DOC: Add docstrings for some scalar types

….37.1

MAINT: Bump hypothesis from 5.37.0 to 5.37.1

…x-theme-0.4.1

MAINT: Bump pydata-sphinx-theme from 0.4.0 to 0.4.1

MAINT: Bump mypy from 0.782 to 0.790

Co-authored-by: Matti Picus <matti.picus@gmail.com>

  This patch also cleans up `CCompilerOpt` calls in build_ext and build_clib.

commands

replaces obsolete (no longer used anywhere AFICT check_compiler_gcc4
with some more general utilities for checking GCC version

… flags

when building the numpy.core._multiarray_umath module

This adds the extra compile args to the extension needed to work around
the bug but only in the known case where the bug is relevant.

`.. c:function::` expects its contents to be a valid C prototype, meaning the return types and arguments are all need types.

DOC: Update top links in landing page

* NEP: Initial draft for NEP 43

* NEP: Small updates to NEP 43

* Partial iteration on some content, mostly updates the calling convention

Its not quite settled, I don't quite like the `npy_intp *` as a default
"user-data" yet, but I think I may warm up to it, and I think some kind
of default like that is really very convenient.

Split out `user_data *`, since I think Marten has a point that
separating "constant" and volatile data is conceptionally easier.

* Add a bit more overview-intro at the start and refactor "bound" method section

* Small fixups based on Marten and also Hameers comments

* Revise the "promotion and dispatching" section a bit.

* Fix back-compat section and add a tiny bit of implementation

* WIP: Further updates nep 43

* Revise NEP 43 and expand on arraymethod (previously the dispatching/promotion was more fleshed out)

* Update image and make sure it is included at the right place.

* small fixups

* Update doc/neps/nep-0043-extensible-ufuncs.rst

Co-authored-by: Dave Hirschfeld <dave.hirschfeld@gmail.com>

* Fix comment which was missing the final part of sentence

* Pass through, up to "steps involved in a ufunc call"

* Review up to ArrayMethod

* Review up to ArrayMethod Specs

* Review up to loop reuse

* Review most of the remaining document

* Fix title typo

* Wording updates and minor fixups.

* Apply suggestions from code review

Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>

* Address Ross's additional comments

Co-authored-by: Dave Hirschfeld <dave.hirschfeld@gmail.com>
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>

CI: fix conditional for PR merge command

BUG: Workaround for numpy#14787 on affected platforms

DOC: Fix wrong blockquotes

…tives

DOC: Remove directives for some constants

Rather than saying 'NEP 4x', the links
in the note at the top now include the NEP titles as well.

DOC: MAINT: Add NEP 43 links to NEP 42

* Added missing overloads
* Use `DtypeLike` and `_Shapelike` where applicable
* Moved a few annotation-aliases to the top of the module

MAINT: explicit disabling `CCompilerOpt` in F2PY

DOC: Fix typos

`False_`, `True_` and `UFUNC_PYVALS_NAME`

It should be a boolean, not an integeer

DOC: Fix Boolean array indexing typo

ENH: make dtype generic over scalar type

ENH: Add annotations for three new constants

…umpy#17535)

* ENH: add function to get broadcast shape from a given set of shapes.

Add new function numpy.broadcast_shape which takes tuples
for the shapes to be broadcast against each other.
Return the broadcasted shape as a tuple.
See numpy#17217

* Perform array allocations of size 0 for provided shape tuples

Co-authored-by: Eric Wieser <wieser.eric@gmail.com>

* Test for int as input shape

Also update docstring to include both ints and tuples of ints as input

* Remove unnecessary array_function_dispatch

* Add missing set_module

* Add release notes. Add versionadded to docstring.

Also fix up docstring details.

* follow convention for trailing comma

Co-authored-by: Sebastian Berg <sebastian@sipsolutions.net>

* Change name to broadcast_shapes. Also add test case, and type hint.

* follow convention

Co-authored-by: Eric Wieser <wieser.eric@gmail.com>

* Update docstring

Co-authored-by: Eric Wieser <wieser.eric@gmail.com>

* Add reference to numpy docs on broadcasting to docstring

Also move versionadded

* Fix spelling

Co-authored-by: Warren Weckesser <warren.weckesser@gmail.com>

* Add broadcast_shapes to reference docs and add See Also sections

Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
Co-authored-by: Sebastian Berg <sebastian@sipsolutions.net>
Co-authored-by: Warren Weckesser <warren.weckesser@gmail.com>

* Removed redundant `type: ignore` messages
* Set the return precision as `Union[_NBit_co, _NBit]`
* Type the precision of `builtins.int` operations as `Any`

Mypy uses a `*` whenever an annotation or one of its parameters is based on a TypeVar.

Its added value is neglible and it unnecessarily complicates the `reveal` tests so lets just ignore them.

Note that this is done after running mypy, so it won't affect cases where `*` is used as multiplication operator.

Fixes numpygh-16354. Previously np.poly1d(z).coeffs.dtype would always
be np.float64 for zero array z, regardless of z's dtype.

Instead of causing a C stack overflow, these now raise RecursionError.

It shouldn't be possible to recurse through the string, type, or byte conversion paths; only the tuple, dict, and list paths are at risk.

Co-authored-by: Eric Wieser <wieser.eric@gmail.com>

Replaces ``PyInt_Check`` and ``PyInt_AsLong`` in a few places.

…file

 MAINT: Move the `np.core.numerictypes` annotations to their own stub file

Bumps [hypothesis](https://github.com/HypothesisWorks/hypothesis) from 5.37.1 to 5.37.3.
- [Release notes](https://github.com/HypothesisWorks/hypothesis/releases)
- [Commits](HypothesisWorks/hypothesis@hypothesis-python-5.37.1...hypothesis-python-5.37.3)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

ENH: Add annotations for `np.core._type_aliases`

….37.3

MAINT: Bump hypothesis from 5.37.1 to 5.37.3

Add wording and examples to ufuncs highlighting corresponding operators.

Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>

When relaxed strides is active (and has an effect), we recalculate
the strides to export "clean" strides in the buffer interface.
(Python and probably some other exporters expect this, i.e. NumPy
has fully switched to and embraced relaxed strides, but the buffer
interface at large probably not.)

The place where "fixing" the strides occured however meant that
when the strides are fixed, the old, cached buffer-info was not
reused when it should have been reused.

This moves the "fixing" logic so that reuse will occur.  It leaves
one issue open in that an array shaped e.g. `(1, 10)` is both
C- and F-contiguous. Thus, if it is exported as C-contiguous and
then as F-contiguous, and then *again* as C-contiguous, this will
work, but the last export will compare to the export as an F-contig
buffer and thus still leak memory.

Address numpygh-16934 (but does leave a small hole)

Exporting these multiple times alternating would previously cause
a new buffer-info to be created each time.

…trides :(

...it's rows... --> ...its rows...

DOC: Typo in lexsort docstring

`axes` can take either an integer or a 2-tuple of shape-like objects

ENH: Make `np.number` generic with respect to its precision