Re: Fixing middleware/view decorator handling of content iterators

Hi, Sorry for the volume of messages, but I had one more note to add. ;) On Sat, Feb 20, 2010 at 03:46:52PM -0500, Forest Bond wrote: > Here are the use cases that have been identified: > > 1. A content iterator was passed for no apparent reason. The view could just >as easily have

Re: Fixing middleware/view decorator handling of content iterators

Hi, On Sat, Feb 20, 2010 at 03:46:52PM -0500, Forest Bond wrote: > Then there is the question of how to trigger handling as a streaming response. > Either we require a view to explicitly request it by using a > StreamingHttpResponse instead of a normal HttpResponse, or we assume that if > the >

Re: Fixing middleware/view decorator handling of content iterators

Hi, On Thu, Feb 18, 2010 at 08:40:55PM -0800, Tai Lee wrote: > See also #7581, which has a patch that I have been using in my local > Django branch for over a year without issue. My use case is that I > need to generate large amounts of data in CSV format and stream the > response to avoid

Re: inlineformset_factory bug

On Sat, Feb 20, 2010 at 11:09 PM, Alexandru Nedelcu wrote: > On Feb 20, 1:54 pm, Russell Keith-Magee > wrote: >> Django is currently in bugfix mode, but this could be a candidate >> feature for Django 1.3. In order for this to happen, it needs to be >>

Re: inlineformset_factory bug

On Feb 20, 1:54 pm, Russell Keith-Magee wrote: > "if form.errors" will work fine - as long as you're using a form. It > will also work fine if you're iterating over a formset to get the > consituent forms. There are also instances where I want to have global errors (i.e.

Re: admin javacripts

> > > var $jQD = jQuery.noConflict(); > > > And somebody else includes this: > > > > Then Django's version of jQuery would be available to all widgets as > $jQD and the other jQuery version would still be available as $ or > jQuery. This kind of sounds nice, but perhaps some sort of

Re: inlineformset_factory bug

On Sat, Feb 20, 2010 at 3:30 PM, Alexandru Nedelcu wrote: > Hi, > > I want to report a bug ... is here OK? The best place to report a bug is in our Trac instance. However, that said: > I have an InlineFormSet ... created like so ... > >    inlineformset_factory(MainModel,

Re: Per application default database?

2010/2/3 kmpm : > Hmm... strange. > I get a strange error when I tried to do this > Something about a django_content_type  relation which I don't have. > This probably happens when the "app" gets registerd in the auth > system. > Same error with both postgresql and

inlineformset_factory bug

Hi, I want to report a bug ... is here OK? I have an InlineFormSet ... created like so ... inlineformset_factory(MainModel, ChildModel, extra=1, exclude=('num',)) Trouble is in /var/lib/elf-lib/src/django/django/forms/formsets.py:269 in full_clean() ... for i in range(0,