[tor-bugs] #6810 [Flashproxy]: Reduce code duplication across client programs

[Tor Bug Tracker & Wiki]

#6810: Reduce code duplication across client programs
-----------------------------+--------------------------
     Reporter:  dcf          |      Owner:  dcf
         Type:  enhancement  |     Status:  needs_review
     Priority:  minor        |  Milestone:
    Component:  Flashproxy   |    Version:
   Resolution:               |   Keywords:
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+--------------------------

Comment (by infinity0):

 I haven't decided on what I'll do yet, but regarding the manual-
 environment approach:

 Replying to [comment:14 dcf]:
 > Having to set PYTHONPATH is annoying but probably tolerable. I would
 rather not have an `init-dev-env` script; let's just document that you
 have to set PYTHONPATH. (The name `init-dev-env` is mostly unknown to
 Google--is there some other name commonly used by other projects?)
 >

 The abstract idea here would be {launch a shell with,export} an
 environment suitable for manually {running,debugging} {from source,built-
 but-not-installed components,tests}.

 It sounds like something that's just on the wrong side of the boundary of
 "popular enough to be standardised". I did find a few examples though:

 - "init-dev-env": https://github.com/karma-
 runner/karma/tree/master/scripts
 - "devshell": http://www.openembedded.org/wiki/Devshell

 I'll look into the topic a bit more. Documenting is OK for now (that is if
 I choose this path), and if we ever need to do more than just "set the
 environment" we can consider turning it into a script then.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6810#comment:15>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online