[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #6950 [pyonionoo]: write tests for pyonionoo

#6950: write tests for pyonionoo
-----------------------+----------------------------------------------------
 Reporter:  gsathya    |          Owner:  gsathya 
     Type:  task       |         Status:  accepted
 Priority:  major      |      Milestone:          
Component:  pyonionoo  |        Version:          
 Keywords:             |         Parent:          
   Points:             |   Actualpoints:          
-----------------------+----------------------------------------------------

Comment(by atagar):

 > atagar, you pondered working on pyonionoo. Is that still your plan?

 I'm pondering three projects...

  * pyonoinoo
  * clean up the arm codebase and finish making a release that uses stem
  * twisted counterpart for the stem's control module

 My present plan is to spend a few weeks addressing lingering stem issues,
 after that we'll see. Each project has a different appeal for me...

  * Pyonionoo would involve improving stem's descriptor support and
 learning more about databases.
  * Arm would improve stem's controller functionality and is outstanding
 technical debt for me.
  * Judging by Txtorcon's popularity twisted support is pretty popular.
 We'll see if the [https://www.torproject.org/getinvolved/volunteer.html.en
 #txtorcon-stemIntegration gsoc idea] gets any good applications, if not
 then sinking time here might be a good way for me to improve stem
 adoption.

 > If so, do you have any preferences for choosing a testing framework for
 Onionoo/pyonionoo?

 I would probably use python's builtin unittest framework, like stem does.

 > Somewhat related, what do you think about keeping the name "Onionoo" and
 developing the Python rewrite in Onionoo's current Git repo?

 I like the idea of keeping the name, and can see some advantage for doing
 the python rewrite within a branch of the onionoo repo. It really doesn't
 matter at this point though - we can experiment elsewhere then merge in
 the history later. You're right that if we do our jobs right then no one
 will even know that the codebase was rewritten. ;)

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6950#comment:20>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs