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 500 page does disp
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 should
support that too ;)
C
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 mailing list alias. For ex
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,
Russ
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 r
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 wrote:
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 Google Groups
"Django developers" gro
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: Thu, Jun 9, 2011 at 3:48 PM
Subj
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:
a) can't upgrade
The technical 500 page does display a lot of information, but debugging a
failure is all about information.
#11834 is helpful (dims django frames) without getting in the way (hiding
things). For now, this is a good example of a helpful change with minimal
negative impact.
I'm sure the 500 page
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 Genssen a écrit :
>
> > the q
On 9 juin, 10:51, Tom Evans wrote:
> I disagree entirely. The stack trace is the first thing I look at, and
> whilst we need to make it easy for people to learn django, we
> shouldn't be hiding essential information from people - even if it is
> just hidden in a separate 'tab'.
Me too. Why is
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.
htt
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
>reply to message:
>date: 09.06.2011 14:22:54
>from: "Carl Meyer"
>to: django-developers@googlegroups.com
>subject: [] Re
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 p
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 Gazit wrote:
>
>> I'm loo
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 support
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 that function. By placing a ne
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. That leaves our
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" +
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
apps/platfor
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 moved down the list as n
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 items:
> - Python path a
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 fram
24 matches
Mail list logo
