#27357: Variant of FilePathField that uses a Storage backend
     Reporter:  Curtis Maloney       |                    Owner:  nobody
         Type:  New feature          |                   Status:  new
    Component:  Database layer       |                  Version:  1.10
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  1
Changes (by Tim Graham):

 * needs_docs:  1 => 0


 The `FilePathField` form field looks coupled to the file system
 (`os.walk()`, etc). Maybe it would be enough to try to add a storage
 agnostic file path form field and allow developers to use it with
 `models.FileField`. While `models.FilePathField` takes `path`, `math`,
 `recursive`, `allow_files`, and `allow_folders` arguments, it's not doing
 anything with them besides passing them to the form field.

Ticket URL: <https://code.djangoproject.com/ticket/27357#comment:1>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to