<html><head></head><body bgcolor="#FFFFFF"><div><br><font class="Apple-style-span" color="#000000"><a href="x-apple-data-detectors://0" x-apple-data-detectors="true" x-apple-data-detectors-result="0">05.10.2012, в 2:51</a>, Antoni Segura Puimedon <<a href="mailto:asegurap@redhat.com" x-apple-data-detectors="true" x-apple-data-detectors-result="1">asegurap@redhat.com</a>> написал(а):<br><span></span><br></font><blockquote type="cite"><font class="Apple-style-span" color="#000000"><span>Hello Марк,</span><br></font></blockquote><blockquote type="cite"><font class="Apple-style-span" color="#000000"><span></span><br></font></blockquote><blockquote type="cite"><font class="Apple-style-span" color="#000000"><span>I was today discussing with Thomas Graf the python bindings of libnl and he</span><br></font></blockquote><blockquote type="cite"><font class="Apple-style-span" color="#000000"><span>told me that he passed you the control of that part of libnl. Looking at your</span><br></font></blockquote><blockquote type="cite"><font class="Apple-style-span" color="#000000"><span>github page, I saw that you just finished refactoring a ctypes based libnl</span><br></font></blockquote><blockquote type="cite"><font class="Apple-style-span" color="#000000"><span>wrapper.</span><br></font></blockquote><span>Yes, exactly.</span><br><span></span><br><blockquote type="cite"><font class="Apple-style-span" color="#000000"><span></span><br></font></blockquote><blockquote type="cite"><font class="Apple-style-span" color="#000000"><span>My question are the following: Is there gonna be any extra effort going into</span><br></font></blockquote><blockquote type="cite"><font class="Apple-style-span" color="#000000"><span>Thomas' swig based python bindings? Are you going to submit the new ctypes for</span><br></font></blockquote><blockquote type="cite"><font class="Apple-style-span" color="#000000"><span>inclusion in libnl as a drop in replacement? Do you have some documentation of</span><br></font></blockquote><blockquote type="cite"><font class="Apple-style-span" color="#000000"><span>the python API you are aiming for?</span><br></font></blockquote><span>1. Yes, I will patch swig if needed until ctypes binding become ready.</span><br><span>Original swig binding contain many trivial errors and sometimes non python-way api. I tried to fix that, but discovered problem with pypy as it is not compatible well with swig. So I decide to write new one using ctypes.</span><br><span></span><br><span>2. Yes, when ctypes binding will be ready, I will replace swig with ctypes. But drop-in replacement will not be guaranteed, as the api will change.</span><br><span></span><br>3. No, i have no documentation yet. Architecture changes somewhat. I'm trying to write api both thin and pythonic at the same time. I mean generators instead of get_first + get_next, automatic destruction and object dependency tracking, and so on. I appreciate any help, so it will be nice if you review my work. If you want I to implement some of features just for you - please ask me. <span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); font-size: medium; "><br></span></div><div></div></body></html>