Re: get_object_or_404 hook

2011-06-09 Thread Jonathan Slenders 
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 frameworks will not work.
Also, you won't receive an error mail. A better solution may be to
handle this errors in custom middleware, but that's actually to be
discussed at django-users.

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Django Error Display Page

2011-06-09 Thread Tom Evans 
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 at the top yellow background.
> - (Hide or fold) django traceback entries
> When I have a problem I have to scroll down (passing django calls) few pages
> until I am able to find which MY action caused an error.
> I know looking at django callback may be useful, but in my case, hardly
> ever, and probably for newcommers also.
> I am imagining this like that:
> At the top of the error page, there are tabs.
> Summary, Traceback, Request, Settings, and copy-paste view (feedback view).
> Summary tab, contains this yellow background information with PYTHON_PATH
> initially folded, and traceback filtered out to include only information
> from project not calls from django itself.
> Traceback, request and settings tabs as it is right now, but separated for
> easy of view.
> copy-paste (feedback) - a standardize view for easy of copy-and-paste to the
> Internet message boards, groups and so on...
> It would need a template refactor and some more js involved, should not be a
> hard thing to do.
> I read that there is a plan to redesign an error page, but since then, those
> modifications should do the job.
> What do you think?

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'.

I also strongly disagree about manipulating the traceback at all. Why
would I not want to see where it went wrong inside Django? I also
don't buy the 'too much information' argument, I have never been in a
situation where a crash report has too much information - most of the
time it doesn't have enough.

Besides which, if the django error page is not what you desire, you
can always write your own middleware to produce your own error page.
If you really want to change how django's default error page looks
like, producing your own version first would be more compelling (and
less bikesheddy).

Cheers

Tom

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Sorting UX question

2011-06-09 Thread Tom Evans 
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 necessary).
>
> 2. If you click on a header that was already part of the sorting,
>   the sort order for that field is reversed.
>

Just an idea, when a column is in use as a sort field, could we not
add/make visible a sort order widget, which is then used to control
the sort ordering of the column.
Eg, click the column to activate sorting by that field, with the
details you described. It then gains a simple widget (a large \u2193
?) in the column header, which when clicked toggles the sort order on
that column, without affecting the position in the sorting list.

This would remove the ambiguity about what clicking the header of a
column does - it always toggles sorting by that column, and provides a
simple and obvious way to change the sort order.

Cheers

Tom

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Sorting UX question

2011-06-09 Thread Idan Gazit 
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/platforms) and maybe actually develop the nicer UI promosed earlier in 
#11834.

I

On Thursday, June 9, 2011 at 1: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 necessary).
> 
> 2. If you click on a header that was already part of the sorting,
>  the sort order for that field is reversed.
> 
> Item 1. is behaviour we agreed on, and item 2. is too, kind of, but the
> latter is the one I'm interested in tweaking.
> 
> Currently, this means that if, for example, you do:
> 
> 1) Click 'first name' header
> 2) Click 'last name' header
> 3) Click 'first name' header
> 
> you build up the following sort:
> 
> 1) Sort by first name ascending
> 
> 2) Sort by last name ascending, then
>  first name ascending
> 
> 3) Sort by first name *descending*, then
>  last name ascending
> 
> It is this last step that might need improving. Is it confusing that you
> end up with first name *descending*?
> 
> We could change the 2nd rule to:
> 
> 2. If you click on a header that was already the primary sort field,
>  the sort order for that field is reversed.
> 
> I think this might be more intuitive. Comments?
> 
> Luke
> 
> -- 
> "Where a person wishes to attract, they should always be ignorant."
> (Jane Austen)
> 
> Luke Plant || http://lukeplant.me.uk/
> 
> -- 
> 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 
> (mailto:django-developers@googlegroups.com).
> To unsubscribe from this group, send email to 
> django-developers+unsubscr...@googlegroups.com 
> (mailto:django-developers+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/django-developers?hl=en.


-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Deprecation policy for IE6

2011-06-09 Thread 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. 

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" + IE>7.

* contrib.admin is contrib, and thus not covered by Django's deprecation policy

* This isn't a change which affects any other frontend product built with 
Django. The only audience this affects is users of the admin. I think it's 
reasonable to require administrative users to have IE7 if all they have is IE.

The admin is already using the HTML5 doctype (see 
https://groups.google.com/d/topic/django-developers/wJ9dnUDHUVI/ for 
background), but not any of the new HTML5 elements. 

This change would mainly open up the ability to use PNGs and remove hacks and 
workarounds from admin CSS/HTML

Any objections?

I



-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Deprecation policy for IE6

2011-06-09 Thread Gert Van Gool 
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 support footprint for the Admin at "modern
> browsers" + IE>7.
>
> * contrib.admin is contrib, and thus not covered by Django's deprecation
> policy
>
> * This isn't a change which affects any other frontend product built with
> Django. The only audience this affects is users of the admin. I think it's
> reasonable to require administrative users to have IE7 if all they have is
> IE.
>
> The admin is already using the HTML5 doctype (see
> https://groups.google.com/d/topic/django-developers/wJ9dnUDHUVI/ for
> background), but not any of the new HTML5 elements.
>
> This change would mainly open up the ability to use PNGs and remove hacks
> and workarounds from admin CSS/HTML
>
> Any objections?
>
> I
>
>
>
> --
> 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
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>
Although I don't personally.
I remember from the HTML5 doctype that some people (with app in enterprises)
need the support

-- Gert

Mobile: +32 498725202
Twitter: @gvangool 

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Template inheritance and duplicated content.

2011-06-09 Thread Armin Ronacher 
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 new block within a block you
want that behavior and if you override a block and in that another
block that already existed both Jinja2 and Django will have to also
immediately call it. There is only one rule: if you don't like that,
make the block toplevel. The only alternative sane semantic would be
raising a runtime error, but I don't think that is a good idea.

Regards,
That Jinja guy

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Deprecation policy for IE6

2011-06-09 Thread Carl Meyer 
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 footprint for the
> Admin at "modern browsers" + IE>7.
> 
> * contrib.admin is contrib, and thus not covered by Django's
> deprecation policy
> 
> * This isn't a change which affects any other frontend product built
> with Django. The only audience this affects is users of the admin. I
> think it's reasonable to require administrative users to have IE7 if
> all they have is IE.
> 
> The admin is already using the HTML5 doctype (see
> https://groups.google.com/d/topic/django-developers/wJ9dnUDHUVI/ for
> background), but not any of the new HTML5 elements.
> 
> This change would mainly open up the ability to use PNGs and remove
> hacks and workarounds from admin CSS/HTML
> 
> Any objections?

Hearty +1 from me, for purely pragmatic reasons. In 2011, IE6 support is
simply an unreasonable burden to place on volunteer front-end
development work, IMHO. It's hard enough getting front-end work done
without tripling (quadrupling? more?) the pain factor like that. In my
mind, asking front-end developers to support IE6 is roughly similar to
asking Python devs to support Python 1.5, perhaps not in terms of usage,
but in terms of the additional development pain.

I think it needs to be stated clearly that the effective choice is
between maintaining IE6 support and making major improvements to the
admin. If someone wants to argue that admin IE6 support should be
maintained for another release, they should acknowledge that the
implication is that there probably won't be significant upgrades to the
admin UI for at least that long.

If there are Django deployments whose administrators really can't use
any browser other than IE6, Django 1.3 will be around as long as they
need it. It's not a reasonable tradeoff for that (frankly somewhat
ridiculous - IE6 is how many years old now?) edge case to continue to
hold the rest of the community hostage.

