tor/scripts/maint/practracker
Nick Mathewson dd4fa9b468 Extract relay-only handshake code into its own file.
This is not the only relay-only handshake code, but it is most of
such code that is in connection_or.c.
2020-02-19 19:11:57 -05:00
..
testdata practracker: integration tests for --regen and --regen-overbroad 2020-02-03 13:11:58 -05:00
.enable_practracker_in_hooks maint-0.4.2: remove ".enable_practracker_in_hooks". 2019-10-11 17:18:55 -04:00
exceptions.txt Extract relay-only handshake code into its own file. 2020-02-19 19:11:57 -05:00
includes.py Stop assuming that /usr/bin/python exists 2020-02-16 21:58:01 +02:00
metrics.py Stop assuming that /usr/bin/python exists 2020-02-16 21:58:01 +02:00
practracker_tests.py Stop assuming that /usr/bin/python exists 2020-02-16 21:58:01 +02:00
practracker.py Stop assuming that /usr/bin/python exists 2020-02-16 21:58:01 +02:00
problem.py practracker: add a --regen-overbroad option to remove overbroad exceptions. 2020-02-03 13:02:12 -05:00
README practracker: make filename terminology uniform 2019-08-29 09:20:27 -04:00
test_practracker.sh practracker: integration tests for --regen and --regen-overbroad 2020-02-03 13:11:58 -05:00
util.py python: Add __future__ imports for python 3 compatibility 2019-12-12 15:58:51 +10:00

Practracker is a simple python tool that keeps track of places where
our code is ugly, and tries to warn us about new ones or ones that
get worse.

Right now, practracker looks for the following kinds of
best-practices violations:

  .c files greater than 3000 lines long
  .h files greater than 500 lines long
  .c files with more than 50 includes
  .h files with more than 15 includes

  All files that include a local header not listed in a .may_include
  file in the same directory, when that .may_include file has an
  "!advisory" marker.

The list of current violations is tracked in exceptions.txt; slight
deviations of the current exceptions cause warnings, whereas large
ones cause practracker to fail.

For usage information, run "practracker.py --help".