Hi,
I've spotted what I think is a bug. See ticket #7651.
Basically, there is a duplicate entry in the file list (i.e.
request.FILES.getlist(file_input_name)), when using the jQuery
MultiFile plugin. It used to work just fine before #2070 was merged.
Cheers,
Julien
[1]
On Tue, Jul 1, 2008 at 2:40 PM, David Cramer <[EMAIL PROTECTED]> wrote:
> I haven't read this over in too much detail yet (I just auto ignore
> the 10k trac emails about it :P) but a few concerns:
I haven't read the rest of your email yet, but I think the answers are
"77" and "see a doctor if
On Tue, Jul 1, 2008 at 4:40 PM, David Cramer <[EMAIL PROTECTED]> wrote:
> - Is there a setting (e.g. settings.py) to restrict the maximum file
> size in an upload?
FILE_UPLOAD_MAX_MEMORY_SIZE
--~--~-~--~~~---~--~~
You received this message because you are
I haven't read this over in too much detail yet (I just auto ignore
the 10k trac emails about it :P) but a few concerns:
- Is there a setting (e.g. settings.py) to restrict the maximum file
size in an upload?
- For test suites couldn't you while (xrange(n)) pass /dev/random or
whatever to make a
I mentioned some issues to Michael Axiak a while back, and he said
he'd get to them but that I should post them on the 2070 ticket. I
forgot to post them, so he might've missed it before it was committed
to SVN. I made a new ticket for them:
http://code.djangoproject.com/ticket/7593
A quick
On Sat, Jun 28, 2008 at 5:32 AM, Russell Keith-Magee
<[EMAIL PROTECTED]> wrote:
[...]
> 1) The confusion between 0/1 and False/True on BooleanField
>
> This is an issue with MySQL support that has existed for some time.
> Strictly, it's only an issue with the test suite because 0 is not
>
On Fri, Jun 27, 2008 at 5:41 PM, David Reynolds
<[EMAIL PROTECTED]> wrote:
> Running with mysql backend created a few errors (I'm not sure if
> they're related so I've attached them in full, hope that's ok):
Hi David,
Thanks for doing this testing, but from the look of it, these errors
are all
Full test pass on Ubuntu Hardy Heron, with python 2.5, and sqlite3. I
also did some general testing of uploading files, which were
succesful, and I was able to observe large uploads going to my /tmp
dir.
On Jun 27, 4:41 am, David Reynolds <[EMAIL PROTECTED]>
wrote:
> Jacob,
>
> Hopefully this
Jacob,
Hopefully this will be of some use..
On 26 Jun 2008, at 8:14 pm, Jacob Kaplan-Moss wrote:
> * Running the test suite -- coverage is quite good now, but I've only
> been able to test on a limited set of OSes/DBs. Looks elsewhere just
> in case, very good.
I've just checked the branch
On Jun 26, 8:14 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
> Documentation of the new features is can be found in
> ``docs/upload_handling.txt``
> orhttp://code.djangoproject.com/git/?p=django;a=blob_plain;f=docs/uploa
Just a small thing:
"""
Like any data supplied by the user, you
Hey Jacob,
FYI: Our environment isn't that bizarre (Apache/Debian), but we've been
running patch #2070 in production on Pownce for a couple weeks now (we
actually ran a back-ported version of #2070 on 0.96 before we moved to
trunk). It's been working beautifully, and has really improved
On Thu, Jun 26, 2008 at 3:14 PM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
>
> Hi folks --
>
> As far as I'm concerned, #2070, adding large streaming uploads, is
> done. I'd like to get some public kicking-of-the-tires before I push
> the change to trunk (which won't happen before Tuesday: I'm
Hi folks --
As far as I'm concerned, #2070, adding large streaming uploads, is
done. I'd like to get some public kicking-of-the-tires before I push
the change to trunk (which won't happen before Tuesday: I'm taking a
long weekend off).
You can get the code either from my git repository
13 matches
Mail list logo