Carl

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Deprecation policy for IE6

2011-06-09 Thread Richard Bronosky 
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 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" + IE>7.
>>
>> * contrib.admin is contrib, and thus not covered by Django's deprecation
>> policy
>>
>> * This isn't a change which affects any other frontend product built with
>> Django. The only audience this affects is users of the admin. I think
it's
>> reasonable to require administrative users to have IE7 if all they have
is
>> IE.
>>
>> The admin is already using the HTML5 doctype (see
>> https://groups.google.com/d/topic/django-developers/wJ9dnUDHUVI/ for
>> background), but not any of the new HTML5 elements.
>>
>> This change would mainly open up the ability to use PNGs and remove hacks
>> and workarounds from admin CSS/HTML
>>
>> Any objections?
>>
>> I
>>
>>
>>
>> --
>> 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
>> django-developers+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/django-developers?hl=en.
>>
>>
> Although I don't personally.
> I remember from the HTML5 doctype that some people (with app in
enterprises)
> need the support
>
> -- Gert
>
> Mobile: +32 498725202
> Twitter: @gvangool 
>
> --
> 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
django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
>

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Deprecation policy for IE6

2011-06-09 Thread Idan Gazit 
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 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" + IE>7.
> > 
> > * contrib.admin is contrib, and thus not covered by Django's
> > deprecation policy
> > 
> > * This isn't a change which affects any other frontend product built
> > with Django. The only audience this affects is users of the admin. I
> > think it's reasonable to require administrative users to have IE7 if
> > all they have is IE.
> > 
> > The admin is already using the HTML5 doctype (see
> > https://groups.google.com/d/topic/django-developers/wJ9dnUDHUVI/ for
> > background), but not any of the new HTML5 elements.
> > 
> > This change would mainly open up the ability to use PNGs and remove
> > hacks and workarounds from admin CSS/HTML
> > 
> > Any objections?
> 
> Hearty +1 from me, for purely pragmatic reasons. In 2011, IE6 support is
> simply an unreasonable burden to place on volunteer front-end
> development work, IMHO. It's hard enough getting front-end work done
> without tripling (quadrupling? more?) the pain factor like that. In my
> mind, asking front-end developers to support IE6 is roughly similar to
> asking Python devs to support Python 1.5, perhaps not in terms of usage,
> but in terms of the additional development pain.
> 
> I think it needs to be stated clearly that the effective choice is
> between maintaining IE6 support and making major improvements to the
> admin. If someone wants to argue that admin IE6 support should be
> maintained for another release, they should acknowledge that the
> implication is that there probably won't be significant upgrades to the
> admin UI for at least that long.
> 
> If there are Django deployments whose administrators really can't use
> any browser other than IE6, Django 1.3 will be around as long as they
> need it. It's not a reasonable tradeoff for that (frankly somewhat
> ridiculous - IE6 is how many years old now?) edge case to continue to
> hold the rest of the community hostage.
> 
> Carl
> 
> -- 
> 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 
> (mailto:django-developers@googlegroups.com).
> To unsubscribe from this group, send email to 
> django-developers+unsubscr...@googlegroups.com 
> (mailto:django-developers+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/django-developers?hl=en.


-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

RE: [] Re: Deprecation policy for IE6

2011-06-09 Thread Henrik Genssen 
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: 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 support footprint for the
>> Admin at "modern browsers" + IE>7.
>> 
>> * contrib.admin is contrib, and thus not covered by Django's
>> deprecation policy
>> 
>> * This isn't a change which affects any other frontend product built
>> with Django. The only audience this affects is users of the admin. I
>> think it's reasonable to require administrative users to have IE7 if
>> all they have is IE.
>> 
>> The admin is already using the HTML5 doctype (see
>> https://groups.google.com/d/topic/django-developers/wJ9dnUDHUVI/ for
>> background), but not any of the new HTML5 elements.
>> 
>> This change would mainly open up the ability to use PNGs and remove
>> hacks and workarounds from admin CSS/HTML
>> 
>> Any objections?
>
>Hearty +1 from me, for purely pragmatic reasons. In 2011, IE6 support is
>simply an unreasonable burden to place on volunteer front-end
>development work, IMHO. It's hard enough getting front-end work done
>without tripling (quadrupling? more?) the pain factor like that. In my
>mind, asking front-end developers to support IE6 is roughly similar to
>asking Python devs to support Python 1.5, perhaps not in terms of usage,
>but in terms of the additional development pain.
>
>I think it needs to be stated clearly that the effective choice is
>between maintaining IE6 support and making major improvements to the
>admin. If someone wants to argue that admin IE6 support should be
>maintained for another release, they should acknowledge that the
>implication is that there probably won't be significant upgrades to the
>admin UI for at least that long.
>
>If there are Django deployments whose administrators really can't use
>any browser other than IE6, Django 1.3 will be around as long as they
>need it. It's not a reasonable tradeoff for that (frankly somewhat
>ridiculous - IE6 is how many years old now?) edge case to continue to
>hold the rest of the community hostage.
>
>Carl
>
>-- 
>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 
>django-developers+unsubscr...@googlegroups.com.
>For more options, visit this group at 
>http://groups.google.com/group/django-developers?hl=en.
>

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: [] Re: Deprecation policy for IE6

