On Sun, Aug 15, 2010 at 5:53 PM, wrote:
> On Sun, Aug 15, 2010 at 4:27 PM, Sturla Molden wrote:
>>
>>> Matlab also takes a copy if we create an array slice. It means for example
>>> that a wavelet transform written in Python will be O(n) with respect to
>>> memory, whereas it will be O(n log n)
On Sun, Aug 15, 2010 at 4:27 PM, Sturla Molden wrote:
>
>> Matlab also takes a copy if we create an array slice. It means for example
>> that a wavelet transform written in Python will be O(n) with respect to
>> memory, whereas it will be O(n log n) in Matlab.
>
> Other examples:
>
> A reshape wil
Hi everyone,
I've been pretty happy with how Spider went along when I tried it. I use
Emacs but I think Spyder is perfectly usable for someone used to Matlab. A
few HPC-centric of my reasons (I've shamelessly copy-pasted this because
I'm lazy right now):
1. Python is an expressive, full-fledged,
> Matlab also takes a copy if we create an array slice. It means for example
> that a wavelet transform written in Python will be O(n) with respect to
> memory, whereas it will be O(n log n) in Matlab.
Other examples:
A reshape will create a new array in Matlab. It will create a view in NumPy.
> It's not fully pass-by-value, a copy is only made if the matrix/array
> is changed, but not if only accessed for getting the data. And from
> the comments I have seen they keep improving lazy copying.
Yes it is copy-on-write. But that means we must restrict ourselves to
read-only access.
It al
On Sun, Aug 15, 2010 at 1:43 PM, Sturla Molden wrote:
>
>> Could those contributing here put up a Cookbook page of "reasons why
>> we've moved on from MATLAB", to be used as a resource by people trying
>> to convince supervisors/professors/sponsors/clients that they should
>> be allowed to use Pyt
[scipy/python vs. matlab discussion elided]
To all potential future contributors to this thread:
At the risk of adding noise, I'd like to suggest that if
you're going to create an extended discussion thread (even
if it is a worthwhile hijack, as this one is, I think),
at least change its name to
On Sun, Aug 15, 2010 at 1:43 PM, Sturla Molden wrote:
>
>> Could those contributing here put up a Cookbook page of "reasons why
>> we've moved on from MATLAB", to be used as a resource by people trying
>> to convince supervisors/professors/sponsors/clients that they should
>> be allowed to use Pyt
> Could those contributing here put up a Cookbook page of "reasons why
> we've moved on from MATLAB", to be used as a resource by people trying
> to convince supervisors/professors/sponsors/clients that they should
> be allowed to use Python?
There are many reasons, to name a few:
1. Ease of pro
While this thread is super off-topic (and long enough that I'm not
going to quote it), I'm actually finding it very interesting, as a
non-MATLAB person, to find out what I need to say to the MATLAB mafia
here to demonstrate that MATLAB has sufficient flaws and non-followers
"out in the real world"
Den 15. aug. 2010 kl. 04.34 skrev Gary Pajer :
Similar situation here. Been Matlab-free for about ten years, but
my new employer ...
Embed Python in a MEX an tell your employer you do MEX development.
Works like a charm ;-)
Or use Matlab's COM integration to run pywin32 as an ActiveX
11 matches
Mail list logo
