#26492: "./manage.py migrate" causes "maximum recursion depth exceeded" error -------------------------------------+------------------------------------- Reporter: berkerpeksag | Owner: | berkerpeksag Type: Bug | Status: closed Component: Migrations | Version: master Severity: Release blocker | Resolution: fixed Keywords: | Triage Stage: Ready for | checkin Has patch: 1 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+------------------------------------- Changes (by Tim Graham <timograham@…>):
* status: assigned => closed * resolution: => fixed Comment: In [changeset:"93deb1691eb27dc89135511fb0c10e077c8baca7" 93deb16]: {{{ #!CommitTicketReference repository="" revision="93deb1691eb27dc89135511fb0c10e077c8baca7" Fixed #26492 -- Fixed "maximum recursion depth exceeded" migrate error. A regression introduced in 0d3c616fbb2f49fa7ff6809e5a6777275352b35b; refs #26351. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/26492#comment:6> 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 django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/070.77e499210114bd91c43e08e1499869a7%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.