[Numpy-discussion] NumPy 2.0.1 released

2024-07-21 Thread Charles R Harris 
Hi All

On behalf of the NumPy team, I'm pleased to announce the release of NumPy
2.0.1. NumPy 2.0.1 is a maintenance release that fixes bugs and regressions
discovered after the 2.0.0 release. NumPy 2.0.1 is the last planned release
in the 2.0.x series, 2.1.0rc1 should be out shortly.

This release supports Python 3.9-3.12. Wheels can be downloaded from PyPI
; source archives, release notes, and
wheel hashes are available on Github
.


*Contributors*

A total of 15 people contributed to this release.  People with a "+" by
their names contributed a patch for the first time.

   - @vahidmech +
   - Alex Herbert +
   - Charles Harris
   - Giovanni Del Monte +
   - Leo Singer
   - Lysandros Nikolaou
   - Matti Picus
   - Nathan Goldbaum
   - Patrick J. Roddy +
   - Raghuveer Devulapalli
   - Ralf Gommers
   - Rostan Tabet +
   - Sebastian Berg
   - Tyler Reddy
   - Yannik Wicke +


*Pull requests merged*

A total of 24 pull requests were merged for this release.

   - #26711: MAINT: prepare 2.0.x for further development
   - #26792: TYP: fix incorrect import in ``ma/extras.pyi`` stub
   - #26793: DOC: Mention '1.25' legacy printing mode in
   ``set_printoptions``
   - #26794: DOC: Remove mention of NaN and NAN aliases from constants
   - #26821: BLD: Fix x86-simd-sort build failure on openBSD
   - #26822: BUG: Ensure output order follows input in numpy.fft
   - #26823: TYP: fix missing sys import in numeric.pyi
   - #26832: DOC: remove hack to override _add_newdocs_scalars (#26826)
   - #26835: BUG: avoid side-effect of 'include complex.h'
   - #26836: BUG: fix max_rows and chunked string/datetime reading in
   ``loadtxt``
   - #26837: BUG: fix PyArray_ImportNumPyAPI under -Werror=strict-prototypes
   - #26856: DOC: Update some documentation
   - #26868: BUG: fancy indexing copy
   - #26869: BUG: Mismatched allocation domains in
   ``PyArray_FillWithScalar``
   - #26870: BUG: Handle --f77flags and --f90flags for meson [wheel build]
   - #26887: BUG: Fix new DTypes and new string promotion when signature
   is...
   - #26888: BUG: remove numpy.f2py from excludedimports
   - #26959: BUG: Quantile closest_observation to round to nearest even
   order
   - #26960: BUG: Fix off-by-one error in amount of characters in strip
   - #26961: API: Partially revert unique with return_inverse
   - #26962: BUG,MAINT: Fix utf-8 character stripping memory access
   - #26963: BUG: Fix out-of-bound minimum offset for in1d table method
   - #26971: BUG: fix f2py tests to work with v2 API
   - #26995: BUG: Add object cast to avoid warning with limited API


Cheers,

Charles Harris
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com

[Numpy-discussion] Re: feature request: N-D Gaussian function (not random distribution)

2024-07-21 Thread Joseph Fox-Rabinovitz 
There's also an implementation in scikit-guess, which I mostly maintain.

On Sun, Jul 21, 2024, 00:38 Dom Grigonis  wrote:

> For statistics functions there is `scipy` package.
>
> If you are referring to pdf of n-dimensional gaussian distribution,
> `scipy.stats.multivariate_normal.pdf` should do the trick.
>
> If you are referring to something else, then a bit of clarification would
> be helpful.
>
> Regards,
> dg
>
> > On 20 Jul 2024, at 09:04, tomnewton...@gmail.com wrote:
> >
> > Hello,
> >
> > Apologies if either (a) this is the wrong place to post this or (b) this
> functionality already exists and I didn't manage to find it.
> >
> > I have found myself many times in the past wishing that some sort of N-D
> Gaussian function exists in NumPy. For example, when I wish to test that
> some plot or data analysis method is working correctly, being able to call
> `np.gauss()` on a (M,N) array of coordinates or passing it the arrays
> generated by a meshgrid, along with tuples for sigma and mu, would be very
> convienient.
> >
> > I could write such a function myself, but that would not be convenient
> to reuse (copying the function to every program/project I want to use it
> in), and many other mathematical functions have "convenience" functions in
> NumPy (such as the square root). More importantly, I imagine that any such
> function that was written into NumPy by the people who regularly contribute
> to the project would be far better than one I wrote myself, as I am not
> tremendously good at programming.
> >
> > Regards,
> > Tom
> > ___
> > NumPy-Discussion mailing list -- numpy-discussion@python.org
> > To unsubscribe send an email to numpy-discussion-le...@python.org
> > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
> > Member address: dom.grigo...@gmail.com
>
> ___
> NumPy-Discussion mailing list -- numpy-discussion@python.org
> To unsubscribe send an email to numpy-discussion-le...@python.org
> https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
> Member address: jfoxrabinov...@gmail.com
>
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com

