o be hinting at is a count of years, which is
> definitely too particular for Django inclusion. would make a perfect
> third party app though!
Further, age (for people, at least) is measured in different ways
around the world. See for example https://en.wikipedia.org/wiki/East_As
ian_ag
Just bumping this - can anyone suggest what the next steps should be?
It'd be nice to get it fixed for 1.4.
Thanks,
Jamie
On Nov 28, 5:59 pm, Jamie Matthews wrote:
> > Yeah, that implementation seems preferable. What was the reason for backing
> > it out?
>
> Not
> Yeah, that implementation seems preferable. What was the reason for backing
> it out?
Not sure. What would be the procedure for getting this changed? Open a
new ticket, I assume?
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to
> 2. Improve the default HTTP HEAD handler by ensuring it has a blank body,
> as this is the expectation of a response to a HEAD request. Also, there
> should be consideration for the GET handler not existing, which should
> result in a 405. The code appears to assume it exists, which would result
asy to make
backward-compatible and would be VERY helpful.
My best,
Jamie
On 27 November 2010 23:55, Kevin Renskers wrote:
> Hi,
>
> I'd like to make a suggestion about the build in comments framework.
> Right now, even though you can write your own extension to the
> comments
Hello Peter,
I believe you can catch the instance in a middleware class. I'm sure a
better developer or someone on the core team can explain better than me.
Jamie Rumbelow
-Original Message-
From: django-developers@googlegroups.com
[mailto:django-develop...@googlegroups.com] On B
> I've got some time for testing and results are that without DEBUG is no
> memory overhead. But I still wonder that if I delete connection.queries
> in every cycle, why memory consumption still grows. What other
> structures are created in DEBUG mode? Simple 'grep DEBUG' showed nothing
> really i
nse to join
> the comments_comment table on itself.
This looks very much like the same behaviour as I reported in ticket
#3906.
Jamie
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers&quo
