On Thu, Mar 10, 2011 at 12:10 PM, Venkatraman S <venka...@gmail.com> wrote: > I stumbled on this 'probable' bug and thought would share it with the group > to ensure that it indeed is a bug and not something that i have been > hallucinating :) > When you try using force_unicode without importing it, the django console > does not report an error; for eg, when i was playing around with LogEntry, > using like : > .. > .. > somecode_here_1 > LogUserAction.objects.log_action( > user_id = request.user.pk, > content_type_id = ContentType.objects.get_for_model(object).pk, > object_id = object.pk, > object_repr = force_unicode(object), > action_flag = CHANGE > ) > somecode_here_2 > .. > render_to-response... > > The code just silently failed - i.e control never came to somecode_here_2 , > but somehow the template got rendered without any errors. Thoughts? > > -V- >
If you didn't get to somecode_here_2, you certainly didn't get to render_to_response. More likely, your browser returned a cached version of the page. Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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.