2011-06-09 Thread Xavier Ordoquy 

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.
http://www.theie6countdown.com/default.aspx#list
reports around 2%

The other thing to take into account as idan said is:
are those ie6 users likely to be the same that will access the admin interface ?

Regards.

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Django Error Display Page

2011-06-09 Thread Jonathan Slenders 


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 it that I we have a huge Python Path, the Python
revision number and executeble locations on Top. Further, the
Exception value is displayed twice, and the request URL is also shown
in the address bar. The server time is also not that important that it
has to be shown above the stack trace.

I know it is possible to use a custom template for this, but I think
most people only want to see the Exception message, and the traceback
without scrolling down a whole page...

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Deprecation policy for IE6

2011-06-09 Thread mofle 
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 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.http://www.theie6countdown.com/default.aspx#list
> reports around 2%
>
> The other thing to take into account as idan said is:
> are those ie6 users likely to be the same that will access the admin 
> interface ?
>
> Regards.

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Django Error Display Page

2011-06-09 Thread Idan Gazit 
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 could be better, but I'd need to see a concrete proposal 
outlining the problems and how the improvements address these problems. Right 
now this feels like a case of fixing what ain't broken.

I

On Wednesday, June 8, 2011 at 6:10 PM, Graham King wrote:

> This ticket might be a part of what you're looking for:
> https://code.djangoproject.com/ticket/11834
> It proposes to dim the django parts of the stacktrace, so the code
> which most likely caused the error stands out better, which is
> certainly something I'd love to see.
> 
> There's some similar ideas discussed here:
> https://groups.google.com/group/django-developers/browse_frm/thread/bd43e2e040a17784/?hl=de&pli=1
> 
> On 8 June 2011 03:50, Mateusz Harasymczuk  (mailto:m...@harasymczuk.pl)> 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 at the top yellow background.
> > - (Hide or fold) django traceback entries
> > When I have a problem I have to scroll down (passing django calls) few pages
> > until I am able to find which MY action caused an error.
> > I know looking at django callback may be useful, but in my case, hardly
> > ever, and probably for newcommers also.
> > I am imagining this like that:
> > At the top of the error page, there are tabs.
> > Summary, Traceback, Request, Settings, and copy-paste view (feedback view).
> > Summary tab, contains this yellow background information with PYTHON_PATH
> > initially folded, and traceback filtered out to include only information
> > from project not calls from django itself.
> > Traceback, request and settings tabs as it is right now, but separated for
> > easy of view.
> > copy-paste (feedback) - a standardize view for easy of copy-and-paste to the
> > Internet message boards, groups and so on...
> > It would need a template refactor and some more js involved, should not be a
> > hard thing to do.
> > I read that there is a plan to redesign an error page, but since then, those
> > modifications should do the job.
> > What do you think?
> > --
> > Matt Harasymczuk
> > http://www.matt.harasymczuk.pl
> > 
> > --
> > 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/-/b0pKaV9JR2gzXzRK.
> > To post to this group, send email to django-developers@googlegroups.com 
> > (mailto:django-developers@googlegroups.com).
> > To unsubscribe from this group, send email to
> > django-developers+unsubscr...@googlegroups.com 
> > (mailto:django-developers+unsubscr...@googlegroups.com).
> > For more options, visit this group at
> > http://groups.google.com/group/django-developers?hl=en.
> 
> -- 
> 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 
> (mailto:django-developers@googlegroups.com).
> To unsubscribe from this group, send email to 
> django-developers+unsubscr...@googlegroups.com 
> (mailto:django-developers+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/django-developers?hl=en.


-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Deprecation policy for IE6

2011-06-09 Thread Aymeric Augustin 
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 to IE7
  b) can't run Firefox, even from an USB stick
  c) need to access a Django application — let alone a Django >= 1.4 app.

