Setting choices on TimeFields broken in 1.2?

I'd appreciate it if anyone could take a look at this ticket as I feel that it's been closed in error: http://code.djangoproject.com/ticket/15536. Thanks! -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email

Re: Customizable Serialization

On Sun, Mar 6, 2011 at 2:41 PM, Vivek Narayanan wrote: > @Sebastien: I got your point about using a dict as an intermediate > structure and the use of recursion, and I looked at your > implementation which is somewhat similar to what I have in mind. > > Well, here is a list of

Re: Customizable Serialization

@Sebastien: I got your point about using a dict as an intermediate structure and the use of recursion, and I looked at your implementation which is somewhat similar to what I have in mind. Well, here is a list of deliverables for the project: • Investigate existing structure of the serializer,

Re: Brute force attacks

Hi Russell, here are my thoughts on your points: 1. I do believe there should be something enabled by default. Some security conscious developers will go out of there way to integrate a third party plugin but I believe (and I may be wrong) that many developers just assume the out-of-the-box

Re: the new SELECT DISTINCT query in 1.3 rc1, and how to turn it off

I've created a ticket for this http://code.djangoproject.com/ticket/15559 Also, if someone else is stumbling on this problem, I went around it by providing a custom QuerySet class for my method, which has an overridden distinct method, that returns itself. -- You received this message

Re: Storing language in session/cookie

If I understand the middleware correctly, session cookie is created only when the session itself is modified, unless SESSION_SAVE_EVERY_REQUEST is True. So, after user language is set but before user authentication there could be only one, language cookie. I think that

Re: Brute force attacks

On Sat, Mar 5, 2011 at 5:56 AM, Rohit Sethi wrote: > Hi all, I wanted to revisit a key security discussion. Brute force > attacks are the 7th most prevalent attack by number of incidents in > the Web Hacking Incidents Database (http://projects.webappsec.org/w/ >

Re: the new SELECT DISTINCT query in 1.3 rc1, and how to turn it off

On Mar 5, 7:29 am, Karen Tracey wrote: > It's probably best if you open a ticket in trac > (http://code.djangoproject.com/newticket) for this. I can't think offhand how > to solve both the problem that changeset fixed and the one you are > encountering > If Django ORM