Sure, Once I go through all the related documentation of Ignite. I will get 
down to work, that should around a week.

> On 25-Jan-2017, at 2:07 AM, Denis Magda <[email protected]> wrote:
> 
> I’ve prepared tickets for Python and R clients that presently describes 
> initial job that needs to be done.
> https://issues.apache.org/jira/browse/IGNITE-4600 
> <https://issues.apache.org/jira/browse/IGNITE-4600>
> https://issues.apache.org/jira/browse/IGNITE-4605 
> <https://issues.apache.org/jira/browse/IGNITE-4605>
> 
> Both clients can be developed in parallel by many of us. There is a plenty of 
> work that can be shared. So, once you’re ready to get down to work send a 
> Python dev specific message to the dev list to initiate broader discussion 
> around it.
> 
> 
> —
> Denis
> 
>> On Jan 24, 2017, at 11:28 AM, Nikita Ivanov <[email protected]> wrote:
>> 
>> Native Python client would be awesome as it would be very useful for future
>> Python DSL for IgniteML.
>> 
>> --
>> Nikita Ivanov
>> 
>> 
>> On Tue, Jan 24, 2017 at 8:20 AM, Shashank Gandham <[email protected]
>>> wrote:
>> 
>>> I am planning to participate in GSOC 2017 and while going through
>>> 
>>> http://apache-ignite-developers.2346864.n4.nabble.
>>> com/Google-Summer-Of-Code-2017-td13180.html
>>> 
>>> I found Ignite misses a native python client. I would like to work on it.
>>> 
>>> SWIG or Ctypes can be used to access shared libraries. So right now I am
>>> going through How-to-contribute page of Ignite and at the same time
>>> understanding the functionality of Ignite. I would like to know if I can
>>> start working on it right now, so that I get better understanding of the
>>> code and also a head start related to the project.
>>> 
> 

Reply via email to