[Numpy-discussion] next NumPy triage meeting - July 24th, 2024 at 6 pm UTC

2024-07-21 Thread Inessa Pawson 
The next NumPy triage meeting will be held this Wednesday, July 24th at 6
pm UTC. This is a meeting where we synchronously triage prioritized PRs and
issues.
Join us via Zoom:
https://numfocus-org.zoom.us/j/82096749952?pwd=MW9oUmtKQ1c3a2gydGk1RTdYUUVXZz09
.
Everyone is welcome to attend and contribute to a conversation.
Please notify us of issues or PRs that you’d like to have reviewed by
adding a GitHub link to them in the meeting agenda:
https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg.

-- 
Cheers,
Inessa

Inessa Pawson
GitHub: inessapawson
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com

[Numpy-discussion] Re: PR - can I get a new review?

2024-07-21 Thread Jake S. 
Hi all, it's been a couple of months, so I'm asking for a review again
 of my typing PR.  Original
reviewer requested a useful additional feature, but hasn't been able to
provide feedback since then.  The feature turned out to be problematic and
fragile without a PEP on TypeVarTuple covariance/bounds.  I've needed a
decision on whether I should (a) do the feature, leaving out difficult
tests until the feature is supported by python, and note this in the docs,
(b) remove that feature from the PR (my choice), or (c) commit to a
compromise that will be non-ideal when python *does* support the feature.

I'd like to know the path forward from someone with approval authority; I
don't want to keep troubleshooting and maintaining the PR without a way
forward.

Thanks,
Jake


Jake Stevens-Haas
Ph.D. Candidate
Applied Mathematics
University of Washington
+1-(908)-462-4196
jacob.stevens.h...@gmail.com
j...@uw.edu



On Tue, May 14, 2024 at 2:26 PM Jake S. 
wrote:

> Ah, thanks Nathan!  Most of them resolved, but one still fails (macOS
> x86-64 conda
> ).
> The spin build gives Error: 'types.SimpleNamespace' object has no
> attribute 'dir_info'; aborting.  Not sure if that relates to handling the
> gcov argument, or whether it will block the PR?
>
> - Jake
>
> Jake Stevens-Haas
> Ph.D. Candidate
> Applied Mathematics
> University of Washington
> +1-(908)-462-4196
> jacob.stevens.h...@gmail.com
> j...@uw.edu
>
>
>
> On Tue, May 7, 2024 at 11:53 AM Nathan  wrote:
>
>> I think most of the build failures you’re seeing would be fixed by
>> merging with or rebasing on the latest main branch.
>>
>> Note that there is currently an issue with some of the windows CI
>> runners, so you’ll see failures related to our spin configuration failing
>> to handle a gcov argument that was added in spin 0.9 released a couple days
>> ago.
>>
>> On Mon, May 6, 2024 at 8:48 PM Jake S. 
>> wrote:
>>
>>> Hi community,
>>>
>>> PR 26081  is about making
>>> numpy's ShapeType covariant and bound to a tuple of ints.  The community
>>> has requested this occasionally in issue 16544
>>> .  I'm reaching out via
>>> the listserv because it's been a few months, and I don't want it to get too
>>> stale.  I could really use some help pushing it over the finish line.
>>>
>>> Summary:
>>> Two numpy reviewers and one interested community member reviewed the PR
>>> and asked for a type alias akin to npt.NDArray that allowed shape.  I
>>> worked through the issues with TypeVarTuple and made npt.Array, and it was
>>> fragile, but passing CI.  After a few months passed, I returned to fix the
>>> fragility in the hopes of getting some more attention, but now it fails CI
>>> in some odd builds (passes the mypy bit).  I have no idea how to get these
>>> to pass, as they appear unrelated to anything I've worked on (OpenBLAS on
>>> windows, freeBSD...?).
>>>
>>> Thanks,
>>> Jake
>>> ___
>>> NumPy-Discussion mailing list -- numpy-discussion@python.org
>>> To unsubscribe send an email to numpy-discussion-le...@python.org
>>> https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
>>> Member address: nathan12...@gmail.com
>>>
>> ___
>> NumPy-Discussion mailing list -- numpy-discussion@python.org
>> To unsubscribe send an email to numpy-discussion-le...@python.org
>> https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
>> Member address: jacob.stevens.h...@gmail.com
>>
>
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com