c) is extremely unlikely happen in places where the corporate culture
enforces a) and b).

-- 
Aymeric.

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Backscatter from django-users (att of moderator please)

2011-06-09 Thread Cal Leeming [Simplicity Media Ltd] 
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
Subject: Re: Re: VERY cheap django hosting?
To: cal.leem...@simplicitymedialtd.co.uk


The user d...@wildpalmsresources.com does not accept mail from your address.

The headers of the message sent from your address are shown below:

>From django-users+bnccpw99b_xahcuuspvbboez52...@googlegroups.com Thu Jun 09
09:48:45 2011
Received: from gator271.hostgator.com ([184.173.199.247]:46842)
   by terminator.websitewelcome.com with esmtps (TLSv1:AES256-SHA:256)
   (Exim 4.69)
   (envelope-from <
django-users+bnccpw99b_xahcuuspvbboez52...@googlegroups.com>)
   id 1QUgXN-0001HT-R6
   for d...@wildpalmsresources.com; Thu, 09 Jun 2011 09:48:45 -0500
Received: from mail-gx0-f184.google.com ([209.85.161.184]:58910)
   by gator271.hostgator.com with esmtps (TLSv1:RC4-SHA:128)
   (Exim 4.69)
   (envelope-from <
django-users+bnccpw99b_xahcuuspvbboez52...@googlegroups.com>)
   id 1QUgXP-0001kG-Lm
   for d...@wildpalms.com; Thu, 09 Jun 2011 09:48:47 -0500
Received: by gxk20 with SMTP id 20sf2618476gxk.11
   for ; Thu, 09 Jun 2011 07:48:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
   d=googlegroups.com; s=beta;
   h=domainkey-signature:x-beenthere:received-spf:mime-version
:x-originating-ip:in-reply-to:references:date:message-id:subject
:from:to:x-original-sender:x-original-authentication-results
:reply-to:precedence:mailing-list:list-id:x-google-group-id
:list-post:list-help:list-archive:sender:list-subscribe
:list-unsubscribe:content-type;
   bh=TSoLt/dYwGgASKftzrlR7U3iL0mbFxNANgwdwEnvFLo=;
   b=Sxh489zJCOg5ByM45Fw8DTzbo6+xEFqX4iffWNOKnkSyjylUrkt+n3ta69dvRkb4k+
HIQtyKOmX7UQfIJSRJ6r9T6Up8DAFLRHs4CgKUmQ2bY5GiOsNCf0h+btZy8UeQWHn/Vy
1d+FfQwsruLyUXBvDjceJ/UxGTqViIvtrgdhI=
DomainKey-Signature: a=rsa-sha1; c=nofws;
   d=googlegroups.com; s=beta;
   h=x-beenthere:received-spf:mime-version:x-originating-ip:in-reply-to
:references:date:message-id:subject:from:to:x-original-sender
:x-original-authentication-results:reply-to:precedence:mailing-list
:list-id:x-google-group-id:list-post:list-help:list-archive:sender
:list-subscribe:list-unsubscribe:content-type;
   b=p8vZwyQM1+NQB7IUf35DhbU8sSvauvtINOf/oCAUEfGdpgzzciu5Jxs9kD7TYiPNXq
Q2DtMKtfCysfH8tMlpufBmp3rg0ZF4GPUKWLRk2UKeIraV1sM6L483mAapUBey+4iXKd
IXxPx1qgvtKSHaE3K+YjrRAAPPdVr/vW/NzoI=
Received: by 10.236.95.147 with SMTP id p19mr77010yhf.64.1307630920768;
   Thu, 09 Jun 2011 07:48:40 -0700 (PDT)
X-BeenThere: django-us...@googlegroups.com
Received: by 10.100.116.9 with SMTP id o9ls114855anc.7.gmail; Thu, 09 Jun
2011
 07:48:13 -0700 (PDT)
Received: by 10.101.7.31 with SMTP id k31mr362976ani.20.1307630893491;
   Thu, 09 Jun 2011 07:48:13 -0700 (PDT)
