Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Django developers
Home
+ new post
About this group
Join this group
Message from discussion 1.2 Proposal: django debug toolbar in contrib
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
David Cramer  
View profile  
 More options Aug 13 2009, 3:30 am
From: David Cramer <dcra...@gmail.com>
Date: Thu, 13 Aug 2009 00:30:35 -0700 (PDT)
Local: Thurs, Aug 13 2009 3:30 am
Subject: Re: 1.2 Proposal: django debug toolbar in contrib
Print | View thread | Show original | Report this message | Find messages by this author
Oh, and thats most likely my branch you're referring to Martin. I
implemented a lot of the panels, and went so far as adding crazy
monkey patching in some of them to catch some information I wanted.

http://github.com/dcramer/django-debug-toolbar/tree/master

On Aug 11, 11:38 am, Martin Maney <ma...@two14.net> wrote:

> On Tue, Aug 11, 2009 at 09:50:35AM -0500, Alex Gaynor wrote:
> > Right now django-debug-toolbar has a pretty stable panel interface and
> > I actually can't recall it changing since release.  A possibly more
> > interesting issue is that some of the debug information it get's is
> > somewhat of a hack, that is template data is gotten from monkey
> > patching Template.render, the SQL data is also a monkeypatch.

> Caching stats were another area where monkeypatching seemed to be the
> only alternative to an altered usage in one's source code.  Back when I
> spent some time using and extending parts of ddt the situation was as
> described here:

> http://wiki.github.com/mmaney/django-debug-toolbar/cache-panel-workar...

> That predates the discussion I had with Rob Hudson about another fellow's
> branch (can't recall whose offhand) which used a monkeypatch to add the
> necessary intercept to the cache object.  At one point I had hoped to
> bend Jacob's ear at PyCon about this, but I got to be too busy with
> other work and, in fact, never had time to drop in.  Plus I had read
> about how everyone was focusing on getting 1.1 out Real Soon Now and
> figured it wasn't the best time for it.  Months passed...


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google