Re: Re: Bits about Intel MKL packaging -- Higher Priority than OpenBLAS

On Fri, May 18, 2018 at 11:49:05PM +0800, Drew Parsons wrote: > > I wonder if the simplest solution is to just have > intel-mkl Depends: libblas. i.e. use policy to simply prevent a sole > mkl installation. > > That way, the mkl alternative will always have a free BLAS to press > it's

Re: Re: Bits about Intel MKL packaging -- Higher Priority than OpenBLAS

On Sat, 2018-05-19 at 10:55 +, Lumin wrote: > On Fri, May 18, 2018 at 11:49:05PM +0800, Drew Parsons wrote: > > > > I wonder if the simplest solution is to just have > > intel-mkl Depends: libblas. i.e. use policy to simply prevent a > > sole > > mkl installation. > > > > That way, the

Re: Bug#899159: Acknowledgement ([numpy/grave] Incorrect Memory offset in numpy.uint8 arrays)

Sorry, I made a stupid mistake. uint8 ranges from 0 to 255. signature.asc Description: PGP signature

Bug#899159: [numpy/grave] Incorrect Memory offset in numpy.uint8 arrays

Package: python3-numpy Version: 1:1.14.3-2 Severity: grave X-Debbugs-CC: debian-science@lists.debian.org Dear Numpy maintainers, As a student/researcher, I cannot bear any library that *SILENTLY* produces totally wrong result. This time numpy just triggered me, and I wish you can understand that