Re: "needsinfo": resolution vs. triage stage

On Thu, 2011-02-24 at 19:17 -0800, Gabriel Hurley wrote: > In regards to #14702, which so far has been a universally favored > idea, there's one lingering issue: > > > Do we want to implement it as a resolution (i.e. you close a ticket as > "needsinfo" and the reporter reopens to provide the

Re: "needsinfo": resolution vs. triage stage

On Sat, Feb 26, 2011 at 5:43 PM, Julien Phalip wrote: > On Feb 24, 7:17 pm, Gabriel Hurley wrote: >> In regards to #14702 , which so >> far has been a universally favored idea, there's one lingering issue: >> >> Do

Re: The XMLField ticket

On Sun, Feb 27, 2011 at 3:31 AM, Jacob Kaplan-Moss wrote: > On Sat, Feb 26, 2011 at 11:47 AM, Paul McMillan wrote: >> We need to either deprecate it, provide some validation, or fix the >> docs to say it doesn't do anything. We can't fix the docs till we

Re: Customizable Serialization

On Thu, Feb 24, 2011 at 10:24 PM, Vivek Narayanan wrote: > Hi, > > I am Vivek Narayanan, an undergrad student at IIT, Varanasi in India > and am interested in participating in this year's SoC Hi Vivek, and thanks for your interest in the GSoC! > Problem > >

Re: Control json serialization

Hiya, thanks a lot for your response. So, using my approach (the json generation templates) is somewhat more or less ok then? I'd like to get involved but I'm just not really good at python and django, so I guess I will be mixing rather than fixing I'm afraid :) By putting json serialization to

Re: Control json serialization

On Sun, Feb 27, 2011 at 5:23 AM, Alexander Bolotnov wrote: > Is there a way to control json serialization in django? Simple code below > will return serialized object in json: ... > You can see it's serializing it in a way that you are able to re-create the > whole model,

Re: The XMLField ticket

On Sat, Feb 26, 2011 at 11:47 AM, Paul McMillan wrote: > We need to either deprecate it, provide some validation, or fix the > docs to say it doesn't do anything. We can't fix the docs till we have > a decision on this ticket. I say deprecate the field entirely. There isn't a

Re: A word about CSRF Protection and AJAX

I'll chime in as opposed to forcing the cookie where not strictly necessary. It makes caching harder, and means that many of the dumber caching systems out there won't cache it at all (some mobile operators, smaller ISPs in lower GDP countries, etc.). Pushing the cookie to make AJAX easier seems

Re: "needsinfo": resolution vs. triage stage

I'm also +1 for the close resolution. Fewer open tickets is a good thing! -Paul -- 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

Re: The XMLField ticket

On Sat, Feb 26, 2011 at 4:47 AM, Paul McMillan wrote: > Ticket #3094 needs a decision. > http://code.djangoproject.com/ticket/3094#comment:17 > > The quick summary: > > Once upon a time the XMLField accepted a schema and validated > documents against that. This hasn't been true

The XMLField ticket

Ticket #3094 needs a decision. http://code.djangoproject.com/ticket/3094#comment:17 The quick summary: Once upon a time the XMLField accepted a schema and validated documents against that. This hasn't been true since oldforms, yet the documentation continues to proclaim this. Now, XMLField is

Re: "needsinfo": resolution vs. triage stage

On Feb 24, 7:17 pm, Gabriel Hurley wrote: > In regards to #14702 , which so > far has been a universally favored idea, there's one lingering issue: > > Do we want to implement it as a resolution (i.e. you close a ticket as >