#26975: Unclear documentation: use of paths with loaddata
-------------------------------+--------------------
Reporter: ancientHacker | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.9
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
The howto on fixtures [1] states that providing a path to loaddata
overrides the usual search, but in fact this is only true of an absolute
path. Relative paths to fixture files can be used to namespace them as
with templates and static files.
I suggest that the docs be updated to clarify this point about paths and
to add namespacing advice for fixture files analogous to that for
templates [2] and static files [3]. I have prepared a pull request [4]
with a suggested fix.
References: \\
[1] https://docs.djangoproject.com/en/1.9/howto/initial-data/#where-
django-finds-fixture-files \\
[2] https://docs.djangoproject.com/en/1.9/howto/static-files/#configuring-
static-files \\
[3] https://docs.djangoproject.com/en/1.9/intro/tutorial03/ \\
[4] https://github.com/django/django/pull/6996
--
Ticket URL: <https://code.djangoproject.com/ticket/26975>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/056.531e54c27b043e8236be936d53d052c1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
