#24701: Migration created on python2.7 fails to load on python 3 due to
models.Manager
----------------------------+---------------------------------------------
Reporter: aeby | Owner: MarkusH
Type: Bug | Status: closed
Component: Migrations | Version: 1.8
Severity: Normal | 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
----------------------------+---------------------------------------------
Comment (by Markus Holtermann <info@…>):
In [changeset:"419f296259d7c22d34d7d1cf46e7cf29e6b26b13" 419f2962]:
{{{
#!CommitTicketReference repository=""
revision="419f296259d7c22d34d7d1cf46e7cf29e6b26b13"
[1.8.x] Fixed #24701 -- Converted model manager names to unicode in
migrations
Thanks to Reto Aebersold for reporting the issue and Tim Graham and
Claude Paroz for the review.
Backport of faad6070ee2eeea270c76381f9ca5999bf1ac15f from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24701#comment:9>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.3680fbfea5033b10840c9fb7b6f1405e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
