On 1/6/10 4:58 AM, has wrote:
Though personally I'd be looking to add a proper AE API, even if only
procedural, so that users can't just run arbitrary code. But that's your
decision, not mine.
Following has's advice here, I'm trying to implement a basic API (set of
Python commands/functio
On Thu, Jan 7, 2010 at 1:22 AM, Christopher Barker
wrote:
> NOTE: cc-d to the pythonmac list from the numpy list -- this is really a
> Mac issue. It's a discussion of what/how to produce binaries of numpy
> for OS-X
>
>
> David Cournapeau wrote:
>> On Wed, Jan 6, 2010 at 9:18 AM, Christopher Barke
On Thu, Jan 7, 2010 at 1:35 AM, Christopher Barker
wrote:
> One more note:
>
> An easy improvement to the current situation with binaries is to LABEL
> THEM WELL:
>
> It's worse to have a binary you expect to work fail for you than to not
> have one available. IN the past, I think folks' have used
Christopher Barker wrote:
David Cournapeau wrote:
On Thu, Jan 7, 2010 at 1:35 AM, Christopher Barker
In the past, I think folks' have used the default
name provided by bdist_mpkg, and those are not always clear. Something like:
numpy1.4-osx10.4-python.org2.6-32bit.dmg
The 32 bits is redundan
Hi,
I would like to try out OpenCL on 10.6. When I searched for python and opencl
I thought I'd just found several mirrors of the same project but it looks like
there are at least 4(!) pyopencls.
That would be:
http://mathema.tician.de/software/pyopencl (has entry on python.org)
http://source
On 1/10/10 3:08 PM, Kevin Walzer wrote:
What's the best way to structure the command so that it can be seen from
AppleScript, i.e. run in the proper scope and not return an error?
Never mind about the scope question--I found that simply adding the
aemreceive bits and the custom function insi
