[tor-dev] Python TorCtl development questions

[Sean Robinson]

On Sat, Jun 11, 2011 at 12:28 PM, Damian Johnson <atagar1 at gmail.com> wrote:
>>  I have begun using the Python TorCtl package to develop a gui TOR
>> controller.
>
> Great! What are your planned use cases for this gui? Kamran is also
> beginning work on a gtk gui for arm (http://www.atagar.com/arm/ - a
> python project that uses torctl) so that might be of interest too.
> We'd certainly be glad to have the help.

  The one feature I really, really miss from Tork is the Tor Console
<http://sourceforge.net/dbimage.php?id=95124>. So, Syboa replicates
that screen.  I still have not decided whether I will try to release
this software.  But, I can still provide developer feedback for
TorCtl.

>> In this examination, I have begun adding
>> comments, renaming vars to be more explicit, etc.  How open are the
>> developers to these changes?
>
> Changes need to support backward comparability but besides that it's

  I completely agree.  One of my first steps is to write unit tests
for those parts I am tweaking so that I can verify behavior before and
after changes.  I, also, would like to submit these unit tests to the
TorCtl package.

>>  Is there interest in making TorCtl into a more mainstream form of
>> Python package?
>
> TorCtl already has been packaged for Debian (the python-torctl
> package) so a big advantage of a distutils installer have already been
> covered. I'm not sure if there's interest in an rpm or distutils for
> standalone installation.

  I would encourage a distutils-compatible form.  Since the Debian
package seems to move the TorCtl modules into a distutils package
form, it should make things easier for the Debian packager and other
potential OS/distribution packagers.  Also, this would enable
developers on any platform to install just the TorCtl Python package
with minimal work.  Currently, (as far as I can see) the only way for
a non-Debian-based developer to get TorCtl is through git clone.

>>  How far back in Python versions are we trying to maintain
>> compatibility?
>
> Definitely back to 2.4, I'm not sure how much further than that.

  I would agree that Py2.4 is a good threshold.  I was afraid someone
was going to want Py1.x compatibility.


-- 
Sean Robinson
WiFi Radar - http://wifi-radar.berlios.de
Python WiFi - http://pythonwifi.wikispot.org
pymnl - http://pymnl.wikispot.org