From: Jon M. <jm...@re...> - 2020-10-02 22:58:05
|
On 10/1/20 11:04 PM, Hoang Huu Le wrote: > Hi Jon, > > I've done this a long time ago: > 5057f8bb4de0 tipcutils: introduce python api > > Basically, it works with Python 2. > > Regards, > Hoang Sorry, I mixed it up and thought it was Tuong. The reason I said it looked "unfinished" was all the "TODO:" lines I see in tipc.py. What are those? ///jon >> -----Original Message----- >> From: Jon Maloy <jm...@re...> >> Sent: Friday, October 2, 2020 4:56 AM >> To: tip...@li...; tipc-dek <tip...@de...>; Xin Long <luc...@gm...>; Ying Xue >> <yin...@wi...> >> Subject: tipc.py >> >> I am updating the programmer's manual, and realized that the Python API >> is missing. >> Since there are so many programmers knowing Python nowadays, but not C, >> I think it would >> be very useful to have this API in the manual, so those programmers can >> get a feeling >> for how simple it to use TIPC. >> >> Tuong started development of an API based on the libtipc C-API, but it >> seems to me it was never finished. >> However, Python does since a long time have native TIPC support, >> allegedly both in Python 2 and Pyton 3. >> I had never seen that API until now, but after some googling I came over >> the following link, that seems to contain >> that native implemenation: >> >> https://blitiri.com.ar/p/pytipc/ >> >> I wonder if anybody has the time to try this one, and verify, using the >> examples, that it really works. >> It would be embarrassing to add this to the manual if it turns out it >> doesn't work. >> >> Regards >> ///jon >> >> PS. Does anybody volunteer to be become co-maintainer of the home page >> and project page >> at SourceForge? I think we should even consider moving it to >> GitLab or GitHub. >> Since we have our own domain (tipc.io) that could easily be >> re-steered to a different >> host system. |