#30908: FilePathField doc & field scan dir issue
-----------------------------------------+------------------------
Reporter: jheld | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 2.2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
The docs around the model of FilePathField show the path as being default
None, while the code is empty string.
Also, due to a change in 2.2 around using scandir on the form field for
FilePathField, if the path doesn't exist, a FileNotFoundError is issued
(same would have happened before the scandir change), but now the
try/except logic on OSError (super class) has been removed, in the PR that
changed to scandir.
So, the docs are out of date (regardless of whichever value is more sane
as a default), and the change on scandir also removed the try/except.
Previously it was not an issue because there was a try/except, so we were
caught off guard.
--
Ticket URL: <https://code.djangoproject.com/ticket/30908>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/048.f563a75b8f0610b6b572360991e36795%40djangoproject.com.
