[GSoC] Python scripting project

[Christian Stimming]

Dear Rohan,

indeed there is a lot of code in the Scheme language. Our point of  
view is the following: As a GSoC project, you should *not* plan to  
convert any larger part of the *existing* code from Scheme to Python.  
That's just pointless because as you say it doesn't change the  
functionality. Instead, you should use python for adding *new*  
features. This is much more suited to a GSoC project with its limited  
time and scope. Our expectation is that those features which are very  
needed will get ported from Scheme to Python by somebody interested  
anyway in the long run. But the first steps for Python is to get a  
useful framework up and running, and this indeed should be your GSoC  
project. However, it is important that your project already includes a  
bunch of new visible features. I.e., you should decide on a few  
features that you would like to see in gnucash which are not yet  
available, and then work on implementing those in Python.

Best Regards,

Christian

Zitat von Rohan Kulkarni <kulkarni.rohan.p at gmail.com>:
> Regarding exporting the scripting language to python, there is a lot  
> of scripting in scheme that exporting all of it to python will be a  
> big task in itself. It won't change the functionality of gnucash a  
> lot instantly but once the scripts are in python it will then be  
> open to a large section of developers. What does the community  
> prefer at this point of time? Exporting the whole code to python or  
> start with individual parts like report generating along with adding  
> the potential features that python will facilitate over scheme, such  
> as flexible exporting/importing file formats or ease in generating  
> graphical reports.
>
> Hoping for some suggestions.
>
> Thanks,
> Rohan Kulkarni
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>