[Numpy-discussion] Re: welcome Andrew Nelson to the NumPy maintainers team

On Mon, Aug 21, 2023 at 10:09 PM Andrew Nelson wrote: > On Mon, 21 Aug 2023 at 18:39, Ralf Gommers wrote: > >> Hi all, >> >> On behalf of the steering council, I am very happy to announce that >> Andrew is joining the Maintainers team. Andrew has been contributing to our >> CI setup in particula

[Numpy-discussion] Re: Dealing with static local variables in Numpy

On Fri, Sep 1, 2023 at 11:11 AM Sebastian Berg wrote: > On Tue, 2023-08-29 at 08:01 +, Nicolas Holzschuch wrote: > > Hello, > > > > This is my first post to this group; I'd like to start by expressing > > my appreciation for the amazing work in developing and maintaining > > Numpy. > > > > I

[Numpy-discussion] NumPy 1.26.0rc1 released

Hi All, On behalf of the NumPy team, I'm pleased to announce the release of NumPy 1.26.0rc1. The NumPy 1.26.0 release is a continuation of the 1.25.x release cycle with the addition of Python 3.12.0 support. Python 3.12 dropped distutils, consequently supporting it required finding a replacement f

[Numpy-discussion] Re: NumPy 1.26.0rc1 released

On Wed, Sep 6, 2023 at 4:53 PM Charles R Harris wrote: > Hi All, > > On behalf of the NumPy team, I'm pleased to announce the release of NumPy > 1.26.0rc1. The NumPy 1.26.0 release is a continuation of the 1.25.x release > cycle with the addition of Python 3.12.0 support.

[Numpy-discussion] Re: Curious performance different with np.unique on arrays of characters

On Thu, Sep 14, 2023 at 11:34 AM Devulapalli, Raghuveer < raghuveer.devulapa...@intel.com> wrote: > What processor you are running this on? np.sort uses AVX-512 accelerated > sorting for np.int32, so just wondering if you that is the reason for this > difference. > > Raghuveer We also have radix

[Numpy-discussion] NumPy 1.26.0 released

Hi All, On behalf of the NumPy team, I'm pleased to announce the release of NumPy 1.26.0. The NumPy 1.26.0 release is a continuation of the 1.25.x release cycle with the addition of Python 3.12.0 support. Python 3.12 dropped distutils, consequently supporting it required finding a replacement for

[Numpy-discussion] NumPy 1.26.1 released

Hi All, On behalf of the NumPy team, I'm pleased to announce the release of NumPy 1.26.1. NumPy 1.26.1 is a maintenance release that fixes bugs and regressions discovered after the 1.26.0 release. In addition, it adds new functionality for detecting BLAS and LAPACK when building from source. Highl

[Numpy-discussion] Re: We've recevied a NumFOCUS SDG!

On Wed, Nov 8, 2023 at 4:24 PM wrote: > Hello NumPy community, > > I am thrilled to announce that I have been awarded a NumFocus Small > Development Grant for my work on NumPy-Financial. This grant will enable me > to enhance compatibility with NumPy 2.0, attract new contributors, improve > testi

[Numpy-discussion] Re: Switching default order to column-major

On Sat, Nov 11, 2023 at 8:07 AM Valerio De Benedetto wrote: > Hi, I found that the documented default row-major order is enforced > throughout the library with a series of `order='C'` default parameters, so > given this I supposed there's no way to change the default (or am I wrong?) > If, suppos

[Numpy-discussion] NumPy 1.26. 2 released

Charles R Harris Sat, Oct 14, 3:03 PM to numpy-discussion, SciPy, bcc: python-announce-list Hi All, On behalf of the NumPy team, I'm pleased to announce the release of NumPy 1.26.2. NumPy 1.26.2 is a maintenance release that fixes bugs and regressions discovered after the 1.26.1 release

[Numpy-discussion] NumPy 1.26.3 released

Hi All, On behalf of the NumPy team, I'm pleased to announce the release of NumPy 1.26.3. NumPy 1.26.3 is a maintenance release that fixes bugs and regressions discovered after the 1.26.2 release. The most notable fixes are the f2py bug fixes. The Python versions supported by this release are 3.9-

[Numpy-discussion] Re: Proposal to accept NEP 55: Add a UTF-8 variable-width string DType to NumPy