Received: by 10.101.7.31 with SMTP id k31mr362975ani.20.1307630893461;
   Thu, 09 Jun 2011 07:48:13 -0700 (PDT)
Received: from mail-yw0-f46.google.com (mail-yw0-f46.google.com[209.85.213.46])
   by gmr-mx.google.com with ESMTPS id
v1si1570130anh.2.2011.06.09.07.48.12
   (version=TLSv1/SSLv3 cipher=OTHER);
   Thu, 09 Jun 2011 07:48:12 -0700 (PDT)
Received-SPF: neutral (google.com: 209.85.213.46 is neither permitted nor
denied by best guess record for domain of f...@foxwhisper.co.uk)
client-ip=209.85.213.46;
Received: by mail-yw0-f46.google.com with SMTP id 9so833061ywe.19
   for ; Thu, 09 Jun 2011 07:48:12 -0700
(PDT)
Received: by 10.236.181.169 with SMTP id l29mr1090732yhm.447.1307630892199;
   Thu, 09 Jun 2011 07:48:12 -0700 (PDT)
Received: from mail-yx0-f177.google.com
(mail-yx0-f177.google.com[209.85.213.177])
   by mx.google.com with ESMTPS id k10sm874342yhj.64.2011.06.09.07.48.11
   (version=SSLv3 cipher=OTHER);
   Thu, 09 Jun 2011 07:48:12 -0700 (PDT)
Received: by yxk30 with SMTP id 30so740913yxk.8
   for ; Thu, 09 Jun 2011 07:48:11 -0700
(PDT)
MIME-Version: 1.0
Received: by 10.151.155.11 with SMTP id h11mr1967329ybo.146.1307630891276;
 Thu, 09 Jun 2011 07:48:11 -0700 (PDT)
Received: by 10.151.6.19 with HTTP; Thu, 9 Jun 2011 07:48:11 -0700 (PDT)
X-Originating-IP: [86.155.47.221]
In-Reply-To: <
8e880184-f1b4-4eb7-b1d8-0ae7cbf51...@r2g2000vbj.googlegroups.com>
References: <
46a83e65-5c63-4622-abc7-2e7c48235...@u26g2000vby.googlegroups.com>
   
   <4deffd2d.6040...@memset.com>
   
   
   <200b70dc-b8bb-4dac-9eb6-7cbcac34f...@u26g2000vby.googlegroups.com>
   <8e880184-f1b4-4eb7-b1d8-0ae7cbf51...@r2g2000vbj.googlegroups.com>
Date: Thu, 9 Jun 2011 15:48:11 +0100
Message-ID: 
Subject: Re: VERY cheap django hosting?
From: "Cal Leeming [Simplicity Media Ltd]" <
cal.leem...@simplicitymedi

Re: Deprecation policy for IE6

2011-06-09 Thread Javier Guerra Giraldez 
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" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: [] Re: Deprecation policy for IE6

2011-06-09 Thread Richard Bronosky 
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:
> 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: 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 support footprint for the
>>> Admin at "modern browsers" + IE>7.
>>>
>>> * contrib.admin is contrib, and thus not covered by Django's
>>> deprecation policy
>>>
>>> * This isn't a change which affects any other frontend product built
>>> with Django. The only audience this affects is users of the admin. I
>>> think it's reasonable to require administrative users to have IE7 if
>>> all they have is IE.
>>>
>>> The admin is already using the HTML5 doctype (see
>>> https://groups.google.com/d/topic/django-developers/wJ9dnUDHUVI/ for
>>> background), but not any of the new HTML5 elements.
>>>
>>> This change would mainly open up the ability to use PNGs and remove
>>> hacks and workarounds from admin CSS/HTML
>>>
>>> Any objections?
>>
>>Hearty +1 from me, for purely pragmatic reasons. In 2011, IE6 support is
>>simply an unreasonable burden to place on volunteer front-end
>>development work, IMHO. It's hard enough getting front-end work done
>>without tripling (quadrupling? more?) the pain factor like that. In my
>>mind, asking front-end developers to support IE6 is roughly similar to
>>asking Python devs to support Python 1.5, perhaps not in terms of usage,
>>but in terms of the additional development pain.
>>
>>I think it needs to be stated clearly that the effective choice is
>>between maintaining IE6 support and making major improvements to the
>>admin. If someone wants to argue that admin IE6 support should be
>>maintained for another release, they should acknowledge that the
>>implication is that there probably won't be significant upgrades to the
>>admin UI for at least that long.
>>
>>If there are Django deployments whose administrators really can't use
>>any browser other than IE6, Django 1.3 will be around as long as they
>>need it. It's not a reasonable tradeoff for that (frankly somewhat
>>ridiculous - IE6 is how many years old now?) edge case to continue to
>>hold the rest of the community hostage.
>>
>>Carl
>>
>>--
>>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 
>>django-developers+unsubscr...@googlegroups.com.
>>For more options, visit this group at 
>>http://groups.google.com/group/django-developers?hl=en.
>>
>
> --
> 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 
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/django-developers?hl=en.
>
>



-- 
.!# RichardBronosky #!.

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Better error message for django.core.urlresolvers.reverse

