Re: [Numpy-discussion] Copyright status of NumPy binaries on Windows/OS X
Hi Travis, the Anaconda binaries (free packages as well as the non-free addons) link against Intel MKL - not against ATLAS. Are this binaries really free redistributable as stated? The lack of numpy/scipy 64bit windows binaries with opensource blas/lapack with was one of the main reasons to start with the development of a dedicated mingw-w64 based compiler toolchain to support OpenBLAS / ATLAS based binaries on windows. Cheers, carlkl 2014-10-08 1:32 GMT+02:00 Travis Oliphant tra...@continuum.io: Hey Andrew, You can use any of the binaries from Anaconda and redistribute them as long as you cite Anaconda --- i.e. tell your users that they are using Anaconda-derived binaries. The Anaconda binaries link against ATLAS. The binaries are all at http://repo.continuum.io/pkgs/ In case you weren't aware: Another way you can build and distribute an application is to build a 'conda' meta-package which lists all the dependencies. If you add to this meta-package 1) an icon and 2) an entry-point, then your application will automatically show up in the Anaconda Launcher (see this blog-post: http://www.continuum.io/blog/new-launcher ) and anyone with the Anaconda Launcher app can install/update your package by clicking on the icon next to it. Users can also install your package with conda install or using the conda-gui. Best, -Travis On Mon, Oct 6, 2014 at 11:54 AM, Andrew Collette andrew.colle...@gmail.com wrote: Hi all, I am working with the HDF Group on a new open-source viewer program for HDF5 files, powered by NumPy, h5py, and wxPython. On Windows, since people don't typically have Python installed, we are looking to distribute the application using PyInstaller, which embeds dependencies like NumPy. Likewise for OS X (using Py2App). We would like to make sure we don't accidentally include non-open-source components... I recall there was some discussion here about using the Intel math libraries for binary releases on various platforms. Do the releases on SourceForge or PyPI use any proprietary code? We'd like to avoid building NumPy ourselves if we can avoid it. Apologies if this is explained somewhere, but I couldn't find it. Thanks! Andrew Collette ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion -- Travis Oliphant CEO Continuum Analytics, Inc. http://www.continuum.io ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Copyright status of NumPy binaries on Windows/OS X
Only on Windows does free Anaconda link against the MKL. But, you are correct, that the MKL-linked binaries can only be re-distributed if the person or entity doing the re-distribution has a valid MKL license from Intel. Microsoft has actually released their Visual Studio 2008 compiler stack so that OpenBLAS and ATLAS could be compiled on Windows for these platforms as well. I would be very interested to see conda packages for these libraries which should be pretty straightforward to build. -Travis On Wed, Oct 8, 2014 at 1:12 PM, Carl Kleffner cmkleff...@gmail.com wrote: Hi Travis, the Anaconda binaries (free packages as well as the non-free addons) link against Intel MKL - not against ATLAS. Are this binaries really free redistributable as stated? The lack of numpy/scipy 64bit windows binaries with opensource blas/lapack with was one of the main reasons to start with the development of a dedicated mingw-w64 based compiler toolchain to support OpenBLAS / ATLAS based binaries on windows. Cheers, carlkl 2014-10-08 1:32 GMT+02:00 Travis Oliphant tra...@continuum.io: Hey Andrew, You can use any of the binaries from Anaconda and redistribute them as long as you cite Anaconda --- i.e. tell your users that they are using Anaconda-derived binaries. The Anaconda binaries link against ATLAS. The binaries are all at http://repo.continuum.io/pkgs/ In case you weren't aware: Another way you can build and distribute an application is to build a 'conda' meta-package which lists all the dependencies. If you add to this meta-package 1) an icon and 2) an entry-point, then your application will automatically show up in the Anaconda Launcher (see this blog-post: http://www.continuum.io/blog/new-launcher ) and anyone with the Anaconda Launcher app can install/update your package by clicking on the icon next to it. Users can also install your package with conda install or using the conda-gui. Best, -Travis On Mon, Oct 6, 2014 at 11:54 AM, Andrew Collette andrew.colle...@gmail.com wrote: Hi all, I am working with the HDF Group on a new open-source viewer program for HDF5 files, powered by NumPy, h5py, and wxPython. On Windows, since people don't typically have Python installed, we are looking to distribute the application using PyInstaller, which embeds dependencies like NumPy. Likewise for OS X (using Py2App). We would like to make sure we don't accidentally include non-open-source components... I recall there was some discussion here about using the Intel math libraries for binary releases on various platforms. Do the releases on SourceForge or PyPI use any proprietary code? We'd like to avoid building NumPy ourselves if we can avoid it. Apologies if this is explained somewhere, but I couldn't find it. Thanks! Andrew Collette ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion -- Travis Oliphant CEO Continuum Analytics, Inc. http://www.continuum.io ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion -- Travis Oliphant CEO Continuum Analytics, Inc. http://www.continuum.io ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Copyright status of NumPy binaries on Windows/OS X
Travis Oliphant tra...@continuum.io wrote: Microsoft has actually released their Visual Studio 2008 compiler stack so that OpenBLAS and ATLAS could be compiled on Windows for these platforms as well. I would be very interested to see conda packages for these libraries which should be pretty straightforward to build. OpenBLAS does not compile with Microsoft compilers because of ATT assembly syntax. You need to use a GNU compiler and you also need to have a GNU environment. OpenBLAS is easy to build on Windows with MinGW (with gfortran) and MSYS. Carl's toolchain ensures that the binaries are compatible with the Python binaries from Python.org. Sturla ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Copyright status of NumPy binaries on Windows/OS X
Ah, yes, I hadn't realized that OpenBLAS could not be compiled with Visual Studio. Thanks for that explanation. Also, I had heard that 32bit mingw on Windows could still produce 64-bit binaries. It looks like there are OpenBLAS binaries available for Windows 32 and Windows 64 (two flavors). It should be straightforward to take those binaries and make conda (or wheel) packages out of them. A good mingw64 stack for Windows would be great and benefits many communities. On Wed, Oct 8, 2014 at 4:46 PM, Sturla Molden sturla.mol...@gmail.com wrote: Travis Oliphant tra...@continuum.io wrote: Microsoft has actually released their Visual Studio 2008 compiler stack so that OpenBLAS and ATLAS could be compiled on Windows for these platforms as well. I would be very interested to see conda packages for these libraries which should be pretty straightforward to build. OpenBLAS does not compile with Microsoft compilers because of ATT assembly syntax. You need to use a GNU compiler and you also need to have a GNU environment. OpenBLAS is easy to build on Windows with MinGW (with gfortran) and MSYS. Carl's toolchain ensures that the binaries are compatible with the Python binaries from Python.org. Sturla ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion -- Travis Oliphant CEO Continuum Analytics, Inc. http://www.continuum.io ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] Extracting individual columns in Numpy
How to extract individual columns from a numpy array? For example, consider this script import numpy as np a = np.array([[1,2,3],[4,5,6],[7,8,9]]) a[0][:] a[:][0] Now both a[:][0] and a[0][:] are outputting the same result, i.e np.array([1,2,3]). If I want to extract the array [[1],[4],[7]] then what should I do? Is it possible to add this feature? If so, which file(s) should I edit? I know C,C++ and Python programming and I am new to open-source software development. Please help me. I have attached the screenshot with this mail. Thanks Suchith.J.N ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Extracting individual columns in Numpy
On Thu, Oct 9, 2014 at 6:42 AM, suchith suchithj...@gmail.com wrote: How to extract individual columns from a numpy array? For example, consider this script import numpy as np a = np.array([[1,2,3],[4,5,6],[7,8,9]]) a[0][:] a[:][0] Now both a[:][0] and a[0][:] are outputting the same result, i.e np.array([1,2,3]). If I want to extract the array [[1],[4],[7]] then what should I do? You want a[:, 0]. I'd recommend never writing expressions like a[0], where you give just 1 index into a 2d array -- numpy interprets such a thing as equivalent to a[0, :], so you should just write a[0, :] in the first place, it'll be more explicit and less confusing. (This also explains the problem you're having: a[:] is the same as a[:, :], i.e., it just returns all of 'a'. So a[:][0] is the same as a[0]. Similarly, a[0][:] returns all of a[0].) (The one time you might want to write something that looks like a[foo], with no commas inside the [], is where 'foo' is a 2d boolean mask.) -n -- Nathaniel J. Smith Postdoctoral researcher - Informatics - University of Edinburgh http://vorpus.org ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Extracting individual columns in Numpy
import numpy as np a = np.array([[1,2,3],[4,5,6],[7,8,9]]) a[0][:] a[:][0] Now both a[:][0] and a[0][:] are outputting the same result, i.e np.array([1,2,3]). If I want to extract the array [[1],[4],[7]] then what should I do? Is it possible to add this feature? The feature is already there: a[:, 0] -- _ Dr. Andrew Nelson _ ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
