Re: registering unzipped files on the local disk

On Sun, 19 Jun 2011, francescortiz wrote: Faheem, In your post you write: "This works, but I traced through the code, and found that the code was using streaming, when clearly the optimal thing to do in this case would be to just copy the file from the temporary location to the permanent

registering unzipped files on the local disk

Hi, Can anyone help me with http://stackoverflow.com/questions/6386062/django-registering-unzipped-files-on-the-local-disk ? If you reply via email, please cc me. Thanks. Regards, Faheem. -- You received this message because you are subscribed to the Google

Re: using the stable api

Hi Malcolm, Thanks for the helpful reply. On Sat, 01 Aug 2009 12:24:29 +1000, Malcolm Tredinnick <malc...@pointy-stick.com> wrote: > On Fri, 2009-07-31 at 11:42 -0400, Faheem Mitha wrote: >> >> Hi everybody, >> >> I upgraded from somewhere around Dja

using the stable api

Hi everybody, I upgraded from somewhere around Django 1.0 to 1.0.2, and some things broke and had to be changed. In the following, f is an object of class 'django.core.files.uploadedfile.TemporaryUploadedFile'. I need to 1) Get the contents of the file corresponding to f. I had to change

appeal for help with #9232

Hi, Can anyone help with http://code.djangoproject.com/ticket/9232 ? Currently I don't even know if this problem is reproducible. If someone could solve it, or even indicate what was wrong, if anything, I'd be happy to pay for services rendered.

Re: streaming file uploads not working with Django 1.0

On Sat, 27 Sep 2008 01:56:53 -0400 (EDT), Faheem Mitha <[EMAIL PROTECTED]> wrote: > Hi, > > I just upgraded to Django 1.0, and I've just finished fixing all my unit > tests. However, streaming file uploads are still broken. The behaviour I'm > seeing is as follows: > &

streaming file uploads not working with Django 1.0

in /tmp appearing and growing in size as the upload progresses, as expected. Suggestions for debugging would be appreciated. Please CC me on any reply. Thanks. Sincerely, Faheem Mitha. class OldFileUpload(models.Model): upload_date

Re: Two Django visions running at once.

On Wed, 17 Sep 2008 13:21:50 -0700 (PDT), KillaBee <[EMAIL PROTECTED]> wrote: > Is it possible to have two versions of django running at the same time > on an Ubuntu server(9.0 and 1.0)? > It is taking to long to recode, and until I do I wanted It up and > running with the old version. > I got

Re: change file upload destination "on the fly" for tests

On Wed, 17 Sep 2008 14:42:40 -0400 (EDT), Faheem Mitha <[EMAIL PROTECTED]> wrote: > > Hi, > > I wrote some unit tests for file upload. since I didn't want the files in > the unit tests to be uploaded to the "official locaion", I changed the > upload

Re: unable to import Storage from django.core.files.storage into settings.py

On Thu, 18 Sep 2008 12:16:52 -0400, Marty Alchin <[EMAIL PROTECTED]> wrote: > > On Thu, Sep 18, 2008 at 11:55 AM, Faheem Mitha <[EMAIL PROTECTED]> wrote: >> Putting the following into my settings.py (checked for two different >> projects for Dango 1.0) >> >

unable to import Storage from django.core.files.storage into settings.py

Hi, Putting the following into my settings.py (checked for two different projects for Dango 1.0) from django.core.files.storage import Storage gives [EMAIL PROTECTED]:/var/django/hg$ python manage.py validate Error: Can't find the file 'settings.py' in the directory containing 'manage.py'.

Re: change file upload destination "on the fly" for tests

location dynamically, even using a file storage object. Faheem. > On Sep 17, 11:45 pm, Faheem Mitha <[EMAIL PROTECTED]> wrote: >> [This message has also been posted.] >> >> On Wed, 17 Sep 2008 20:14:54 -0700 (PD

Re: change file upload destination "on the fly" for tests

argument corresponds to the subdirectory where the file is placed. I could not understand the code, so this summary may be incorrect. Faheem. > On Sep 17, 11:00 pm, Faheem Mitha <[EMAIL PROTECTED]> wrote: >> >> Thanks for the

Re: change file upload destination "on the fly" for tests

[This message has also been posted.] On Wed, 17 Sep 2008 18:40:12 -0700 (PDT), akonsu <[EMAIL PROTECTED]> wrote: > hello, > upload_to can take a callable, which can be used to change your > files' location. > konstantin Thanks for the suggestion. However, upload_to is appended to

Re: change file upload destination "on the fly" for tests

Hi Lisa, Thanks for the reply. On Wed, 17 Sep 2008 14:28:59 -0700, Lisa Dusseault <[EMAIL PROTECTED]> wrote: > --=_Part_17268_18727299.1221686939556 > Content-Type: text/plain; charset=ISO-8859-1 > > I have a bunch of unit tests that do file upload too. E.g.: > > def testBasics(self):

change file upload destination "on the fly" for tests

Hi, I wrote some unit tests for file upload. since I didn't want the files in the unit tests to be uploaded to the "official locaion", I changed the upload location by reassiging MEDIA_ROOT to something else, '/tmp' in this case. With an upgrade to Django 1.0, this method no longer works.

Re: wsgi in django for hgwebproxy

On Fri, 22 Aug 2008, Dirkjan Ochtman wrote: > Faheem Mitha wrote: >> * >> self.env = req.META where req is a django request (see__init__ of >

wsgi in django for hgwebproxy

Hello everyone, The version control system mercurial (hg) has some functionality to allow its repositories to be viewed via the web. However, it does not have a builtin authentication system. I'm trying to get a setup working where I can put Django in front. Jesper Noehr of bitbucket.org

Re: using Django unit test framework with existing production db

On Fri, 28 Mar 2008 17:10:28 -0400 (EDT), Jeff Gentry <[EMAIL PROTECTED]> wrote: >> Is there some graceful way to have the Django unit test framework >> access the "production database" for certain tests as opposed to >> creating a test db? The idea is to do a basic sanity check of the >>

using Django unit test framework with existing production db

Hi, Is there some graceful way to have the Django unit test framework access the "production database" for certain tests as opposed to creating a test db? The idea is to do a basic sanity check of the "production db" in case the schema has changed and the db needs to be rebuilt. Please CC

dynamic url use case

Hi everyone, I have the following situation, and I would value advice. I have two classes, FolderUpload and FileUpload as given below. I want a dynamic upload_to url in FileUpload, such that the upload to field depends on the value of the folder field, specifically path field. I realist that

media directory for testing

Hi. I'm having the following problem while testing. I'm writing a unit test for a file upload (using newforms). This works. However, the file gets written to the same media directory as is used in normal work. I'd prefer this happened somewhere where it would have no impact on normal

testing filesystem operations in Django

Hi, Here is a simple question about testing. I have a django file upload application which needs to operate on the filesystem as part of its functionality (create files/directories etc. under media root) I use Debian etch. So, I want a way to test filesystem operations, preferably without

Django issue #4165

** class FileUpload(models.Model): ## Workaround for http://code.djangoproject.com/ticket/1030. See end of issue. ## Faheem Mitha October 2nd 2007. upload_date = models.DateTimeField(default=datetime.now(), blank=True, editable=False) upload = models.FileField(upload_to

file upload/download management in Django

Dear Django Users, I've been given the task of developing a web application at work. This is for uploading/downloading large data files, specifically microarray data files for bioinformatics work. I've been looking at Django and managed to get some basic framework stuff working, using the