2011-06-09 Thread tomv 
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 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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

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

2011-06-09 Thread Russell Keith-Magee 
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 Magee %-)

On Thu, Jun 9, 2011 at 10:51 PM, Cal Leeming [Simplicity Media Ltd]
 wrote:
> 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
> Subject: Re: Re: VERY cheap django hosting?
> To: cal.leem...@simplicitymedialtd.co.uk
>
>
> The user d...@wildpalmsresources.com does not accept mail from your address.
>
> The headers of the message sent from your address are shown below:
>
> From django-users+bnccpw99b_xahcuuspvbboez52...@googlegroups.com Thu Jun 09
> 09:48:45 2011
> Received: from gator271.hostgator.com ([184.173.199.247]:46842)
>        by terminator.websitewelcome.com with esmtps (TLSv1:AES256-SHA:256)
>        (Exim 4.69)
>        (envelope-from
> )
>        id 1QUgXN-0001HT-R6
>        for d...@wildpalmsresources.com; Thu, 09 Jun 2011 09:48:45 -0500
> Received: from mail-gx0-f184.google.com ([209.85.161.184]:58910)
>        by gator271.hostgator.com with esmtps (TLSv1:RC4-SHA:128)
>        (Exim 4.69)
>        (envelope-from
> )
>        id 1QUgXP-0001kG-Lm
>        for d...@wildpalms.com; Thu, 09 Jun 2011 09:48:47 -0500
> Received: by gxk20 with SMTP id 20sf2618476gxk.11
>        for ; Thu, 09 Jun 2011 07:48:44 -0700 (PDT)
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
>        d=googlegroups.com; s=beta;
>        h=domainkey-signature:x-beenthere:received-spf:mime-version
>         :x-originating-ip:in-reply-to:references:date:message-id:subject
>         :from:to:x-original-sender:x-original-authentication-results
>         :reply-to:precedence:mailing-list:list-id:x-google-group-id
>         :list-post:list-help:list-archive:sender:list-subscribe
>         :list-unsubscribe:content-type;
>        bh=TSoLt/dYwGgASKftzrlR7U3iL0mbFxNANgwdwEnvFLo=;
>        b=Sxh489zJCOg5ByM45Fw8DTzbo6+xEFqX4iffWNOKnkSyjylUrkt+n3ta69dvRkb4k+
>         HIQtyKOmX7UQfIJSRJ6r9T6Up8DAFLRHs4CgKUmQ2bY5GiOsNCf0h+btZy8UeQWHn/Vy
>         1d+FfQwsruLyUXBvDjceJ/UxGTqViIvtrgdhI=
> DomainKey-Signature: a=rsa-sha1; c=nofws;
>        d=googlegroups.com; s=beta;
>        h=x-beenthere:received-spf:mime-version:x-originating-ip:in-reply-to
>         :references:date:message-id:subject:from:to:x-original-sender
>         :x-original-authentication-results:reply-to:precedence:mailing-list
>         :list-id:x-google-group-id:list-post:list-help:list-archive:sender
>         :list-subscribe:list-unsubscribe:content-type;
>        b=p8vZwyQM1+NQB7IUf35DhbU8sSvauvtINOf/oCAUEfGdpgzzciu5Jxs9kD7TYiPNXq
>         Q2DtMKtfCysfH8tMlpufBmp3rg0ZF4GPUKWLRk2UKeIraV1sM6L483mAapUBey+4iXKd
>         IXxPx1qgvtKSHaE3K+YjrRAAPPdVr/vW/NzoI=
> Received: by 10.236.95.147 with SMTP id p19mr77010yhf.64.1307630920768;
>        Thu, 09 Jun 2011 07:48:40 -0700 (PDT)
> X-BeenThere: django-us...@googlegroups.com
> Received: by 10.100.116.9 with SMTP id o9ls114855anc.7.gmail; Thu, 09 Jun
> 2011
>  07:48:13 -0700 (PDT)
> Received: by 10.101.7.31 with SMTP id k31mr362976ani.20.1307630893491;
>        Thu, 09 Jun 2011 07:48:13 -0700 (PDT)
> Received: by 10.101.7.31 with SMTP id k31mr362975ani.20.1307630893461;
>        Thu, 09 Jun 2011 07:48:13 -0700 (PDT)
> Received: from mail-yw0-f46.google.com (mail-yw0-f46.google.com
> [209.85.213.46])
>        by gmr-mx.google.com with ESMTPS id
> v1si1570130anh.2.2011.06.09.07.48.12
>        (version=TLSv1/SSLv3 cipher=OTHER);
>        Thu, 09 Jun 2011 07:48:12 -0700 (PDT)
> Received-SPF: neutral (google.com: 209.85.213.46 is neither permitted nor
> denied by best guess record for domain of f...@foxwhisper.co.uk)
> client-ip=209.85.213.46;
> Received: by mail-yw0-f46.google.com with SMTP id 9so833061ywe.19
>        for ; Thu, 09 Jun 2011 07:48:12 -0700
> (PDT)
> Received: by 10.236.181.169 with SMTP id l29mr1090732yhm.447.1307630892199;
>        Thu, 09 Jun 2011 07:48:12 -0700 (PDT)
> Received: from mail-yx0-f177.google.com (mail-yx0-f177.google.com
> [209.85.213.177])
>        by mx.google.com with ESMTPS id k10sm874342yhj.64.2011.06.09.07.48.11
>        (version=SSLv3 cipher=OTHER);
>        Thu, 09 Jun 2011 07:48:12 -0700 (PDT)
> Received: by yxk30 with SMTP id 30so740913yxk.8
>        for ; Thu, 09 Jun 2011 07:48:11 -0700
> (PDT)
> MIME-Version: 1.0
> Received: by 10.151.155.11 with SMTP id h11mr1967329ybo.146.1307630891276;
>  Thu, 09 Jun 2011 07:48:11 -0700 (PDT)
> Received: by 10.151.6.19 with HTTP; Thu, 9 Jun 2011 07:48:11 -0700 (PDT)
> X-Originating-IP: [86.155.47.221]
> In-Reply-To:
> <8e880184-f1b4-4eb7-b1d8-0ae7cbf51...@r2g2000vbj.googlegroups.com>
> Re

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

