#1796: [patch] "Cannot resolve keyword ___ into field" error when working with
ManyToMany relation
------------------------------+---------------------------------------------
Reporter: anonymous | Owner: adrian
Type: defect | Status: new
Priority: high | Milestone:
Component: Database wrapper | Version: SVN
Severity: critical | Resolution:
Keywords: |
------------------------------+---------------------------------------------
Comment (by lukeplant):
Multiple 'Option' objects per model class shouldn't be created -- this is
the bug. I've seen the exact same thing before:
http://groups.google.com/group/django-
developers/tree/browse_frm/thread/8fb80e97076e707a/0059cbddcee8eb2c?rnum=1&_done=%2Fgroup%
2Fdjango-
developers%2Fbrowse_frm%2Fthread%2F8fb80e97076e707a%2F0059cbddcee8eb2c%3Flnk%3Dst%26rnum%3D1%26#doc_02ef913ed50a6705
Basically it seems there is some bug in Python's __import__ statement, or
something wrong with the way Django is using it, that causes a module to
be reloaded. There are a lot of usages of __import__(), and I think we
need to get this sorted out.
--
Ticket URL: <http://code.djangoproject.com/ticket/1796>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates
-~----------~----~----~----~------~----~------~--~---
