Re: feedback on full atom feed support

On 10/08/2007, at 9:27 AM, Rob Hudson wrote: > I know the basics of what Atom is and what AtomPub is (but not quite > clear on where REST and full AtomPub differ or relate -- they sound > like they have a lot of overlap where maybe REST is at the HTTP level > and AtomPub is more on implementation

Re: Case-insensitive URLS (was: usability issues)

On Mon, 2007-08-06 at 09:49 +0400, Alex Nikolaenkov wrote: [...] > > (B) Reopening tickets because you disagree with the resolution is also > > quite impolite. Bringing the issue here is the right way to go, but > > leave the ticket closed unless you can convince us to rep-open it. > I never

Re: Request data encoding

On Sat, 2007-08-11 at 13:16 +1000, Malcolm Tredinnick wrote: [...] > Receiving genuinely bad/invalid data is not uncommon either, as is > obvious as soon as you start running a really anal comment sanitisation > feature or looking at uploads from corporate systems. Trying to silently > change the

Re: Request data encoding

On Thu, 2007-08-02 at 19:33 -0500, Jacob Kaplan-Moss wrote: > On 8/2/07, Simon Willison <[EMAIL PROTECTED]> wrote: > > This is a totally ridiculous flaw with the HTTP spec - you literally > > have no reliable way of telling what encoding a request coming in to > > your site uses, since you can't

Re: Request data encoding

On Thu, 2007-08-02 at 15:14 -0700, Craig Ogg wrote: > On 8/2/07, ludvig.ericson <[EMAIL PROTECTED]> wrote: > > On Aug 2, 11:02 pm, Gábor Farkas <[EMAIL PROTECTED]> wrote: > > > Jacob Kaplan-Moss wrote: > > > > On 8/2/07, Daniel Brandt <[EMAIL PROTECTED]> wrote: > > > >> I am recieving POST-data

Re: input type=hidden for newforms

On Fri, 2007-08-10 at 07:27 +, james_027 wrote: > Hi, > > this might sound stupid but is there a good reason for adding > HiddenField for newforms? A hidden input element is a widget, not a field. It's a render-time property, not a semantic feature of the data. We already have

Re: Cleaning up memcached connections

This rang some bells about a problem we'd had with memcached, so I asked Dave St. Germain (our goto guy for issues like this). Here's what he had to say: I think this is the wrong fix for the problem. memcached connections are supposed to be persistent, not torn down after every

Search API, another way ?

Hello, In a recent project I had to use a full text search engine (wow!) well I sticked with postgresql/tsearch2 [1] because it's easy and avaible in shared hosting (providing there is postgresql). My own implementation is a bit dirty, it works but well not nice implementation. I will explain

Experimental LIMIT/Offset for Sql server

For http://code.djangoproject.com/ticket/5062 I add a experimental support for LIMIT/Offset emulation for Sql Server 2000 and lower and Sql Server 2005+. Kudos for the people that work in the oracle implementation so I can copy & paste ;). However I'm stuck because can't run all the testcases

Re: Maybe we need more triagers? Or something else?

[EMAIL PROTECTED] wrote: > Another thing to possibly consider is putting out some general > guidelines about the thought process the developers go through to > evaluate the tickets with design decisions needed. In other words, > how do the developers make the decision to include/exclude

Re: Maybe we need more triagers? Or something else?

Another thing to possibly consider is putting out some general guidelines about the thought process the developers go through to evaluate the tickets with design decisions needed. In other words, how do the developers make the decision to include/exclude something? How do they decide to accept

Cleaning up memcached connections

Hi all -- We've noticed that in a few cases Django under mod_python can leave dangling connections to memcached open. We've had trouble tracking down the circumstances under which this happens, but when it does it can lead to memcached servers hitting their connection limits, which means caching

Re: feedback on full atom feed support

I've been watching the development with interest. I'm probably your user #1 with curiosity that might lead to user #2. I know the basics of what Atom is and what AtomPub is (but not quite clear on where REST and full AtomPub differ or relate -- they sound like they have a lot of overlap where

Re: Amazon S3 Integration

On Aug 8, 8:12 pm, "Jay Parlar" <[EMAIL PROTECTED]> wrote: > On 8/8/07, John-Scott <[EMAIL PROTECTED]> wrote: > > > > > > > Hello all, > > > I'm trying to integrate S3 support into my Django app using > >http://code.djangoproject.com/wiki/AmazonSimpleStorageServicefor > > now. > > > I would

Re: GSoC 2007 Status Update VI: Django REST interface

On 8/6/07, David Larlet <[EMAIL PROTECTED]> wrote: > * What about additional pages like: create form, update form, delete > confirmation and so on? I've just noticed the get_create_form at the > end of the TemplateResponder but how can I redirect to this function? > (I haven't seen how to do this

Re: Django Instead of Rails

When the hell did "pragmatic" become a buzz-word? Oh god, I must be behind the times, that's so ilpragmatic of me. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group,

Re: input type=hidden for newforms

On 8/10/07, james_027 <[EMAIL PROTECTED]> wrote: > Thanks for revealing this to me. > can I apply the widget = HiddenInput to any field? Please take this question to django-users (or, better yet, read the documentation). Django-dev is for discussion of developing Django itself, not usage

Re: Django Instead of Rails

Hey Matt -- Thanks for the link; it's certainly a good read. However, in the future please post things of this nature to django-users; django-dev is used to discuss the development of Django itself, not user-level things. Thanks! Jacob --~--~-~--~~~---~--~~ You

Re: contrib.auth.models.User and related_name on 'groups' attribute

On Aug 9, 8:46 pm, Collin Grady <[EMAIL PROTECTED]> wrote: > group_obj.user_set.all() /is/ available :) Doh. I forgot about the _set thing... Moral of the story: don't code if you've not slept for 36 hours -- Richard --~--~-~--~~~---~--~~ You received this

Re: Maybe we need more triagers? Or something else?

I like the idea of the voting app - there are several tickets I would +1 already ;) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

Re: input type=hidden for newforms

Hi SmileyChris > > A Widget (not Field) is responsible for the display - and there's a > HiddenInput widget already. Thanks for revealing this to me. can I apply the widget = HiddenInput to any field? cheers, james --~--~-~--~~~---~--~~ You received this

Re: input type=hidden for newforms

On Aug 10, 7:27 pm, james_027 <[EMAIL PROTECTED]> wrote: > Hi, > > this might sound stupid but is there a good reason for adding > HiddenField for newforms? A Widget (not Field) is responsible for the display - and there's a HiddenInput widget already.

input type=hidden for newforms

Hi, this might sound stupid but is there a good reason for adding HiddenField for newforms? cheers, james --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send

Re: Maybe we need more triagers? Or something else?

Evening all, This is great - the trac is really ticking over, which indicates a LOT of interest. I've been triaging for a while now, and the incoming tickets have increased notably in the last few months. However, I try to spend 20 minutes a day or so, and I manage to churn through a sizable