On 04/09/2012 09:19 PM, Dag Sverre Seljebotn wrote:
On 04/08/2012 08:25 PM, Holger Herrlich wrote:
That all sounds like no option -- sad. Cython is no solution cause,
all I want is to leave Python Syntax in favor for strong OOP design
patterns.
I'm sorry, I'm trying and trying to make
On 04/12/2012 01:02 PM, Holger Herrlich wrote:
On 04/09/2012 09:19 PM, Dag Sverre Seljebotn wrote:
On 04/08/2012 08:25 PM, Holger Herrlich wrote:
That all sounds like no option -- sad. Cython is no solution cause,
all I want is to leave Python Syntax in favor for strong OOP design
patterns.
If you want to use C++, it's because you want to use C++ tools anyway,
right?
Some tools like autodia for class diagrams etc. Main reason to use C++
is complexity. Then ..., you get to keep the pieces. becomes too likely.
I see, world's upside down, my GUI runs wxPython. ;)
Thanks to all,
That all sounds like no option -- sad.
Cython is no solution cause, all I want is to leave Python Syntax in
favor for strong OOP design patterns.
What about ctypes?
For straight numerical work where sometimes all one needs to hand across the
python-to-C/C++/Fortran boundary is a pointer to
On 04/08/2012 08:25 PM, Holger Herrlich wrote:
That all sounds like no option -- sad.
Cython is no solution cause, all I want is to leave Python Syntax in
favor for strong OOP design patterns.
I'm sorry, I'm trying and trying to make heads and tails of this
paragraph, but I don't manage to.
On 04/03/2012 04:45 PM, srean wrote:
This makes me ask something that I always wanted to know: why is weave
not the preferred or encouraged way ?
Is it because no developer has interest in maintaining it or is it too
onerous to maintain ? I do not know enough of its internals to guess
an
On Tue, Apr 3, 2012 at 4:45 PM, srean srean.l...@gmail.com wrote:
From the sourceforge forum it
seems the new Blitz++ is quite competitive with intel fortran in SIMD
vectorization as well, which does sound attractive.
you could write Blitz++ code, and call it from Cython. That may be a
bit
I think the story is that Cython overlaps enough with Weave that Weave
doesn't get any new users or developers.
One big issue that I had with weave is that it compile on the fly. As a
result, it makes for very non-distributable software (requires a compiler
and the development headers
On Wed, Apr 4, 2012 at 12:55 PM, srean srean.l...@gmail.com wrote:
One big issue that I had with weave is that it compile on the fly. As a
result, it makes for very non-distributable software (requires a compiler
and the development headers installed), and leads to problems in the long
I do
I do not know much Cython, except for the fact that it is out there
and what it is supposed to do., but wouldnt Cython need a compiler too
?
Yes, but at build-time, not run time.
Ah! I see what you mean, or so I think. So the first time a weave
based code runs, it builds, stores the code on
Hi, I plan to migrate core classes of an application from Python to C++
using SWIG, while still the user interface being Python. I also plan to
further use NumPy's ndarrays.
The application's core classes will create the ndarrays and make
calculations. The user interface (Python) finally
On Tue, Apr 3, 2012 at 6:06 AM, Holger Herrlich
Hi, I plan to migrate core classes of an application from Python to C++
using SWIG,
if you're using SWIG, you may want the numpy.i SWIG interface files,
they can be handy.
but I probably wouldn't use SWIG, unless:
- you are already a SWIG
On 04/03/2012 12:48 PM, Chris Barker wrote:
On Tue, Apr 3, 2012 at 6:06 AM, Holger Herrlich
snip
I know of
boost.python so far.
I've never used boost.python, but it's always seemed to me to be kind
of heavy weight and not all that well maintained [1]
-- but don't take my word for it!
Excerpts from Holger Herrlich's message of Tue Apr 03 09:06:09 -0400 2012:
Hi, I plan to migrate core classes of an application from Python to C++
using SWIG, while still the user interface being Python. I also plan to
further use NumPy's ndarrays.
The application's core classes will
On 04/03/2012 12:48 PM, Chris Barker wrote:
It would be nice to have a clean C++ wrapper around ndarrays, but that
doesn't exist yet (is there a good reason for that?)
Check out:
http://code.google.com/p/numpy-boost/
Mike
___
NumPy-Discussion
This makes me ask something that I always wanted to know: why is weave
not the preferred or encouraged way ?
Is it because no developer has interest in maintaining it or is it too
onerous to maintain ? I do not know enough of its internals to guess
an answer. I think it would be fair to say that
16 matches
Mail list logo
