streaming patches reloaded
Hi folks. Following this thread ( http://groups.google.com/group/django-developers/browse_frm/thread/a0ae32019bb02f05/2c05c5363516ea76?q=streaming&rnum=2#2c05c5363516ea76) , since I can't reply there ( over 30 days old, google tells me). I have an app that uploads a 4mb file and is taking a ton of memory. >From tickets 1484/1569 they are set as fixed, but I cannot find them on django's source code. Are these patches active in trunk? If not, anyones knows if they're working after the merge? Anyone using them? Thanks a lot, arthur --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: streaming patches reloaded
Hi Ivan. Just to make sure I understand: - after patching django I 've set: STORE_UPLOAD_ON_DISK = True I am trying to use this on the admin. Any more steps I must take? thanks a lot (for the patch and help) arthur --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: ImageField and its use in templates
Hi Wegen. carimage = models.ImageField(upload_to = 'images/cars/%s.png' % carID, null = True, blank = True) this won't work. upload_to must be a string (it's not evaluated at the time the object is saved to the database). your best bet is to leave the path to the desired directory and name the file on save. something like this: carimage = models.ImageField(upload_to = 'images/cars/",null = True, blank = True) def save(self): if self.id is not None and len(self.carimage) >1: self.carimage = %s.png' % self.id super(ModelName, self).save() ** the if check is a workaround a bug (ticket # 639) where save passes two times for file fields. --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Progress, status, and opinions of #2070
Hi Mike. This is less of a patch review, and more of an user's feedback. Probably not the best place to post this, but I figured track's ticket 2070 page already has too much going on there. Been using this patch for a while without a glitch ( in webfaction's setup, apache2, mod_python). Running pretty smoothly, even with simultaneous uploads. One suggestion is that the new setting for settings.py could have a bit more descriptive names. FILE_UPLOAD_DIR seems somewhat related to where files are uploaded to (such as upload_to in models) which can be confusing. Maybe something like FILE_UPLOAD_TEMP_DIR will give more the idea of what this is really about. Just wanted to drop in and give the perspective of someone just using the patch. All in all, thanks for the patch, it's a lifesaver. cheers Arthur --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: {GSoC 2008}Django-Newcomments : A preview
Hi Thejaswi. A couple of suggestions: Any reasons for having CommentFlag.flag being a string, and not a foreign key to a FlagType model ? Having them as strings makes it easier to end up with bad data (misspelling and so forth). Of course there is always the performance penalty, but it seems worth it. Also, many times it is useful to keep a "raw" body for a comment (as the user sent it), but also for performance reasons, a "processed" version such as html (from markdown or something else). Maybe keeping both in the db allows for speedier rendering. Then an application can define somewhere (maybe a settings) which function to process the comment (markdown, textile, some home made tag removing routine), and have that run and then persisting both at the database. Thanks Arthur --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
