Hello,
Ticket #25192[1] is about a problem that only affects Python 2 users: If you
write a migration with a `RunPython` operation, and you use the documented
`RunPython.noop` as the reverse action (or forward action, but that is much
less likely...), then all looks well, until you try to squash that migration;
then, things blow up. Since master no longer supports Python 2, the ticket was
closed "wontfix" by core.
However, I think that if we can easily fix the problem in 1.11, then we should;
that version is still supporting Python 2 and will do so for several years.
1.11 is now feature frozen, but this is a bugfix, not a new feature; and the
fix
is 6 lines[2] (in production code) that won't make you cringe too much.
I suggest that we re-open this ticket and solve it in the 1.11.x branch.
Thanks,
Shai.
[1] https://code.djangoproject.com/ticket/25192
[2]
https://github.com/django/django/compare/stable/1.11.x...shaib:ticket_25192?expand=1
