Vishnu Ks 123bcea518 management: Don't use sys.exit(1). ... Using sys.exit in a management command makes it impossible to unit test the code in question. The correct approach to do the same thing in Django management commands is to raise CommandError. Followup of b570c0dafa		2019-05-03 14:20:39 -07:00
..
__init__.py	Move management commands to the analytics app.	2013-11-06 16:51:08 -05:00
analyze_mit.py	analytics: Use python 3 syntax for typing.	2017-11-17 13:16:49 -08:00
analyze_user_activity.py	analytics: Use python 3 syntax for typing.	2017-11-17 13:16:49 -08:00
check_analytics_state.py	analytics/zilencer/zproject: Remove unused imports.	2019-02-02 17:31:45 -08:00
clear_analytics_tables.py	management: Don't use sys.exit(1).	2019-05-03 14:20:39 -07:00
clear_single_stat.py	management: Don't use sys.exit(1).	2019-05-03 14:20:39 -07:00
client_activity.py	analytics: Use python 3 syntax for typing.	2017-11-17 13:16:49 -08:00
populate_analytics_db.py	minor: Fix an artifact of delivery email migration in `populate_analytics_db`.	2019-03-05 13:52:59 -08:00
realm_stats.py	management: Don't use sys.exit(1).	2019-05-03 14:20:39 -07:00
stream_stats.py	management: Don't use sys.exit(1).	2019-05-03 14:20:39 -07:00
update_analytics_counts.py	production: Add optional support for submitting usage statistics.	2019-02-26 17:35:10 -08:00
user_stats.py	management: Don't use sys.exit(1).	2019-05-03 14:20:39 -07:00