It isn't using FileField, infact it isn't touching the DB or using any kind of manipulator at all. The form consists of a simple <input type="file" /> box which allows the user to upload a file. The file is then submitted in a POST request to the second view.
The second view then calls to an outside library which converts the file to a tab-delimited file, then the view continues on and does statistical work. None of my code has anything to do with the mail or email stuff. It is worth noting that parse_file_upload in django.http uses those email and mail libraries a lot. For what I don't know. But like I said, Im not calling to the DB or doing anything else. Really all Django itself is doing is uploading the file and then displaying a template. James Bennett wrote: > On 9/13/06, jp <[EMAIL PROTECTED]> wrote: > > http://paste.e-scribe.com/1564/ > > http://paste.e-scribe.com/1565/ > > It's hard to infer exactly what's going on without knowing more about > the actual code you're using; for example, that first set of profiler > output is spending over 40% of its time in django.core.mail and > related Python email modules, yet AFAIK there's nothing in FileField > or the automatic manipulator for a model with a FileField which should > get into that code. > > Could you provide some more detail about what your code is doing, > especially anything it's trying to do with respect to sending email? > > -- > "May the forces of evil become confused on the way to your house." > -- George Carlin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
