#32350: Showmigrations applied timestamp can cause runtime error
-------------------------------------+-------------------------------------
Reporter: Daniel Ebrahimian | Owner: Daniel
| Ebrahimian
Type: Bug | Status: assigned
Component: Core (Management | Version: master
commands) |
Severity: Normal | Resolution:
Keywords: management command | Triage Stage: Accepted
showmigrations applied timestamp |
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* needs_better_patch: 0 => 1
* needs_tests: 0 => 1
* stage: Unreviewed => Accepted
Comment:
It looks like the issue is related to the usage of `replaces` which is
relied upon the `squashmigrations` feature.
Tentatively accepting if you're able to write a test that triggers a crash
when relying on a supported usage of `replaces` (e.g. a migration squash).
It looks like `social-app-django` ships with a complex graph of migrations
to ''replace'' `django-social-auth` migrations
e.g. https://github.com/python-social-auth/social-app-
django/blob/7a105df36ca579389b93911f748ee297ce141bb3/social_django/migrations/0001_initial.py#L29-L32
--
Ticket URL: <https://code.djangoproject.com/ticket/32350#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.c88d9a5aa50bf2d75a1f54b3bbd6f8ee%40djangoproject.com.
