mitmproxy/test
Aldo Cortesi 9dcd15d350 asyncio: ditch the handler context
There are a few reasons for this. First, logs are now async, and can be called
at any time. Second, the event loop is thread local, so there can only ever be
one master per thread. These two things together completely obviate the need
for a handler context.
2018-04-07 09:04:14 +12:00
..
bench bench: Add some very simple manual benchmarking helpers 2018-03-17 10:06:46 +13:00
examples Revamp verbosity options 2018-02-26 09:02:24 +13:00
helper_tools Clean up un-necessary arguments to taddons.context 2018-02-24 13:22:15 +13:00
mitmproxy asyncio: ditch the handler context 2018-04-07 09:04:14 +12:00
pathod rename TLS/SSL-related functions 2018-01-06 10:43:54 +01:00
__init__.py move tests into shared folder 2016-02-15 16:34:22 +01:00
conftest.py skip ipv6 tests on sudo-enabled travis builds 2017-10-20 16:00:25 +02:00
filename_matching.py Python 3.5 is dead -- long live Python 3.6! 2018-03-31 18:46:32 +02:00
full_coverage_plugin.py Increase net.tcp.py coverage (#2336) 2017-05-17 23:27:57 +08:00
individual_coverage.py Python 3.5 is dead -- long live Python 3.6! 2018-03-31 18:46:32 +02:00