2011-06-09 Thread Cal Leeming [Simplicity Media Ltd] 
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 example, the
> django-users moderators can be reached at
> django-users+ow...@googlegroups.com.
>
> Yours,
> Russ Magee %-)
>
> On Thu, Jun 9, 2011 at 10:51 PM, Cal Leeming [Simplicity Media Ltd]
>  wrote:
> > 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
> > Subject: Re: Re: VERY cheap django hosting?
> > To: cal.leem...@simplicitymedialtd.co.uk
> >
> >
> > The user d...@wildpalmsresources.com does not accept mail from your
> address.
> >
> > The headers of the message sent from your address are shown below:
> >
> > From django-users+bnccpw99b_xahcuuspvbboez52...@googlegroups.com Thu Jun
> 09
> > 09:48:45 2011
> > Received: from gator271.hostgator.com ([184.173.199.247]:46842)
> >by terminator.websitewelcome.com with esmtps
> (TLSv1:AES256-SHA:256)
> >(Exim 4.69)
> >(envelope-from
> > )
> >id 1QUgXN-0001HT-R6
> >for d...@wildpalmsresources.com; Thu, 09 Jun 2011 09:48:45 -0500
> > Received: from mail-gx0-f184.google.com ([209.85.161.184]:58910)
> >by gator271.hostgator.com with esmtps (TLSv1:RC4-SHA:128)
> >(Exim 4.69)
> >(envelope-from
> > )
> >id 1QUgXP-0001kG-Lm
> >for d...@wildpalms.com; Thu, 09 Jun 2011 09:48:47 -0500
> > Received: by gxk20 with SMTP id 20sf2618476gxk.11
> >for ; Thu, 09 Jun 2011 07:48:44 -0700 (PDT)
> > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> >d=googlegroups.com; s=beta;
> >h=domainkey-signature:x-beenthere:received-spf:mime-version
> > :x-originating-ip:in-reply-to:references:date:message-id:subject
> > :from:to:x-original-sender:x-original-authentication-results
> > :reply-to:precedence:mailing-list:list-id:x-google-group-id
> > :list-post:list-help:list-archive:sender:list-subscribe
> > :list-unsubscribe:content-type;
> >bh=TSoLt/dYwGgASKftzrlR7U3iL0mbFxNANgwdwEnvFLo=;
> >
>  b=Sxh489zJCOg5ByM45Fw8DTzbo6+xEFqX4iffWNOKnkSyjylUrkt+n3ta69dvRkb4k+
> >
> HIQtyKOmX7UQfIJSRJ6r9T6Up8DAFLRHs4CgKUmQ2bY5GiOsNCf0h+btZy8UeQWHn/Vy
> > 1d+FfQwsruLyUXBvDjceJ/UxGTqViIvtrgdhI=
> > DomainKey-Signature: a=rsa-sha1; c=nofws;
> >d=googlegroups.com; s=beta;
> >
>  h=x-beenthere:received-spf:mime-version:x-originating-ip:in-reply-to
> > :references:date:message-id:subject:from:to:x-original-sender
> >
> :x-original-authentication-results:reply-to:precedence:mailing-list
> >
> :list-id:x-google-group-id:list-post:list-help:list-archive:sender
> > :list-subscribe:list-unsubscribe:content-type;
> >
>  b=p8vZwyQM1+NQB7IUf35DhbU8sSvauvtINOf/oCAUEfGdpgzzciu5Jxs9kD7TYiPNXq
> >
> Q2DtMKtfCysfH8tMlpufBmp3rg0ZF4GPUKWLRk2UKeIraV1sM6L483mAapUBey+4iXKd
> > IXxPx1qgvtKSHaE3K+YjrRAAPPdVr/vW/NzoI=
> > Received: by 10.236.95.147 with SMTP id p19mr77010yhf.64.1307630920768;
> >Thu, 09 Jun 2011 07:48:40 -0700 (PDT)
> > X-BeenThere: django-us...@googlegroups.com
> > Received: by 10.100.116.9 with SMTP id o9ls114855anc.7.gmail; Thu, 09 Jun
> > 2011
> >  07:48:13 -0700 (PDT)
> > Received: by 10.101.7.31 with SMTP id k31mr362976ani.20.1307630893491;
> >Thu, 09 Jun 2011 07:48:13 -0700 (PDT)
> > Received: by 10.101.7.31 with SMTP id k31mr362975ani.20.1307630893461;
> >Thu, 09 Jun 2011 07:48:13 -0700 (PDT)
> > Received: from mail-yw0-f46.google.com (mail-yw0-f46.google.com
> > [209.85.213.46])
> >by gmr-mx.google.com with ESMTPS id
> > v1si1570130anh.2.2011.06.09.07.48.12
> >(version=TLSv1/SSLv3 cipher=OTHER);
> >Thu, 09 Jun 2011 07:48:12 -0700 (PDT)
> > Received-SPF: neutral (google.com: 209.85.213.46 is neither permitted
> nor
> > denied by best guess record for domain of f...@foxwhisper.co.uk)
> > client-ip=209.85.213.46;
> > Received: by mail-yw0-f46.google.com with SMTP id 9so833061ywe.19
> >for ; Thu, 09 Jun 2011 07:48:12
> -0700
> > (PDT)
> > Received: by 10.236.181.169 with SMTP id
> l29mr1090732yhm.447.1307630892199;
> >Thu, 09 Jun 2011 07:48:12 -0700 (PDT)
> > Received: from mail-yx0-f177.google.com (mail-yx0-f177.google.com
> > [209.85.213.177])
> >by mx.google.com with ESMTPS id
> k10sm874342yhj.64.2011.06.09.07.48.11
> >(version=SSLv3 cipher=OTHER);
> >Thu, 09 Jun 2011 07:48:12 -0700 (PDT)
> > Received: by yxk30 with SMTP id 30so740913yxk.8
> >for ; Thu, 09 Jun 2011 07:48:11
> -0700
> > (PDT)
> > MIME-Version: 1.0
> > Received: by 10.151.155.11 with S

