[Numpy-discussion] Re: numpy defaults to free-threaded version on conda-forge

2024-11-26 Thread george trojan via NumPy-Discussion
free-threaded. mamba --version mamba 1.5.10 conda 24.9.2 Le mar. 26 nov. 2024, à 17 h 44, Ralf Gommers a écrit : > Yes, that does look like a conda-forge issue. I think it's this one: > https://github.com/conda-forge/python-feedstock/issues/738 > > On Tue, Nov 26, 2024 at 6:06

[Numpy-discussion] numpy defaults to free-threaded version on conda-forge

2024-11-26 Thread george trojan via NumPy-Discussion
My apologies if this is a wrong venue. Is this a conda-forge problem? When I run mamba create -n foo meson-python numpy 'python>=3.13' the free-threaded python is selected: + python 3.13.0 h6355ac2_0_cp313tconda-forge Cached + numpy 2.1.3 py313hb01392b_0

[Numpy-discussion] Re: Adding bfill() to numpy.

2024-05-20 Thread george trojan
xarray has both bfill and ffill for DataArrays. The implementation useless bottleneck https://github.com/pydata/bottleneck. Le lun. 20 mai 2024, à 13 h 22, Warren Weckesser a écrit : > On Mon, May 20, 2024 at 9:06 AM Raquel Braunschweig via > NumPy-Discussion wrote: > > > > Hello everyone, > >

[Numpy-discussion] Re: Improved 2DFFT Approach

2024-03-11 Thread george trojan
I think the argument nworkers = -1 to scipy.fft.fft2 and scipy.fft.ifft2 is in the wrong places in the notebook. Le lun. 11 mars 2024, à 21 h 25, via NumPy-Discussion < numpy-discussion@python.org> a écrit : > Good afternoon, Ralf. > > We have done some of the measurements you recommended, for yo

[Numpy-discussion] Re: How is "round to N decimal places" defined for binary floating point numbers?

2023-12-28 Thread george trojan
With regard to CPython, there is a recent discussion on this topic: https://discuss.python.org/t/trying-to-understand-rounding-in-python/28014 Le jeu. 28 déc. 2023, à 21 h 43, Stefano Miccoli via NumPy-Discussion < numpy-discussion@python.org> a écrit : > I have always been puzzled about how to c

Re: [Numpy-discussion] deprecating float(x) for ndim > 0

2021-09-15 Thread george trojan
To Andrew Nelson: > In the return section for fsolve the documentation states that the return > value, `x`, is an `ndarray`. True, my bad. There is another issue with `fsolve`: it implicitly changes the argument passed to `func`. Consider def func(x): # x = float(x) if not np.isscalar(x

Re: [Numpy-discussion] deprecating float(x) for ndim > 0

2021-09-15 Thread george trojan
Responding to the post by nico.schloe...@gmail.com (I subscribe to the digest). I just wrote the following code: twb = scipy.optimize.fsolve(phi, tdb, args=(tdb, p, w, hd_tdb, hg_tdb), xtol=1e-8) tdb, p, w, hd_tdb, hg_tdb twb.shape print("wet-bulb temperature {:.5f} [deg K]".format(float(twb)))