14
edits
(→GSoC 2016 Symbolic Project Improvements: new section) |
|||
Line 56: | Line 56: | ||
Here is the plan (work in progress...)- | Here is the plan (work in progress...)- | ||
. | . | ||
* 2016 GSoC Plan | * 2016 GSoC Plan | ||
* References | |||
http://wiki.octave.org/Python_interface | http://wiki.octave.org/Python_interface | ||
* Outline | |||
Currently, Symbolic and PyTave each have their own mechanisms to convert objects into Octave types. As first stepo, we would put @sym creation login into PyTave and remove all the conversion login from Symbolic. Then we will target having the same via some m-file callback to have a more generalised conversion for objects. | Currently, Symbolic and PyTave each have their own mechanisms to convert objects into Octave types. As first stepo, we would put @sym creation login into PyTave and remove all the conversion login from Symbolic. Then we will target having the same via some m-file callback to have a more generalised conversion for objects. | ||
Line 73: | Line 73: | ||
https://savannah.gnu.org/bugs/?43036 | https://savannah.gnu.org/bugs/?43036 | ||
* Midterm Goals | |||
1a) Octave, Symbolic, and PyTave dev versions installed. | 1a) Octave, Symbolic, and PyTave dev versions installed. | ||
Line 91: | Line 91: | ||
* Time-line | * Time-line | ||
edits