On Thu, Sep 30, 2010 at 8:01 AM, Jyrki Pulliainen <jy...@dywypi.org> wrote:
> We encountered a possible backwards incompatibility with change 12950 > [1]. This was noticed when upgrading from 1.1.1 to 1.1.2. > > If I understand correctly the change 12950 removes squelching of > ImportErrors from AppCache. AppCache in turn provides reverse- > relations for app introspection, for example in admin interface. This > change now causes the ImportError in one otherwise fine case to > propagate and break the application. > > Funnily enough, this does not break our application per se. The webapp > still continues to work with admin interface fully responsive, doing > all the changes wanted, tests passing etc. This only affects a smaller > worker script that is run via upstart. > [additional info skipped] Without specifics (at least a traceback from the error) it's virtually impossible to say whether the problem you encountered was a flaw in this changeset or an error in the application. The original fix here was updated based on user feedback, see for example http://code.djangoproject.com/ticket/13335. There may also have been at least one other like that but I don't recall exactly and do not have time to search now. So far as I know the version of the change that appears in a released version only reports true application errors (e.g. circular imports) that really should never have been suppressed in the first place. Karen -- http://tracey.org/kmt/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
