Jump to navigation Jump to search
update Pythonic naming and URLs
| [[Summer of Code - Getting Started#OCS | OCS package]] || Sebastian Schöps || Sebastian Schöps || Octave Forge, Numerical || Yes || Easy || Never
| [[Summer of Code - Getting Started#Using_Python_within_Octave | Pytave projectPythonic package]] || Mike Miller || Colin B. Macdonald, Abhinav Tripathi || Infrastructure || No || Medium || some in GSoC 2016
| [[Summer of Code - Getting Started#JSON_encoding.2Fdecoding | JSON encoding/decoding]] || [[User:Siko1056|Kai T. Ohlhus]] || ? || Infrastructure || Yes || Medium || Never
=== Symbolic package ===
Octave's [ Symbolic package] handles symbolic computing and other CAS tools. The main component of Symbolic is a pure m-file class "@sym" which uses the Python package [ SymPy] to do (most of) the actual computations. The package aims to expose the full functionality of SymPy while also providing a high-level of compatibility with the Matlab Symbolic Math Toolbox. The Symbolic package requires communication between Octave and Python. Recently, a GSoC2016 project successfully re-implemented this communication using the new [ Pytave tool[Pythonic|Pythonic package]].
This project proposes to go further: instead of using Pytave Pythonic only for the communication layer, we'll use it throughout the Symbolic project. For example, we might make "@sym" a subclass of "@pyobject". We also could stop using the "python_cmd" interface and use Pytave Pythonic directly from methods. The main goal was already mentioned: to expose the *full functionality* of SymPy. For example, we would allow OO-style method calls such as "f.diff(x)" instead of "diff(f, x)".
* '''Required skills'''
: OO-programming with m-files, Python, and possibly C/C++ for improving Pytave Pythonic (if needed).
* '''Difficulty'''
: easy/medium
=== Using Python within Octave ===
[ Pytave[Pythonic]] allows one to call Python functions and interact with Python objects from within Octave .m file code and from the Octave command line interface. Ideally, Pytave will Pythonic may eventually not be a separate projectpackage, but rather a core feature of Octave. This project aims to improve Pytave Pythonic with the goal of merging making the code into the core Octave code basepackage more stable, maintainable, and full-featured.
Based on a previous summer project related to PytavePythonic, this work will consist of fast-paced collaborative software development based on tackling the [https://bitbucketgitlab.orgcom/mtmiller/pytaveoctave-pythonic/issues?status=new&status=open pytave Pythonic issue list]. You would also be expected to participate in software design decisions and discussion, as well as improve documentation, doctests , and unit tests. As an example of the sorts of decision decisions being made, note that Octave indexes from 1 whereas Python typically indexes from 0; in which cases is it appropriate to make this transparent to the user?
* '''Mentors'''


Navigation menu