PieterCK dfae02a273 migration_status: Move get_migration_status to a new file. ... This moves `get_migration_status` to its own file in zerver/lib/migration_status.py. This is a prep work to refactor the check migration function of import/export later on. Some of the imports are moved into `get_migration_status` because we're planning to share this file with `check-database-compatibility` which is also called when one does `production-upgrade`, so we'd want to avoid doing file-wide import on certain types of modules because it will fail under that scenario. In `test_fixtures.py`, `get_migration_status` is imported within `Database.what_to_do_with_migrations` so that it is called after `cov.start()` in `test-backend`. This is to avoid wierd interaction with coverage, see more details in #33063. Fixes #33063.		2025-01-24 17:08:37 -08:00
..
commands	migration_status: Move get_migration_status to a new file.	2025-01-24 17:08:37 -08:00
data	emoji: Moved unified_reactions.json file.	2017-06-09 16:38:58 -07:00
__init__.py	[manual] Rename Django app from zephyr to zerver.	2013-08-06 07:39:36 -04:00