Re: [Numpy-discussion] Status of NumPy and Python 3.3

2012-08-04 Thread Ondřej Čertík
On Fri, Aug 3, 2012 at 8:03 AM, Ondřej Čertík wrote: > On Mon, Jul 30, 2012 at 5:00 PM, Ronan Lamy wrote: >> Le lundi 30 juillet 2012 à 11:07 -0700, Ondřej Čertík a écrit : >>> On Mon, Jul 30, 2012 at 10:04 AM, Ronan Lamy wrote: >>> > Le lundi 30 juillet 2012 à 17:10 +0100, Ronan Lamy a écrit :

Re: [Numpy-discussion] Moving away from using accelerate framework on mac os x ?

2012-08-04 Thread Aron Ahmadia
Responding to both Dag and David, > OpenMP is pretty widespread in supercomputing, and so is OpenMP + > multiple threads using LAPACK at the same time. This does NOT sound like > any issue with multiprocessing to me. > These are built on dynamic thread-level (pthreads), not process-level (multip

Re: [Numpy-discussion] Unicode revisited

2012-08-04 Thread David Cournapeau
On Sat, Aug 4, 2012 at 12:58 PM, Stefan Krah wrote: > Nathaniel Smith wrote: >> On Sat, Aug 4, 2012 at 11:42 AM, Stefan Krah >> wrote: >> > switch (descr->byteorder) { >> > case '<': >> > byteorder = -1; >> > case '>': >> > byteorder = 1; >> >

Re: [Numpy-discussion] Moving away from using accelerate framework on mac os x ?

2012-08-04 Thread David Cournapeau
On Sat, Aug 4, 2012 at 12:14 PM, Aron Ahmadia wrote: > Hi David, > > Apple's response here is somewhat confusing, but I will add that on the > supercomputing side of things we rarely fork, as this is not well-supported > from the vendors or the hardware (it's hard enough to performantly spawn > 50

Re: [Numpy-discussion] Moving away from using accelerate framework on mac os x ?

2012-08-04 Thread Dag Sverre Seljebotn
On 08/04/2012 01:14 PM, Aron Ahmadia wrote: > Hi David, > > Apple's response here is somewhat confusing, but I will add that on the > supercomputing side of things we rarely fork, as this is not > well-supported from the vendors or the hardware (it's hard enough to > performantly spawn 500,000 proc

Re: [Numpy-discussion] Unicode revisited

2012-08-04 Thread Stefan Krah
Nathaniel Smith wrote: > On Sat, Aug 4, 2012 at 11:42 AM, Stefan Krah > wrote: > > switch (descr->byteorder) { > > case '<': > > byteorder = -1; > > case '>': > > byteorder = 1; > > default: /* '=', '|' */ > > byteorder = 0; > >

Re: [Numpy-discussion] Unicode revisited

2012-08-04 Thread Nathaniel Smith
On Sat, Aug 4, 2012 at 11:42 AM, Stefan Krah wrote: > switch (descr->byteorder) { > case '<': > byteorder = -1; > case '>': > byteorder = 1; > default: /* '=', '|' */ > byteorder = 0; > } I think you might want some break

Re: [Numpy-discussion] Moving away from using accelerate framework on mac os x ?

2012-08-04 Thread Aron Ahmadia
Hi David, Apple's response here is somewhat confusing, but I will add that on the supercomputing side of things we rarely fork, as this is not well-supported from the vendors or the hardware (it's hard enough to performantly spawn 500,000 processes statically, doing this dynamically becomes even m

[Numpy-discussion] Moving away from using accelerate framework on mac os x ?

2012-08-04 Thread David Cournapeau
Hi, During last PyCon, Olivier Grisel (from scikits-learn fame) and myself looked into a nasty bug on mac os x: https://gist.github.com/2027412. The short story is that I believe this means numpy cannot be used with multiprocessing if linked against accelerate framework, and as such we should thin

Re: [Numpy-discussion] Unicode revisited

2012-08-04 Thread Stefan Krah
Travis Oliphant wrote: > The difficulty starts when you start to interact with the unicode array > scalar (which is the same data-structure exactly as a Python unicode object > with a different type-name --- numpy.unicode_).However, I overlooked the > "encoding" argument to the standard "un