When running pytest on a database with --reuse-db where python manage.py migrate was already run, cause failure on old runpython

I explain myself,

I have a project with a lot of migrations, with 3 important migrations for our case (in that order):

1. a migration that add the field foo to the model Bar
2. a migration that has a RunPython, doing some computation based on the field foo
3. a migration that remove the field foo

now if i first do

python manage.py migrate

I finish with a database without field foo => normal and expected

if I then run pytest --reuse-db I will got SQL failure because pytest re-runs all migrations, but without actually replaying the changes on the database , but only running the RunPython, so the RunPython of 2) is run on database were the field has already been removed

is it a known behaviour , if so why ?

I would have thought that it would see migrations has been run , and will not execute anything, runpython included

Start by reproducing the sequence with python manage.py migrate followed by pytest --reuse-db, focusing on the migrations containing RunPython and the removed foo field. Trace how pytest-django determines which migrations to apply and verify whether the database state is expected; done means the behavior is explained or corrected with a regression test for this sequence.