User:Ozzy: Difference between revisions
Jump to navigation
Jump to search
m (→Y: Your task) |
(→Y: Your task: - changed proposal to Symbolic) |
||
Line 77: | Line 77: | ||
== Y: Your task == | == Y: Your task == | ||
* Did you select a task from our list of proposals and ideas? | * Did you select a task from our list of proposals and ideas? | ||
** If yes, what task did you choose? Please describe what part of it you especially want to focus on if you can already provide this information. ''Please also wiki-link the page for your elaborated proposal here.'' | ** If yes, what task did you choose? Please describe what part of it you especially want to focus on if you can already provide this information. ''Please also wiki-link the page for your elaborated proposal here.'' | ||
** If you apply for a task you have added yourself instead, please describe this task, its scope and people you already talked to concerning it. What field of tasks did you miss on the list? | ** If you apply for a task you have added yourself instead, please describe this task, its scope and people you already talked to concerning it. What field of tasks did you miss on the list? | ||
I would like to work on solving the problem described [[Summer_of_Code_Project_Ideas#Symbolic_package|here]]. Because the recent discussion on the octave-maintainers mailing list suggests it would be better to prepare a general method for liking Octave to Python and than apply this to this specific issue I would follow this way. | |||
As already mentioned in the discussion there already exist a library intended for this purpose, namely Pytave. The library was intended to be used to calling Octave code from Python code, but as suggested its code base can potentially serve for two-way communication, especially because it already contains all the required conversions between Python and Octave types. | |||
My project would consist of three main parts: | |||
* Cleaning up the Pytave library. This would include extracting the conversion functions between octave types and Python types (numpy arrays + primitive types), possibly leaving out legacy Python numeric types. This part would have to also include some C interface for both Octave and Python functions with proper exception mapping. | |||
* Writing an Octave module which would allow to call Python functions from Octave. This part would be realized as oct-files linking to the code prepared in the previous step (probably as a part of Pytave). This part would also have to include some Python session management. As a stand alone package it could be become a useful thing by itself. | |||
* Substituting present way of communication between Octave and Python in Symbolic Package. Since now everything is said to be done on strings, substituting current pipe approach to the one resulting from the previous step shouldn't cause much too trouble. | |||
* | |||
[[Category: Summer of Code]] | [[Category: Summer of Code]] |