Opened 4 years ago

Last modified 4 years ago

#26975 new Bug

Unclear documentation: use of paths with loaddata

Reported by: Daniel Brotsky Owned by: nobody
Component: Documentation Version: 1.9
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: yes
Easy pickings: no UI/UX: no

Description (last modified by Daniel Brotsky)

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/intro/tutorial03/
[3] https://docs.djangoproject.com/en/1.9/howto/static-files/#configuring-static-files
[4] https://github.com/django/django/pull/6996

Change History (4)

comment:1 Changed 4 years ago by Daniel Brotsky

Description: modified (diff)

comment:2 Changed 4 years ago by Tim Graham

Has patch: set
Triage Stage: UnreviewedAccepted

comment:3 Changed 4 years ago by Tim Graham

Patch needs improvement: set

Left an idea for improvement on the PR. Please uncheck "Patch needs improvement" when you update it.

comment:4 in reply to:  3 Changed 4 years ago by Daniel Brotsky

I am happy to improve the patch, but have in mind a slightly different approach, and would like your opinion. Please see the PR for details.

Note: See TracTickets for help on using tickets.
Back to Top