On Friday, 10 June 2011 at 04:31, Valentin Golev wrote:
> What I'd really like is a stacktrace in a plain text in the html
> commentary ("") on the very top of the page.
+1
This would actually be very useful when debugging Ajax calls in browsers. I
often find myself reading the HTML particular
On Fri, Jun 10, 2011 at 12:01 AM, Florian Apolloner
wrote:
> Hi,
>
> On Jun 9, 1:11 pm, Gert Van Gool wrote:
>> I remember from the HTML5 doctype that some people (with app in enterprises)
>> need the support
>
> Right, but even Google is dropping support for IE < 8 [1]! And if
> Google is trying
On Jun 10, 3:34 am, Dougal Matthews wrote:
> On Friday, 10 June 2011 at 04:31, Valentin Golev wrote:
> > What I'd really like is a stacktrace in a plain text in the html
> > commentary ("") on the very top of the page.
>
> +1
>
> This would actually be very useful when debugging Ajax calls in brow
For the background to this problem please see my Stack Overflow
question here [1].
I recently had to do some head-scratching over Django 1.3's logging
configuration, because with DEBUG=True the 'django.request' logger
isn't called when an uncaught exception occurs during a request.
It wasn't obvi
Can a core developer please advise on the preferred design here?
The main ideas are:
1. Add a 'disabled_choices' attribute to the widget that takes an
iterable of choices to disable. I've attached a WIP patch to ticket
16149 following this approach. Optionally this could be passed to the
widget
For me, it would definitely be a good idea to change the error page a
bit, so at least the actual error message is not in grey but in black,
and bigger. People tend not to see it right now, because it looks
unimportant.
Wim
--
You received this message because you are subscribed to the Google Gr
Hi Gregor,
On the way home from DjangoCon I realized there is a (IMHO) elegant
solution to this problem that is closer to the nature of django's
template language.
What you want with form-rendering is having defaults, but being able
to override them; which is something you can do with dja
On Thu, Jun 09, 2011 at 08:31:44PM -0700, Valentin Golev wrote:
> What I'd really like is a stacktrace in a plain text in the html
> commentary ("") on the very top of the page.
I've opened https://code.djangoproject.com/ticket/16227 with patch
attached.
Regards,
Dan
--
You received this mess
class EasyWin(object):
def process_exception(self, request, *args, **kwargs):
if not request.is_ajax(): return
impot traceback
return HttpResponse(traceback.format_exc())
On Jun 10, 1:11 pm, Daniel Watkins
wrote:
> On Thu, Jun 09, 2011 at 08:31:44PM -0700, Valentin Golev wrote:
> >
IE 7 should be probably dropped with IE6, I can't see point in keeping
it
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
Totally agree,
If someone moved out of the IE 6, then he/she move out of the IE 7, too.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-developers/-/fAHtqn9esi
11 matches
Mail list logo
