On Sun, Feb 25, 2007 at 06:44:37PM +0200, Jouni K. Seppänen wrote:
Barry Wark [EMAIL PROTECTED] writes:
Yes, I agree. I wasn't coming at so much from the goal of making Pylab
a Matlab clone (as you point out, that's silly, and misses much of the
advantage of Python), but rather from the
I'm confused about the following:
print mgrid[2.45:2.6:0.05, 0:5:1]
[[[ 2.45 2.45 2.45 2.45 2.45]
[ 2.5 2.5 2.5 2.5 2.5 ]]
[[ 0.1.2.3.4. ]
[ 0.1.2.3.4. ]]]
print mgrid[2.45:2.6:0.05]
[ 2.45 2.5 2.55]
In the first case in the first dimension
URL
---
http://mlabwrap.sourceforge.net
Description
---
Mlabwrap-1.0 is a high-level python to matlab(tm) bridge that makes calling
matlab functions from python almost as convenient as using a normal python
library. It is available under a very liberal license (BSD/MIT) and should
work
An update for those of you who did not get the chance to come to PyCon.
PyCon was very well attended this year and there were some excellent
discussions and presentations.
From PyCon I learned that Python 3000 is closer than I had previously
thought. What this means for me, is that I am
PEP: unassigned
Title: Revising the buffer protocol
Version: $Revision: $
Last-Modified: $Date: $
Author: Travis Oliphant [EMAIL PROTECTED]
Status: Draft
Type: Standards Track
Created: 28-Aug-2006
Python-Version: 3000
Abstract
This PEP proposes re-designing the buffer API (PyBufferProcs
On 2/27/07, Travis Oliphant [EMAIL PROTECTED] wrote:
PEP: unassigned
Title: Revising the buffer protocol
Version: $Revision: $
Last-Modified: $Date: $
Author: Travis Oliphant [EMAIL PROTECTED]
Status: Draft
Type: Standards Track
Created: 28-Aug-2006
Python-Version: 3000
snip
Additions to
Charles R Harris wrote:
On 2/27/07, *Travis Oliphant* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
PEP: unassigned
Title: Revising the buffer protocol
Version: $Revision: $
Last-Modified: $Date: $
Author: Travis Oliphant [EMAIL PROTECTED]
mailto:[EMAIL
I'm doing an informal survey on the use of Array Programming Languages
for teaching. If you're using NumPy in this manner I'd like to hear
from you. What subject was/is taught, academic level, results, lessons
learned, etc.
Regards,
Steve
___
On 27/02/07, Travis Oliphant [EMAIL PROTECTED] wrote:
The problem is that we aren't really specifying floating-point
standards, we are specifying float, double and long double as whatever
the compiler understands.
There are some platforms which don't follow the IEEE 754 standard.
This
Charles R Harris wrote:
The problem is that we aren't really specifying floating-point
standards, we are specifying float, double and long double as whatever
the compiler understands.
There are some platforms which don't follow the IEEE 754 standard.
This format
On 2/27/07, Travis Oliphant [EMAIL PROTECTED] wrote:
Charles R Harris wrote:
The problem is that we aren't really specifying floating-point
standards, we are specifying float, double and long double as
whatever
the compiler understands.
There are some platforms which
11 matches
Mail list logo