Feature Proposal: Python API

[HeyImJordi]

Python has become somewhat of a standard for users in the area of data science and machine learning.
So far the CRG library is available as Matlab (paid and proprietary) and C source code (too low level for some users).

I propose creating a Python CRG-API by creating Python bindings to the OpenCRG C-API.
This would open up the OpenCRG library to more users and could drive engagement with the OpenCRG standard.

Priority: Low

[CarawaySeed42]

Set to Milestone 2.1.0 or LATER.

[CarawaySeed42]

To clarify, the Python API is NOT proposed to be a "native" implementation

[ExpectedArgument]

@HeyImJordi I have created an unooficial python wrapper. If you mind, you can check it out:

https://github.com/ExpectedArgument/pycrg

[CarawaySeed42]

Hi @ExpectedArgument, thank you very much for providing a potential implementation for an OpenCRG Python wrapper.
Just to clarify, the Python API issue/topic was created by me, but the original authors of older issues were lost during the transition of OpenCRG to Github.
I will gladly take a look within the next few days. Help in developing and improving OpenCRG is always appreciated.

[CarawaySeed42]

I apologize that it took more than a few days to take a look.
Your Python wrapper does go in the intended direction and it does support most of the features of the OpenCRG C-API.
As a side note, I didn't have time to test every wrapped function but everything I tested worked while I only had a few minor nitpicks.

But first and as a general question, is your intention to bring awareness, that a Python wrapper exists or is your intent to propose it as an addition to the offical OpenCRG repository in one form or another?

[ExpectedArgument]

@CarawaySeed42 Thank you for the feedback. I am glad that the wrapper aligns with openCRG C-API direction.

At first, I had to need to use CRG in python. So, I thought maybe I can create a wrapper for that.

Eventually, I bring this up to an unofficial version of the C-API as an opensource. Just for developers and who needs.

However, If you interested to integrate(merge) the wrapper into this repo, I would happily help.

[CarawaySeed42]

@ExpectedArgument It took some time to discuss but to let you know, multiple OpenCRG maintainer are interested in the Python API solution. It is still up to discuss how we will integrate and manage these external contributions and how to maintain them.
E.g. if they will be part of the standard/repository, if their existence is referenced in the specification or other.

Since the focus right now is on the release of the next OpenCRG version which will not contain these kinds of changes, I have to ask for patience because it might take some time until a plan has been established.