Re: Bring Pytave into core

[Juan Pablo Carbajal]

On Mon, Apr 6, 2015 at 5:48 PM, Julien Bect
<address@hidden> wrote:
> Le 06/04/2015 17:25, Mike Miller a écrit :
>>
>> On Mon, Apr 6, 2015 at 11:10:42 -0400, Jordi Gutiérrez Hermoso wrote:
>>>
>>> >I have a wild idea. I like Python, and I think Numpy and Scipy are a
>>> >great tool. Interfacing Scipy with Octave is also a good thing.
>>> >
>>> >There is oct2py that interfaces between Python and Octave, but I am
>>> >not happy with its overall pipe-based approach. Instead, I think
>>> >Pytave is doing the right thing by directly calling the Octave C++
>>> >API, but this has two disadvantages: it's difficult to build and
>>> >install, and it has gone unmaintained, so it no longer adheres to the
>>> >current API.
>>> >
>>> >I therefore propose to bring Pytave into Octave proper. This would
>>> >make Numpy an optional compile-time dependency of Octave, sort of like
>>> >Java, but it would potentially mean that anyone who installs Octave
>>> >can now do "import pytave" from Python and have two-way in-memory
>>> >communication with an Octave process.
>>> >
>>> >Naturally, this would not be for the 4.0 release, but the one after
>>> >that.
>>> >
>>> >Thoughts?
>>
>> I like Python too. Making Pytave part of Octave sounds like a decent
>> idea to me, make it better maintained and keep it working with API
>> changes, all good things. Unfamiliar with both, are there any things
>> that the oct2py approach allows that pytave doesn't?
>
>
> Sounds like an excellent idea.
>
> Not that I especially like Python, but I would love it if the programs that
> I write for Octave could become easily accessible to Python users.
>
> @++
> Julien
>
>
I support the idea too! I often communicate between Octave and Python,
but all tools out there put Octave as a slave of python. I would love
two-way communication.