id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
21551	1.6 regression: Can't load fixtures from subdir	Jonas H.	nobody	"Consider this fixture directory (added to `FIXTURE_DIRS`):

{{{
- fixtures/
  + initial_data.json
  + tests/
    - initial_data_inner.json
}}}

Loading the outer fixture works:

{{{
$ ./manage.py loaddata initial_data
Installed 3 object(s) from 1 fixture(s)
}}}

The inner does not:

{{{
$ ./manage.py loaddata initial_data_inner
…site-packages/django/core/management/commands/loaddata.py:218: UserWarning: No fixture named 'initial_data_inner' found.
  warnings.warn(""No fixture named '%s' found."" % fixture_name)

Installed 0 object(s) from 0 fixture(s)

$ ./manage.py loaddata tests/initial_data_inner
…site-packages/django/core/management/commands/loaddata.py:218: UserWarning: No fixture named 'initial_data_inner' found.
  warnings.warn(""No fixture named '%s' found."" % fixture_name)

Installed 0 object(s) from 0 fixture(s)
}}}

This used to work in Django 1.5.

The cause of this is that all fixture names that contain an `os.path.sep` are considered absolute paths in the `loaddata` management command."	Bug	closed	Core (Management commands)	1.6	Release blocker	fixed	loaddata, fixtures	jonas-django@…	Accepted	1	0	0	0	0	0