From bea0bd236a60e3e6c80027448e51b7802394304a Mon Sep 17 00:00:00 2001 From: Aldo Cortesi Date: Tue, 14 Apr 2015 11:58:10 +1200 Subject: Housekeeping and cleanups - No output to stdout on load in examples - they muck up the test suite. - Use the odict module directly, rather than aliasing it. The small convenience this gives to scripters is not worth it. - Move the cookie tests from the flow test module to the protocol_http test module. --- doc-src/scripting/inlinescripts.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc-src/scripting') diff --git a/doc-src/scripting/inlinescripts.html b/doc-src/scripting/inlinescripts.html index 7f05eedf..7b9dfe68 100644 --- a/doc-src/scripting/inlinescripts.html +++ b/doc-src/scripting/inlinescripts.html @@ -122,7 +122,7 @@ The main classes you will deal with in writing mitmproxy scripts are: A handle for interacting with mitmproxy's from within scripts. - libmproxy.flow.ODict + libmproxy.odict.ODict A dictionary-like object for managing sets of key/value data. There is also a variant called CaselessODict that ignores key case for some -- cgit v1.2.3