#20933: manage.py loaddata stopped working on Django 1.6b2
-------------------------------------+-------------------------------------
     Reporter:  static               |                    Owner:  aaugustin
         Type:  Bug                  |                   Status:  assigned
    Component:  Database layer       |                  Version:
  (models, ORM)                      |  1.6-beta-1
     Severity:  Release blocker      |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Description changed by apollo13:

Old description:

> Hello,
>
> I have a script for loading fixtures that always worked in Django and it
> suddenly stopped working on Django 1.6b2. It works on 1.5.1, 1.5.2 and
> 1.6b1.
>
> ### Create an app called appname and a folder called fixtures with a file
> groups.yaml like this:
> - fields:
>     name: Group1
>     permissions: []
>   model: auth.group
>   pk: 1
> - fields:
>     name: Group2
>     permissions: []
>   model: auth.group
>   pk: 2
> - fields:
>     name: Group3
>     permissions: []
>   model: auth.group
>   pk: 3
>
> ### Try run on terminal
> python manage.py loaddata appname/fixtures/groups.yaml
>
> ### Output for Django 1.6b2
> .../local/lib/python2.7/site-
> packages/django/core/management/commands/loaddata.py:218: UserWarning: No
> fixture named 'appname/fixtures/groups' found.
>   warnings.warn("No fixture named '%s' found." % fixture_name)
>
> Installed 0 object(s) from 0 fixture(s)
>
> (test was made using PostgreSQL with psycopg2 2.5.1 - I didn't had time
> to test on other dbs)

New description:

 Hello,

 I have a script for loading fixtures that always worked in Django and it
 suddenly stopped working on Django 1.6b2. It works on 1.5.1, 1.5.2 and
 1.6b1.

 ### Create an app called appname and a folder called fixtures with a file
 groups.yaml like this:
 {{{
 - fields:
     name: Group1
     permissions: []
   model: auth.group
   pk: 1
 - fields:
     name: Group2
     permissions: []
   model: auth.group
   pk: 2
 - fields:
     name: Group3
     permissions: []
   model: auth.group
   pk: 3
 }}}
 ### Try run on terminal
 python manage.py loaddata appname/fixtures/groups.yaml

 ### Output for Django 1.6b2
 .../local/lib/python2.7/site-
 packages/django/core/management/commands/loaddata.py:218: UserWarning: No
 fixture named 'appname/fixtures/groups' found.
   warnings.warn("No fixture named '%s' found." % fixture_name)

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

 (test was made using PostgreSQL with psycopg2 2.5.1 - I didn't had time to
 test on other dbs)

--

-- 
Ticket URL: <https://code.djangoproject.com/ticket/20933#comment:6>
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/064.3cb96cb32bacaeb4f40495cbf90e3084%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to