Re: Django Error Display Page

What I'd really like is a stacktrace in a plain text in the html commentary ("") on the very top of the page. This really would save me from curl's output reading nightmare without losing all browser-understandable happiness On Jun 9, 6:16 pm, Idan Gazit wrote: > The technical

Re: Deprecation policy for IE6

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 to get companies to use newer browsers we

Re: Backscatter from django-users (att of moderator please)

Ahh, handy to know! Thanks :) On Thu, Jun 9, 2011 at 9:12 PM, Russell Keith-Magee wrote: > Hi Cal, > > I've just unsubscribed d...@wildpalms.com from django-users. > > For future reference -- you can contact the owners of *any* Google > group by appending +owner to the

Re: Backscatter from django-users (att of moderator please)

Hi Cal, I've just unsubscribed d...@wildpalms.com from django-users. For future reference -- you can contact the owners of *any* Google group by appending +owner to the mailing list alias. For example, the django-users moderators can be reached at django-users+ow...@googlegroups.com. Yours,

Better error message for django.core.urlresolvers.reverse

Hi, This is the current error message when a url name or argument doesn't exist: >>> reverse('core:non_existant') NoReverseMatch: Reverse for 'non_existant' with arguments '()' and keyword arguments '{}' not found. Is there support for adding the namespace into the error message? Tom -- You

Re: [] Re: Deprecation policy for IE6

It's even more complicated than that. You care about the statistics for the people who use your product. Also, the stats for the admin userbase will be very different than the userbase of a public facing frontend. That is very hard to deduce. On Thu, Jun 9, 2011 at 9:06 AM, Henrik Genssen

Re: Deprecation policy for IE6

On Thu, Jun 9, 2011 at 9:44 AM, Aymeric Augustin wrote: > c) need to access a Django application — let alone a Django >= 1.4 app. even less likely: a Django application's admin page -- Javier -- You received this message because you are subscribed to the

Backscatter from django-users (att of moderator please)

Can one of the mods please remove the following user from the django-users mailing list please. Apologies for sending this mail to django-developers, I wanted to make sure the appropriate person noticed it! Cal -- Forwarded message -- From: Date:

Re: Deprecation policy for IE6

2011/6/9 Idan Gazit > I'm looking at admin tickets, and I realize that some defined policy for > when we can safely start to break IE6 would be very helpful. > My vote is: "last year". Even Microsoft begs people to move away from IE6. I can't think of a context where people:

Re: Deprecation policy for IE6

IE7 is almost just IE6 with tabs. In my opinion, going forward, IE support should be IE8+. Like said earlier, if someone really need support for IE7 and lower, they can still use Django 1.3. On Jun 9, 3:27 pm, Xavier Ordoquy wrote: > Le 9 juin 2011 à 15:06, Henrik

Re: [] Re: Deprecation policy for IE6

Le 9 juin 2011 à 15:06, Henrik Genssen a écrit : > the question is not - how old a browser is, but how many user it (still) has > in germany there are still 4% using IE6 - thats > half the user of Google's Chrome with 8%. > > > Henrik It looks like fewer german users are still running ie6.

Re: Deprecation policy for IE6

OK, by the power vested in me, I declare the admin unshackled from the need to support IE6. Reception and dancing shall follow. On Thursday, June 9, 2011 at 2:22 PM, Carl Meyer wrote: > On 06/09/2011 05:32 AM, Idan Gazit wrote: > > I'm looking at admin tickets, and I realize that some defined

Re: Deprecation policy for IE6

I've seen a few admin themes in the wild. Would it be fair to say that after a certain (very near) date, if you need EOL browser support, it will have to be provided by a 3rd party theme? On Jun 9, 2011 7:11 AM, "Gert Van Gool" wrote: > On Thu, Jun 9, 2011 at 12:32, Idan

Re: Deprecation policy for IE6

On 06/09/2011 05:32 AM, Idan Gazit wrote: > I'm looking at admin tickets, and I realize that some defined policy > for when we can safely start to break IE6 would be very helpful. > > I'd like to simply declare that going forward, the admin need not > work perfectly in IE6. That leaves our

Re: Template inheritance and duplicated content.

Hi, On May 24, 10:58 am, Jonathan Slenders wrote: > I guess this is a flaw in the inheritance algorithm, only the most > outer blocks should be used during the resolving of inheritance. How else would it work? Think of a block like a function plus the execution of

Re: Deprecation policy for IE6

On Thu, Jun 9, 2011 at 12:32, Idan Gazit wrote: > I'm looking at admin tickets, and I realize that some defined policy for > when we can safely start to break IE6 would be very helpful. > > I'd like to simply declare that going forward, the admin need not work > perfectly in IE6.

Deprecation policy for IE6

I'm looking at admin tickets, and I realize that some defined policy for when we can safely start to break IE6 would be very helpful. I'd like to simply declare that going forward, the admin need not work perfectly in IE6. That leaves our support footprint for the Admin at "modern browsers" +

Re: Sorting UX question

Jannis and I are sprinting on this; we'd like to take a 2nd look at potential behaviors after a long conversation yesterday. The current solution works, but I think there's still a lot of room for user confusion. Plan is to look again at existing sorting implementations (on various

Re: Sorting UX question

On Thu, Jun 9, 2011 at 12:45 AM, Luke Plant wrote: > In the new admin sorting UI, which now supports sorting on multiple > fields, the behaviour can be described by the following two rules: > > 1. If you click on a header, it is made the primary sort field >   (with others

Re: Django Error Display Page

On Wed, Jun 8, 2011 at 11:50 AM, Mateusz Harasymczuk wrote: > Hi, > I have been thinking about this for quite a long time. > Can you make an error display page less verbose? > I mean not to exclude those useful information, but to initially fold (hide) > them. > Fold those

Re: get_object_or_404 hook

Indeed, this is nothing that has to be in the Django core. You can do something like this: http://dpaste.com/hold/552209/ Although, I do not think that's the best solution. By catching all DoesNotExist errors, the Django middleware will not receive the exception anymore and exception logging