Re: Deprecation policy for IE6

2011-06-09 Thread Florian Apolloner 
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 ;)

Cheers,
Florian

1: 
http://gmailblog.blogspot.com/2011/06/our-plans-to-support-modern-browsers.html

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Django Error Display Page

2011-06-09 Thread Valentin Golev 
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 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 could be better, but I'd need to see a concrete 
> proposal outlining the problems and how the improvements address these 
> problems. Right now this feels like a case of fixing what ain't broken.
>
> I
>
>
>
>
>
>
>
> On Wednesday, June 8, 2011 at 6:10 PM, Graham King wrote:
> > This ticket might be a part of what you're looking for:
> >https://code.djangoproject.com/ticket/11834
> > It proposes to dim the django parts of the stacktrace, so the code
> > which most likely caused the error stands out better, which is
> > certainly something I'd love to see.
>
> > There's some similar ideas discussed here:
> >https://groups.google.com/group/django-developers/browse_frm/thread/b...
>
> > On 8 June 2011 03:50, Mateusz Harasymczuk  > (mailto:m...@harasymczuk.pl)> 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 at the top yellow background.
> > > - (Hide or fold) django traceback entries
> > > When I have a problem I have to scroll down (passing django calls) few 
> > > pages
> > > until I am able to find which MY action caused an error.
> > > I know looking at django callback may be useful, but in my case, hardly
> > > ever, and probably for newcommers also.
> > > I am imagining this like that:
> > > At the top of the error page, there are tabs.
> > > Summary, Traceback, Request, Settings, and copy-paste view (feedback 
> > > view).
> > > Summary tab, contains this yellow background information with PYTHON_PATH
> > > initially folded, and traceback filtered out to include only information
> > > from project not calls from django itself.
> > > Traceback, request and settings tabs as it is right now, but separated for
> > > easy of view.
> > > copy-paste (feedback) - a standardize view for easy of copy-and-paste to 
> > > the
> > > Internet message boards, groups and so on...
> > > It would need a template refactor and some more js involved, should not 
> > > be a
> > > hard thing to do.
> > > I read that there is a plan to redesign an error page, but since then, 
> > > those
> > > modifications should do the job.
> > > What do you think?
> > > --
> > > Matt Harasymczuk
> > >http://www.matt.harasymczuk.pl
>
> > > --
> > > 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/-/b0pKaV9JR2gzXzRK.
> > > To post to this group, send email to django-developers@googlegroups.com 
> > > (mailto:django-developers@googlegroups.com).
> > > To unsubscribe from this group, send email to
> > > django-developers+unsubscr...@googlegroups.com 
> > > (mailto:django-developers+unsubscr...@googlegroups.com).
> > > For more options, visit this group at
> > >http://groups.google.com/group/django-developers?hl=en.
>
> > --
> > 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 
> > (mailto:django-developers@googlegroups.com).
> > To unsubscribe from this group, send email to 
> > django-developers+unsubscr...@googlegroups.com 
> > (mailto:django-developers+unsubscr...@googlegroups.com).
> > For more options, visit this group 
> > athttp://groups.google.com/group/django-developers?hl=en.

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.