On Mon, Jan 22, 2024 at 5:14 PM Nathan wrote: > Hi all, > > I propose we accept NEP 55 and merge PR #25347 implementing the NEP in > time for the NumPy 2.0 RC: > > https://numpy.org/neps/nep-0055-string_dtype.html > https://github.com/numpy/numpy/pull/25347 > > The most controversial aspect of th

[Numpy-discussion] Re: Enhancement: Chebyshev power using DCT

On Wed, Jan 24, 2024 at 6:29 AM Fabio Matti wrote: > Hi, > > In the `numpy.polynomial.chebyshev` module, the function for raising a > Chebyshev polynomial to a power, `chebpow` [1], is essentially implemented > in the following way: > > {{{#!highlight python > def chebpow(c, pow): > """Raise

[Numpy-discussion] Re: New matvec and vecmat functions

On Tue, Jan 23, 2024 at 3:18 PM Marten van Kerkwijk wrote: > Hi All, > > I have a PR [1] that adds `np.matvec` and `np.vecmat` gufuncs for > matrix-vector and vector-matrix calculations, to add to plain > matrix-matrix multiplication with `np.matmul` and the inner vector > product with `np.vecdot

[Numpy-discussion] Re: welcome Raghuveer, Chris, Mateusz and Matt to the NumPy maintainers team

On Fri, Jan 26, 2024 at 1:08 PM Ralf Gommers wrote: > Hi all, > > We've got four new NumPy maintainers! Welcome to the team, and > congratulations to: > > - Raghuveer Devulapalli (https://github.com/r-devulap) > - Chris Sidebottom (https://github.com/mousius) > - Mateusz Sokół (https://github.com

[Numpy-discussion] Re: API: make numpy.lib._arraysetops.intersect1d work on multiple arrays #25688

On Fri, Feb 2, 2024 at 6:34 AM Stephan Kuschel via NumPy-Discussion < numpy-discussion@python.org> wrote: > All the Best > Stephan > ___ > NumPy-Discussion mailing li Dear Community, > > For my own work, I required the intersect1d function to work on mu

[Numpy-discussion] NumPy 1.26.4 released

Hi All, On behalf of the NumPy team, I'm pleased to announce the release of NumPy 1.26.4. NumPy 1.26.4 is a maintenance release that fixes bugs and regressions discovered after the 1.26.3 release. This is the last planned release in the 1.26.x series. Wheels can be downloaded from PyPI

[Numpy-discussion] numpy 2.0.x has been branched.

Hi All, Numpy 2.0.x has been branched, further work on the release notes should be made against that branch. The main branch is now 2.1.0. Chuck ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discu

[Numpy-discussion] Re: numpy 2.0.x has been branched.

On Fri, Mar 8, 2024 at 2:48 PM Oscar Benjamin wrote: > Hi Chuck, > > Is there a rough expected landing time for NumPy 2.0? > > Also does the branching mean that the intention/guarantee is not to > make further incompatible changes? > > SymPy's current master branch is compatible with the current

[Numpy-discussion] Re: numpy 2.0.x has been branched.

On Fri, Mar 8, 2024 at 4:45 PM Oscar Benjamin wrote: > On Fri, 8 Mar 2024 at 23:31, Aaron Meurer wrote: > > > > How bad are the NumPy 2.0 breakages in SymPy? We could do a backport > > release if they are serious. > > I don't remember exactly what needed changing but some basic things in > sympy

[Numpy-discussion] NumPy 2.0.0b1 released

Hi All On behalf of the NumPy team, I'm pleased to announce the release of NumPy 2.0.0b1. NumPy 2.0.0 is the first major release since 2006. It is the result of 10 months of development since the last feature release and is the work of 190 contributors spread over 968 pull requests. It contains a

[Numpy-discussion] Re: Polyfit error in displacement

On Mon, Mar 25, 2024 at 11:28 AM Luca Bertolotti < luca72.bertolo...@gmail.com> wrote: > Hello > in a vb program they use 3rd degree approx and get this value including > displacement:(SC) > [image: image.png] > > Ii think that i'm doing the same with numpy but I get different value does > anyone

[Numpy-discussion] Re: numpy 2.0.x has been branched.

On Mon, Mar 25, 2024 at 5:54 PM Oscar Benjamin wrote: > On Sat, 9 Mar 2024 at 10:16, Ralf Gommers wrote: > > > > On Sat, Mar 9, 2024 at 2:03 AM Oscar Benjamin < > oscar.j.benja...@gmail.com> wrote: > >> > >> On Sat, 9 Mar 2024 at 00:44, Charles R H

[Numpy-discussion] NumPy 2.0.0rc1 released

Hi All On behalf of the NumPy team, I'm pleased to announce the release of NumPy 2.0.0rc1. NumPy 2.0.0 is the first major release since 2006. It is the result of 10 months of development since the last feature release and is the work of 193 contributors spread over 1005 pull requests. It contains

[Numpy-discussion] Re: Moving the weekly traige/community meetings

On Sun, Apr 7, 2024 at 8:37 PM Matti Picus wrote: > Could we move the weekly community/triage meetings one hour later? Some > participants have a permanent conflict, and the current time is > inconvenient for my current time zone. > > Matti > > Works for me. Chuck ___

[Numpy-discussion] Re: Please consider dropping Python 3.9 support for Numpy 2.0

On Fri, May 10, 2024 at 8:47 AM Ralf Gommers wrote: > > > On Thu, May 9, 2024 at 12:28 AM Thomas Caswell wrote: > >> I think the spirit of NEP 29 is to pick your supported Python's when you >> pick a target release date and you should then stick to it (to avoid "we >> delayed so long we are over

[Numpy-discussion] NumPy 2.0.0rc2 released

Hi All On behalf of the NumPy team, I'm pleased to announce the release of NumPy 2.0.0rc2. NumPy 2.0.0 is the first major release since 2006. It is the result of 11 months of development since the last feature release and is the work of 198 contributors spread over 1041 pull requests. It contains

[Numpy-discussion] Re: 3.13 wheels

On Tue, May 14, 2024 at 12:24 AM Andrew Nelson wrote: > I'm not sure if we've discussed this yet. I propose we start making > nightly wheels for cp313 just after numpy2.0 gets officially released. That > way there's no churn in the wheel infra. Note that there's already a > 3.13dev job in CI. >

[Numpy-discussion] Generate documentation for the 2.0.0 release

Hi All, Could someone running Python < 3.12 generate the documentation for the NumPy 2.0.0 release. My native Python is 3.12, which works fine except that there is no distutils. Trying to run the build under 3.11, after hard coding the Python version in the doc/Makefile, runs into various problems

[Numpy-discussion] Re: Generate documentation for the 2.0.0 release

PS, you will need to check out `.spin/cmds.py` from the main branch in order to build the documentation. Chuck On Sun, Jun 16, 2024 at 9:59 AM Charles R Harris wrote: > Hi All, > > Could someone running Python < 3.12 generate the documentation for the > NumPy 2.0.0 release. My n

[Numpy-discussion] Re: Generate documentation for the 2.0.0 release

PPS, the problem can probably be solved in the spin command, I suspect it doesn't use the virtual environment everywhere it should. Chuck On Sun, Jun 16, 2024 at 10:04 AM Charles R Harris wrote: > PS, you will need to check out `.spin/cmds.py` from the main branch in > order t

[Numpy-discussion] Re: Generate documentation for the 2.0.0 release

Thanks Matti. Chuck On Sun, Jun 16, 2024 at 10:31 AM Matti Picus wrote: > I will make a PR to https://github.com/numpy/doc > > Matti > > > On 16/06/2024 19:04, Charles R Harris wrote: > > PS, you will need to check out `.spin/cmds.py` from the main branch i

[Numpy-discussion] NumPy 2.0.0 released

Hi All On behalf of the NumPy team, I'm pleased to announce the release of NumPy 2.0.0rc2. NumPy 2.0.0 is the first major release since 2006. It is the result of 11 months of development since the last feature release and is the work of 198 contributors spread over 1041 pull requests. It contains

[Numpy-discussion] NumPy 2.0.1 released

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 releas

[Numpy-discussion] Re: git status

On Sun, Aug 4, 2024 at 4:25 PM Andrew Nelson wrote: > Hi all, > for some reason my fork has got way out of date and is missing commits > from back to April. I'm not sure if my fork got messed up, or whether the > numpy repo history has been affected. > > Is anyone else experiencing problems? > I

[Numpy-discussion] Re: git status

orked repository. On Sun, Aug 4, 2024 at 9:33 PM Andrew Nelson wrote: > On Mon, 5 Aug 2024 at 10:34, Charles R Harris > wrote: > >> >> On Sun, Aug 4, 2024 at 4:25 PM Andrew Nelson wrote: >> >>> Hi all, >>> for some reason my fork has got way out of

[Numpy-discussion] Re: git status

am/* I am using ssh, which is the `git@` bit, you probably want the `https://` version. Chuck On Sun, Aug 4, 2024 at 9:38 PM Charles R Harris wrote: > What does your `.git/config` file show as the source for fetching numpy? I > just do `git pull upstream main`. I think you can also pull wi

[Numpy-discussion] NumPy 2.1.x branched, main is open for 2.2.0 development

Hi All, Just a note that the 'maintenance/2.1.x' branch has been created and the main branch is now ready for 2.2.0 development. The OpenBlas problems have not yet been resolved, hopefully that can be taken care of before the 2.1.0 release. Chuck ___ Nu

[Numpy-discussion] NumPy 2.1.0rc1 released

Hi All On behalf of the NumPy team, I'm pleased to announce the release of NumPy 2.1.0rc1. NumPy 2.1.0rc1 provides support for the upcoming Python 3.13 release and drops support for Python 3.9. In addition to the usual bug fixes and updated Python support, it helps get us back into our usual relea

[Numpy-discussion] NumPy 2.1.0 released.

Hi All On behalf of the NumPy team, I'm pleased to announce the release of NumPy 2.1.0. NumPy 2.1.0 provides support for the upcoming Python 3.13 release and drops support for Python 3.9. In addition to the usual bug fixes and updated Python support, this release helps get NumPy back into its usua

[Numpy-discussion] Documentation for the 2.0.0 release.

Hi All, Just a note that someone running a version of Python < 3.12 needs to generate the 2.1.0 release documentation. I can't do it, as Python 12 is my system Python and somewhere along the way it gets called, even when the documentation script is run with 3.11, and the build fails because Python

[Numpy-discussion] Re: Welcome Joren Hammudoglu to the NumPy Maintainers Team

On Mon, Aug 19, 2024 at 4:44 AM Sebastian Berg wrote: > Hi all, > > please join me in welcoming Joren (https://github.com/jorenham) to the > NumPy maintainers team. > > Joren has done a lot of work recently contributing, reviewing, and > maintaining typing related improvements to NumPy. > We are

[Numpy-discussion] Re: Documentation for the 2.0.0 release.

On Mon, Aug 19, 2024 at 2:30 PM matti picus wrote: > Done. Thanks for the release. > Matti > Thanks Matti. Chuck ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https:/

[Numpy-discussion] NumPy 2.0.2 released

Hi All On behalf of the NumPy team, I'm pleased to announce the release of NumPy 2.0.2. NumPy 2.0.2 is a maintenance release that fixes bugs and regressions discovered after the 2.0.1 release. This release supports Python 3.9-3.12. Wheels can be downloaded from PyPI

[Numpy-discussion] Re: Adding `P.coef_natural` property to polynomials

On Sun, Sep 1, 2024 at 6:48 AM Rakshit Singh wrote: > Best Wishes > > I am really hesitant of changing the api, some packages might be dependent > on it. > > Regards > Rakshit Kr. Singh > > On Sun, Sep 1, 2024, 5:54 PM oc-spam66--- via NumPy-Discussion < > numpy-discussion@python.org> wrote: > >>

[Numpy-discussion] What should remain on PyPi

Hi All, I just got through deleting a bunch of pre-releases on PyPi and it occurred to me that we should have a policy as to what releases should be kept. I think that reproducibility requires that we keep all the major and micro versions, but if so, we should make that an official guarantee. Perh

[Numpy-discussion] NumPy 2.1.1 release

Hi All, On behalf of the NumPy team, I'm pleased to announce the release of NumPy 2.1.1. NumPy 2.1.1 is a maintenance release that fixes bugs and regressions discovered after the 2.1.0 release. This release supports Python 3.10-3.13. Wheels can be downloaded from PyPI

[Numpy-discussion] Line lengths for Python file increased to 88 characters

Hi All, Just a heads up that the maximum line length for NumPy Python files has been increased to 88 characters , you may want to change some editor settings. This makes us compatible with Black and other auto-formatters, and seems to be the developing st

[Numpy-discussion] Re: What should remain on PyPi

On Tue, Sep 3, 2024 at 10:46 AM Sean Gillies wrote: > Hi Chuck, > > I've got a version of a package on PyPI that requires Numpy 2.0.0rc1 at > build time. Not the best decision in hindsight, but I assumed that Numpy > was the kind of project that wouldn't remove published distributions unless > th

Re: [Numpy-discussion] Fwd: SciPy2017 Sprints FinAid for sprint leaders/core devs

On Tue, Mar 28, 2017 at 5:16 PM, Nathaniel Smith wrote: > In case anyone is interested in helping run a NumPy sprint at SciPy this > year: > I haven't found numpy sprints to be very productive. However, I think it would be useful if we could have a developers meeting sometime this year. Chuck _

[Numpy-discussion] __array_ufunc__ counting down to launch, T-24 hrs.

Hi All, Just a note that the __array_ufunc__ PR is ready to merge. If you are interested, you can review here . Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman

Re: [Numpy-discussion] Fwd: [numfocus] Grants up to $3k available to NumFOCUS projects (sponsored & affiliated)

On Fri, Mar 31, 2017 at 8:07 AM, Julian Taylor < jtaylor.deb...@googlemail.com> wrote: > On 31.03.2017 15:51, Nathaniel Smith wrote: > > On Mar 31, 2017 1:15 AM, "Ralf Gommers" > > wrote: > > > > > > > > On Mon, Mar 27, 2017 at 11:42 PM, Ralf Gommers > > mai

Re: [Numpy-discussion] Fwd: SciPy2017 Sprints FinAid for sprint leaders/core devs

On Fri, Mar 31, 2017 at 12:39 AM, Ralf Gommers wrote: > > > On Fri, Mar 31, 2017 at 11:59 AM, Sebastian Berg < > sebast...@sipsolutions.net> wrote: > >> On Thu, 2017-03-30 at 22:46 +1300, Ralf Gommers wrote: >> > >> >> > >> > Agreed, and I would call that productive. Getting even one new >> > ma

[Numpy-discussion] __array_ufunc__

Hi All, After a week of review and rework, the new and improved __array_ufunc__ has turned the corner and is headed down the homestretch. Now is the time for interested parties to give it a final lookover at https://github.com/numpy/numpy/pull/8247. Chuck _

[Numpy-discussion] Long term plans for dropping Python 2.7

Hi All, It may be early to discuss dropping support for Python 2.7, but there is a disturbance in the force that suggests that it might be worth looking forward to the year 2020 when Python itself will drop support for 2.7. There is also a website, http://www.python3statement.org, where several pr

Re: [Numpy-discussion] Long term plans for dropping Python 2.7

On Fri, Apr 14, 2017 at 11:47 PM, Ralf Gommers wrote: > > > On Sat, Apr 15, 2017 at 5:19 PM, Nathaniel Smith wrote: > >> On Fri, Apr 14, 2017 at 5:19 PM, Charles R Harris >> wrote: >> > Hi All, >> > >> > It may be early to discuss

[Numpy-discussion] Relaxed stride checking fixup

Hi All, Currently numpy master has a bogus stride that will cause an error when downstream projects misuse it. That is done in order to help smoke out errors. Previously that bogus stride has been fixed up for releases, but that requires a special patch to be applied after each version branch is m

Re: [Numpy-discussion] Relaxed stride checking fixup

On Thu, Apr 20, 2017 at 4:21 AM, Ralf Gommers wrote: > > > On Thu, Apr 20, 2017 at 6:28 AM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> Hi All, >> >> Currently numpy master has a bogus stride that will cause an error when >> downstream

Re: [Numpy-discussion] proposal: smaller representation of string arrays

On Thu, Apr 20, 2017 at 12:53 PM, Robert Kern wrote: > On Thu, Apr 20, 2017 at 6:15 AM, Julian Taylor < > jtaylor.deb...@googlemail.com> wrote: > > > Do you have comments on how to go forward, in particular in regards to > > new dtype vs modify np.unicode? > > Can we restate the use cases explici

[Numpy-discussion] __array_ufunc__ final review

Hi All, The __array_ufunc__ PR is ready for final review. If there are no complaints, I plan to put it in tomorrow. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/ma

Re: [Numpy-discussion] proposal: smaller representation of string arrays

On Tue, Apr 25, 2017 at 11:34 AM, Anne Archibald wrote: > > On Tue, Apr 25, 2017 at 7:09 PM Robert Kern wrote: > >> * HDF5 supports fixed-length and variable-length string arrays encoded in >> ASCII and UTF-8. In all cases, these strings are NULL-terminated (despite >> the documentation claiming

Re: [Numpy-discussion] proposal: smaller representation of string arrays

On Tue, Apr 25, 2017 at 12:52 PM, Robert Kern wrote: > On Tue, Apr 25, 2017 at 11:18 AM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > > > > On Tue, Apr 25, 2017 at 11:34 AM, Anne Archibald < > peridot.face...@gmail.com> wrote: > > >> C

Re: [Numpy-discussion] proposal: smaller representation of string arrays

On Tue, Apr 25, 2017 at 1:30 PM, Charles R Harris wrote: > > > On Tue, Apr 25, 2017 at 12:52 PM, Robert Kern > wrote: > >> On Tue, Apr 25, 2017 at 11:18 AM, Charles R Harris < >> charlesr.har...@gmail.com> wrote: >> > >> > On Tue, Apr 25,

Re: [Numpy-discussion] proposal: smaller representation of string arrays

On Tue, Apr 25, 2017 at 5:50 PM, Robert Kern wrote: > On Tue, Apr 25, 2017 at 3:47 PM, Chris Barker - NOAA Federal < > chris.bar...@noaa.gov> wrote: > > >> Presumably you're getting byte strings (with unknown encoding. > > > > No -- thus is for creating and using mostly ascii string data with >

Re: [Numpy-discussion] proposal: smaller representation of string arrays

On Wed, Apr 26, 2017 at 3:15 AM, Julian Taylor < jtaylor.deb...@googlemail.com> wrote: > On 26.04.2017 03:55, josef.p...@gmail.com wrote: > > On Tue, Apr 25, 2017 at 9:27 PM, Charles R Harris > > wrote: > >> > >> > >> On Tue, Apr 25, 2017 at 5:50 P

[Numpy-discussion] Ready to branch 1.13

Hi All, I am getting ready to branch 1.13 after updating the release notes and .mailmap. If there is something that you think is essential to get into 1.13 that is not there, comment. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@python.org h

[Numpy-discussion] Numpy 1.13.x branched

Hi All, Just a quck note that 1.13.x has been branched and master is open for 1.14.0 development. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] NumPy v1.13.0rc1 released.

Hi All, I'm please to announce the NumPy 1.13.0rc1 release. This release supports Python 2.7 and 3.4-3.6 and contains many new features. It is one of the most ambitious releases in the last several years. Some of the highlights and new functions are *Highlights* - Operations like ``a + b + c`

Re: [Numpy-discussion] UC Berkeley hiring developers to work on NumPy

On Sat, May 13, 2017 at 11:45 PM, Nathaniel Smith wrote: > Hi all, > > As some of you know, I've been working for... quite some time now to > try to secure funding for NumPy. So I'm excited that I can now > officially announce that BIDS [1] is planning to hire several folks > specifically to work

[Numpy-discussion] NumPy 1.13.0rc2 released

Hi All, I'm pleased to announce the NumPy 1.13.0rc2 release. This release supports Python 2.7 and 3.4-3.6 and contains many new features. It is one of the most ambitious releases in the last several years. Some of the highlights and new functions are *Highlights* - Operations like ``a + b + c

[Numpy-discussion] SciPy 2017 attendence

Hi All, Just curious as to who may be attending SciPy 2017. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] Future of ufuncs

Hi All, This post is to open a discussion of the future of ufuncs. There are two contradictory ideas that have floated about regarding ufuncs evolution. One is to generalize ufuncs to operate on buffers, essentially separating them from their current entanglement with ndarrays. The other is to acc

Re: [Numpy-discussion] Future of ufuncs

On Mon, May 29, 2017 at 12:32 PM, Marten van Kerkwijk < m.h.vankerkw...@gmail.com> wrote: > Hi Chuck, > > Like Sebastian, I wonder a little about what level you are talking > about. Presumably, it is the actual implementation of the ufunc? I.e., > this is not about the upper logic that decides whi

[Numpy-discussion] NumPy 1.13.0 release

Hi All, On behalf of the NumPy team, I amn pleased to announce the NumPy 1.13.0 release. This release supports Python 2.7 and 3.4-3.6 and contains many new features. It is one of the most ambitious releases in the last several years. Some of the highlights and new functions are *Highlights* -

[Numpy-discussion] Add changelogs to repo

Hi All, I've made a PR adding the NumPy `1.13.0-changelog.rst` to a new `doc/changelog` directory. The idea is to keep the lengthy changelogs separate from the release notes, but still easily accessible and permanently part to the NumPy history. If you hi

Re: [Numpy-discussion] np.diff on boolean arrays now raises

On Thu, Jun 15, 2017 at 4:35 AM, Ralf Gommers wrote: > > > On Thu, Jun 15, 2017 at 7:08 PM, Jaime Fernández del Río < > jaime.f...@gmail.com> wrote: > >> There is an ongoing discussion on github: >> >> https://github.com/numpy/numpy/issues/9251 >> >> In 1.13 np.diff has started raising on boolean

Re: [Numpy-discussion] np.diff on boolean arrays now raises

On Thu, Jun 15, 2017 at 6:16 AM, Charles R Harris wrote: > > > On Thu, Jun 15, 2017 at 4:35 AM, Ralf Gommers > wrote: > >> >> >> On Thu, Jun 15, 2017 at 7:08 PM, Jaime Fernández del Río < >> jaime.f...@gmail.com> wrote: >> >>> There is

[Numpy-discussion] Boolean binary '-' operator

Hi All, The boolean binary '-' operator was deprecated back in NumPy 1.9 and changed to an error in 1.13. This caused a number of failures in downstream projects. The choices now are to continue the deprecation for another couple of releases, or simply give up on the change. For booleans, `a - b`

Re: [Numpy-discussion] Boolean binary '-' operator

ng as foundational as NumPy, in > version 1.x, to follow semantic versioning and not break APIs until 2.x. > > Juan. > > On 27 Jun 2017, 9:25 AM +1000, Nathaniel Smith , wrote: > > On Sun, Jun 25, 2017 at 9:45 AM, Stefan van der Walt > wrote: > > Hi Chuck > &g

[Numpy-discussion] Scipy 2017 NumPy sprint

Hi All, I will be running the NumPy sprint at Scipy 2017 and I'm trying to put together a suitable list of things to sprint on. In my experience, sprinting on NumPy is hard, enhancements generally need lengthy review and even finding and doing simple bug fixes can take time. What I have in mind at

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

On Thu, Jun 29, 2017 at 12:07 PM, Charles R Harris < charlesr.har...@gmail.com> wrote: > Hi All, > > I will be running the NumPy sprint at Scipy 2017 and I'm trying to put > together a suitable list of things to sprint on. In my experience, > sprinting on NumPy is ha

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

On Thu, Jun 29, 2017 at 12:15 PM, Stefan van der Walt wrote: > On Thu, Jun 29, 2017, at 11:09, Charles R Harris wrote: > > > On Thu, Jun 29, 2017 at 12:07 PM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > > I will be running the NumPy sprint at Scipy

[Numpy-discussion] Vector stacks

Hi All, The '@' operator works well with stacks of matrices, but not with stacks of vectors. Given the recent addition of '__array_ufunc__', and the intent to make `__matmul__` use a ufunc, I've been wondering is it would make sense to add ndarray subclasses 'rvec' and 'cvec' that would override

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

gt; Ben Root > > > On Sat, Jul 1, 2017 at 7:12 AM, Ralf Gommers > wrote: > >> >> >> On Fri, Jun 30, 2017 at 6:50 AM, Pauli Virtanen wrote: >> >>> Charles R Harris kirjoitti 29.06.2017 klo 20:45: >>> > Here's a random idea: how

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

On Sun, Jul 2, 2017 at 9:33 AM, Sebastian Berg wrote: > On Sun, 2017-07-02 at 10:49 -0400, Allan Haldane wrote: > > On 07/02/2017 10:03 AM, Charles R Harris wrote: > > > Updated list below. > > > > > > On Sat, Jul 1, 2017 at 7:08 PM, Benjamin Root > >

Re: [Numpy-discussion] New python/numpy user

On Tue, Jul 4, 2017 at 1:32 AM, wrote: > Hi Brian > > > First of all thanks for the answer, the explanations and the advices; as > mentioned I've to think differently in order to code with efficiency. > > 1.: yes 'mat[:,0]=vect0' works fine and I understand why :-) > > 2. more generally, I've rea

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

Lots of good ideas here. It would help if issues were opened for them and flagged with the sprint label. I'll be doing some myself, but I'm not as intimately familiar with some of the topics as the proposers are. Chuck ___ NumPy-Discussion mailing list

[Numpy-discussion] Making a 1.13.2 release

Hi All, I've delayed the NumPy 1.13.2 release hoping for Python 3.6.2 to show up fixing #29943 so we can close #9272 , but the Python release has been delayed to July 11 (expected). The Python problem means that NumP

Re: [Numpy-discussion] Making a 1.13.2 release

On Thu, Jul 6, 2017 at 7:15 AM, Matthew Brett wrote: > Hi, > > On Thu, Jul 6, 2017 at 2:10 PM, Charles R Harris > wrote: > > Hi All, > > > > I've delayed the NumPy 1.13.2 release hoping for Python 3.6.2 to show up > > fixing #29943 so we can clo

Re: [Numpy-discussion] Making a 1.13.2 release

On Thu, Jul 6, 2017 at 9:53 AM, Matthew Brett wrote: > On Thu, Jul 6, 2017 at 3:37 PM, Charles R Harris > wrote: > > > > > > On Thu, Jul 6, 2017 at 7:15 AM, Matthew Brett > > wrote: > >> > >> Hi, > >> > >> On Thu, J

[Numpy-discussion] NumPy 1.13.1 released

Hi All, On behalf of the NumPy team, I am pleased to announce the release of NumPy 1.13.1. This is a bugfix release for problems found in 1.13.0. The major changes are: - fixes for the new memory overlap detection, - fixes for the new temporary elision capability, - reversion of the rem

[Numpy-discussion] pytest and degrees of separation.

Hi All, Just looking for opinions and feedback on the need to keep NumPy from having a hard nose/pytest dependency. The options as I see them are: 1. pytest is never imported until the tests are run -- current practice with nose 2. pytest is never imported unless the testfiles are impor

Re: [Numpy-discussion] pytest and degrees of separation.

On Wed, Jul 12, 2017 at 1:26 AM, Ralf Gommers wrote: > > > On Wed, Jul 12, 2017 at 11:06 AM, Chris Barker > wrote: > >> >> >> On Tue, Jul 11, 2017 at 5:04 PM, Thomas Caswell >> wrote: >> >>> Going with option 2 is probably the best option so that you can use >>> pytest fixtures and parameteriza

Re: [Numpy-discussion] quantile() or percentile()

On Thu, Aug 10, 2017 at 3:08 PM, Eric Wieser wrote: > Let’s try and keep this on topic - most replies to this message has been > about #9211, which is an orthogonal issue. > > There are two main questions here: > >1. Would the community prefer to use np.quantile(x, 0.25) instead of > np.perc

Re: [Numpy-discussion] Tensor Contraction (HPTT) and Tensor Transposition (TCL)

On Tue, Aug 15, 2017 at 10:26 AM, Paul wrote: > Hi all, > > I recently spent some time adding python interfaces to my tensor libraries: > * Tensor Contraction Library (TCL): https://github.com/springer13/tcl > * Tensor Transposition Library (HPTT): https://github.com/springer13/ > hptt > > Bo

Re: [Numpy-discussion] Tensor Contraction (HPTT) and Tensor Transposition (TCL)

On Thu, Aug 17, 2017 at 10:15 AM, Chris Barker wrote: > On Thu, Aug 17, 2017 at 12:55 AM, Sebastian Berg < > sebast...@sipsolutions.net> wrote: > >> > How would the process look like if NumPY is distributed as a >> > precompiled binary? >> >> >> Well, numpy is BSD, and the official binaries will

Re: [Numpy-discussion] NumPy default citation

On Tue, Sep 5, 2017 at 12:36 PM, Stefan van der Walt wrote: > Hi, everyone > > I see that the NumPy homepage does not have a "Citation" section. > Furthermore, on scipy.org, the default NumPy citation points to a short > summary paper that I wrote with Gael V & Stephen C. While it's a > reasonab

[Numpy-discussion] New distribution

Hi All, This is a heads up that there is a pull request adding a univariate complex_normal distribution. Anyone interested in this should take a look at the PR. I'd also be interested if there was

Re: [Numpy-discussion] ANN: SciPy 1.0 beta release

On Sun, Sep 17, 2017 at 4:48 AM, Ralf Gommers wrote: > Hi all, > > I'm excited to be able to announce the availability of the first beta > release of Scipy 1.0. This is a big release, and a version number that > has been 16 years in the making. It contains a few more deprecations and > backwards

[Numpy-discussion] NumPy 1.13.2 released.

HI All, On behalf of the NumPy team, I am pleased to annouce the release of Numpy 1.13.2. This is a bugfix release for some problems found since 1.13.1. The most important fixes are for CVE-2017-12852 and temporary elision. Users of earlier versions of 1.13 should upgrade. The Python versions sup

  1   2   3   4   5   6   >