#2070: [patch] Large streaming uploads
----------------------------------------+-----------------------------------
   Reporter:  [EMAIL PROTECTED]  |                Owner:  jacob         
     Status:  assigned                  |            Component:  Core framework
    Version:                            |           Resolution:                
   Keywords:  streaming, upload, large  |                Stage:  Accepted      
  Has_patch:  1                         |           Needs_docs:  1             
Needs_tests:  0                         |   Needs_better_patch:  1             
----------------------------------------+-----------------------------------
Comment (by [EMAIL PROTECTED]):

 Replying to [comment:11 adrian]:
 > In reference to bnewbold's comment above, it's the
 [http://www.python.org/doc/current/lib/module-shutil.html shutil module],
 and it looks like it's been around since at least Python 2.3. (Django
 supports Python 2.3 and up.)
 
 os.rename('old', 'new') does result in an 'invalid cross-link device'
 exception when 'old' and 'new' are on different filesystems. It doesn't
 make sense to do this, as once a large file has been streamed to disk,
 copying to another filesystem is a pointless additional overhead. However,
 the code could catch the error, and do a copy and then delete operation
 (and generate a warning that the system can be configured more
 efficiently).
 
 Or it could use shutil as suggested by a previous poster.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/2070#comment:107>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to