@@ -79,28 +79,28 @@ fits your skills and background best when submitting your application.
Ledger-CLI does have a basic test suite, but it might turn out that using
a more "full featured" test harness is useful. The student will
investigate and discuss this possibility with the mentor. It would also
be nice if lcov or other test-coverage tool could generate reports
automatically.
While this project is of primary interest to this project, it will
require careful coordination with Ledger-CLI as an upstream, and we'll
help mentor the student in that.
4. Build a better Python interface to Ledger-CLI for use by our API.
Right now, Ledger-CLI has a rather incomplete Python interface, based on
[Boost.Python](http://www.boost.org/doc/libs/1_55_0/libs/python/doc/).
However, the right approach is probably to use
[SWIG](http://www.swig.org/) or some other similar mechanism to build a
proper Python API. Perhaps Ledger-CLI could stick with Boost.Python, but
what's there clearly needs an overhaul. The upside of using SWIG will be
that we can get APIs for other languages too.
While this project is of primary interest to this project, it will require
careful coordination with Ledger-CLI as an upstream, and we'll help mentor
the student in that.
5. Add a JSON/RESTful API to [[Hledger]]'s hledger-web app, mirroring the C++/python API.
5. Add a JSON/RESTful API to [Hledger](http://hledger.org)'s hledger-web app, mirroring the C++/python API.
This would provide an alternate, single-language implementation
useful for testing, validation and future-proofing.