Re: [Numpy-discussion] NumPy 1.15.0rc1 released
> The Python versions supported by this release are 2.7, 3.4-3.6. The wheels > are linked with > OpenBLAS 3.0, which should fix some of the linalg problems reported for NumPy > 1.14, > and the source archives were created using Cython 0.28.2 and should work with > the upcoming > Python 3.7. just checking: in Debian we're currently linking against libblas/liblapack (as available from http://www.netlib.org/lapack/) - should we start investigating switching to OpenBLAS? Thanks! -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] (no subject)
hey! On Sun, May 31, 2020 at 7:52 PM Charles R Harris wrote: > Downstream developers should use Cython >= 0.29.16 for Python 3.8 support and > OpenBLAS >= 3.7 to avoid wrong results on the Skylake architecture. The NumPy > Wheels for this release can be downloaded from PyPI, source archives and > release notes are available from Github. just so that i can re-configure (if necessary) our automation in Debian, is this going to be the future setting for releasing numpy? wheels via PyPI and source via github? I stumbled upon this since there's no source release available on PyPI for 1.19.0rc2 Thanks, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] (no subject)
> Should be fixed. indeed it is, thanks! -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] Importance of setting up SVML during build
Hello, i'm preparing 1.22.1 for inclusion in Debian, and noticed how the new numpy has a git submodule to include numpy/SVML in its source tree. We are basing the debian package on the github tarball, and that does not include any submodule, so i'm wondering how important it is to have the SVML files around when building the packages. Given it's not immediately possible to include an external set of files, i'm just trying to balance the effort to inject them and their usefulness. At the same time, i'm wondering if https://github.com/numpy/numpy/pull/20695 (the PR that introduced NPY_DISABLE_SVML, also probably https://github.com/numpy/numpy/pull/20741 for the doc) should be backported to the 1.22.x branch, so that we can start using it in the release that introduced that feature. Thanks, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi ___ 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: Importance of setting up SVML during build
> You are using the wrong tarball I believe. I just checked numpy-1.22.1.tar.gz > from our GitHub Releases page, and it does include SVML (at > numpy/core/src/umath/svml). If you instead grabbed the > autogenerated-by-github "Source code" tarball, that is the wrong one. We'd > delete it if we could, but unfortunately that is not possible. argh, you're absolutely right: i am currently using the tags tarball instead of the release one; i'll switch to that when a new release is cut. >> At the same time, i'm wondering if >> https://github.com/numpy/numpy/pull/20695 (the PR that introduced >> NPY_DISABLE_SVML, also probably >> https://github.com/numpy/numpy/pull/20741 for the doc) should be >> backported to the 1.22.x branch, so that we can start using it in the >> release that introduced that feature. > > > I followed up on this on the PR. Thanks for pointing out this issue. Thanks! ___ 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: deprecating numpy.distutils
> 4. Write a docs page with migration info on how to deal with the deprecation, > and update it before the 1.23.0 release. i think this will be extremely important. Just to give you the current POV of debian projects using numpy.distutils: - https://codesearch.debian.net/search?q=numpy.distutils+-package%3Anumpy&literal=0&perpkg=1 (there are 74 of them) - https://codesearch.debian.net/search?q=from+numpy+import+.*distutils&literal=0 (only one "from numpy import distutils") hope this could help you come up with a smooth deprecation process :) thanks, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi ___ 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
