What is it?
---
PyOpenCL makes the industry-standard OpenCL compute abstraction available from
Python.
PyOpenCL has been tested to work with AMD's and Nvidia's OpenCL
implementations and allows complete access to all features of the standard,
from a nice, Pythonic interface.
Where can
On Montag 29 Dezember 2008, Robert Kern wrote:
> You could wrap the wrappers in Python and check the dtype. You'd have
> a similar bug if you passed a wrong non-object dtype, too.
> Checking/communicating the dtype is something you always have to do
> when using the 2.x buffer protocol. I'm incline
On Montag 29 Dezember 2008, Robert Kern wrote:
> On Sun, Dec 28, 2008 at 20:38, Andreas Klöckner
wrote:
> > On Montag 29 Dezember 2008, Robert Kern wrote:
> >> On Sun, Dec 28, 2008 at 19:23, Andreas Klöckner
> >>
> >
> > wrote:
> >> > Hi all,
&
On Montag 29 Dezember 2008, Robert Kern wrote:
> On Sun, Dec 28, 2008 at 19:23, Andreas Klöckner
wrote:
> > Hi all,
> >
> > I don't think PyObject pointers should be accessible via the buffer
> > interface. I'd throw an error, but maybe a (silenceable) warn
Hi all,
I don't think PyObject pointers should be accessible via the buffer interface.
I'd throw an error, but maybe a (silenceable) warning would do. Would have
saved me some bug-hunting.
>>> import numpy
>>> numpy.array([55, (33,)], dtype=object)
>>> x = numpy.array([55, (33,)], dtype=object)
On Sonntag 22 Juni 2008, Kevin Jacobs <[EMAIL PROTECTED]> wrote:
> Thanks for the clarification. That makes perfect sense. Do you have any
> feelings on the relative performance of GPUArray versus CUBLAS?
Same. If you check out the past version of PyCuda that still has CUBLAS, there
are files t
Hi all,
I am happy to announce the availability of PyCuda [1,8], which is a
value-added Python wrapper around Nvidia's CUDA [2] GPU Computation
framework. In the presence of other wrapping modules [3,4], why would you
want to use PyCuda?
* It's designed to work and interact with numpy.
* RAII
Hi all,
Is this supposed to be like that, i.e. is the fancy __setitem__ supposed to
not complain about unused assignees?
>>> v = zeros((10,))
>>> z = [1,2,5]
>>> v[z] = [1,2,4,5]
>>> v
array([ 0., 1., 2., 0., 0., 4., 0., 0., 0., 0.])
Contrast with:
>>> v[1:3] = [1,2,3,4]
Traceback (mo
On Freitag 06 Juni 2008, Thomas Hrabe wrote:
> Furthermore, I sometimes get a
> Segmentation fault
> Illegal instruction
>
> and sometimes it works
>
> It might be a memory leak, due to the segfault and the arbitrary behavior.?
Shameless plug: PyUblas [1] will take care of the nasty bits of wrappi
On Samstag 17 Mai 2008, Joe Harrington wrote:
> To head off another pedagogical meltdown, the University of Central
> Florida has hired Stefan van der Walt full time to coordinate a
> community documentation effort to write reference documentation and
> tools.
This is truly excellent news. One qu
On Sonntag 04 Mai 2008, Neal Becker wrote:
> Is it safe to compile numpy with gcc 'strict aliasing'?
It seems that numpy (and most other Python-related C code) would constantly be
casting back and forth between PyObject * and PyArrayObject * (and others).
Does strict aliasing allow that, as long
On Dienstag 29 April 2008, David Cournapeau wrote:
> Andreas Klöckner wrote:
> > Yes, obviously everything will need to be linked into one big static
> > executable blob. I am somewhat certain that distutils will be of no help
> > there, so I will need to "roll my ow
On Dienstag 29 April 2008, David Cournapeau wrote:
> Andreas Klöckner wrote:
> > Argh. -1 for a hard dependency on dlopen().
>
> There is no hard dependency on dlopen, there is a hard dependency on
> runtime loading, because well, that's the point of a plugin system. It
&g
On Dienstag 29 April 2008, Lisandro Dalcin wrote:
> Your implementation make uses of low level dlopening. Then, your are
> going to have to manage all the oddities of runtime loading in the
> different systems.
Argh. -1 for a hard dependency on dlopen(). At some point in my life, I might
be force
On Samstag 26 April 2008, Charles R Harris wrote:
> I'm working through the linalg module. There is currently variation as to
> whether or not eigenvalues/singular_values/residuals, are returned as
> arrays or as matrices. I'm leaning towards making them all matrices. What
> do you think?
IMO, the
.
Brian
On Thu, Apr 24, 2008 at 10:04 AM, Andreas Klöckner
<[EMAIL PROTECTED]> wrote:
> Hi all,
>
> numpy (1.0.4 anyway) doesn't seem to install right when it's pulled in as a
> setuptools depdency from a package. If you need an example:
>
> http://pypi.python.or
Hi all,
numpy (1.0.4 anyway) doesn't seem to install right when it's pulled in as a
setuptools depdency from a package. If you need an example:
http://pypi.python.org/pypi/PyUblas/0.92.3
This is the error message:
error: /tmp/easy_install-BhSDYE/numpy-1.0.4/temp/tmpUk0utg/LLgCtQ: No such
file
On Mittwoch 23 April 2008, Christopher Barker wrote:
> What's the status of the Boost array object? maintained? updated for
> recent numpy?
The numeric.hpp included in Boost.Python is a joke. It does not use the native
API.
PyUblas [1] fills this gap, by allowing you to use Boost.Ublas on the C+
On Mittwoch 23 April 2008, Christopher Barker wrote:
> NOTE:
> Most folks now think that the pain of writing extensions completely by
> hand is not worth it -- it's just too easy to make reference counting
> mistakes, etc. Most folks are now using one of:
>
> Cython (or Pyrex)
> SWIG
> ctypes
IMO,
On Mittwoch 23 April 2008, Albert Strasheim wrote:
> Hello,
>
> On Tue, Apr 22, 2008 at 11:38 PM, Thomas Hrabe <[EMAIL PROTECTED]> wrote:
> > I am currently developing a python module in C/C++ which is supposed to
> > access nd arrays as defined by the following command in python
>
> You might als
On Mittwoch 16 April 2008, Stéfan van der Walt wrote:
> The inclusion of those cblas routines sounds like a good idea. Could
> you describe which we need, and what would be required to get this
> done?
Suppose cblas gets included in numpy, but for some reason someone decides to
link another copy
On Freitag 11 April 2008, Robert Kern wrote:
> On Thu, Apr 10, 2008 at 10:57 PM, Charles R Harris
>
> <[EMAIL PROTECTED]> wrote:
> > Turns out it matches the matlab definition. Maybe we just need another
> > function: vandermonde
>
> -1 It's needless duplication.
Agree. Let's just live with Matlab
On Mittwoch 09 April 2008, Charles R Harris wrote:
> import numpy.linalg as la ?
Yes! :)
Andreas
signature.asc
Description: This is a digitally signed message part.
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org
Hi Chuck, all,
On Mittwoch 09 April 2008, Charles R Harris wrote:
> It would affect polyfit, where the powers correspond to the numpy
> polynomial coefficients. That can be fixed, and as far as I can determine
> that is the only numpy function that uses vander, but it might break some
> software o
On Mittwoch 26 März 2008, Charles R Harris wrote:
> The docstring is incorrect. The Vandermonde matrix produced is compatible
> with numpy polynomials that also go from high to low powers. I would have
> done it the other way round, so index matched power, but that isn't how it
> is.
Patch attache
On Montag 07 April 2008, Stéfan van der Walt wrote:
> I wouldn't exactly call 494 functions "just enough namespace clutter";
> I'd much prefer to have a clean api to work with.
Not to bicker, but...
>>> import numpy
>>> len(dir(numpy))
494
>>> numpy.__version__
'1.0.4'
>>> funcs = [s for s in di
Hi Nadav,
On Montag 07 April 2008, Nadav Horesh wrote:
> [snip]
Try something like this:
[atlas]
library_dirs = /users/kloeckner/mach/x86_64/pool/lib,/usr/lib
atlas_libs = lapack, f77blas, cblas, atlas
Andreas
signature.asc
Description: This is a digitally signed message part.
___
On Montag 07 April 2008, Robert Kern wrote:
> I would prefer not to do it at all. We've just gotten people moved
> over from Numeric; I'd hate to break their trust again.
+1.
IMO, numpy has arrived at a state where there's just enough namespace clutter
to allow most use cases to get by without i
I can answer my own question now:
1) Option --fcompiler=gnu95
2) Add the following to site.cfg
[atlas]
library_dirs = /users/kloeckner/mach/x86_64/pool/lib,/usr/lib
atlas_libs = lapack, f77blas, cblas, atlas
Andreas
On Sonntag 06 April 2008, Andreas Klöckner wrote:
> Hi all,
>
> I
Hi all,
I'm having trouble getting numpy to compile something usable on a cluster I'm
using, in particular I see
8< -
ImportError:
/users/kloeckner/mach/x86_64/pool/lib/python2.5/site-packages/numpy/linalg/lapack_lite.so:
undefined symbol: _
Hi all,
is there a particular reason why dot() and tensordot() don't have output
arguments?
Andreas
signature.asc
Description: This is a digitally signed message part.
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy
Hi all,
The docstring for vander() seems to contradict what the function does. In
particular, the columns in the vander() output seem reversed wrt its
docstring. I feel like one of the two needs to be fixed, or is there
something I'm not seeing?
This here is fresh from the Numpy examples page:
On Dienstag 25 März 2008, Nadav Horesh wrote:
> scalars are immutable objects in python. Thus the += (and alike) are "fake":
Again, thanks for the explanation. IMHO, whether or not they are fake is an
implementation detail. You shouldn't have to know Python's guts to be able to
use Numpy success
On Dienstag 25 März 2008, Travis E. Oliphant wrote:
> > Question: If it's a known trap, why not change it?
>
> It also has useful applications. Also, it can only happen at with a
> bump in version number to 1.1
I'm not trying to make the functionality go away. I'm arguing that
int_array += downc
On Montag 24 März 2008, Stéfan van der Walt wrote:
> > I think this is highly undesirable and should be fixed, or at least
> > warned about. Opinions?
>
> I know the result is surprising, but it follows logically. You have
> created two integers in memory, and now you add 0.2 and 0.1 to both --
>
Hi all,
I just got tripped up by this behavior in Numpy 1.0.4:
>>> u = numpy.array([1,3])
>>> v = numpy.array([0.2,0.1])
>>> u+=v
>>> u
array([1, 3])
>>>
I think this is highly undesirable and should be fixed, or at least warned
about. Opinions?
Andreas
signature.asc
Description: This is a
36 matches
Mail list logo
