Is there any kind of workaround for this? I'm worried that rows are not
making it into the db because of this problem which I'm also having.
On Wednesday, February 8, 2012 4:44:12 PM UTC-5, akaariai wrote:
>
> Quickly looking through the code it seems this is a bug in Django. The
> full_path variable is used in a place where it is not guaranteed to be
> initialized. In fact, the whole loaddata.py file seems like a good
> candidate for some cleanup. 9 levels of indentation in a method and
> this sort of bug is likely...
>
> The code was going to tell you that fixture loading didn't succeed, so
> the error when reporting this error isn't that critical.
>
> Please file a bug in trac about this. Try to include enough
> information so that the error can be reproduced. A failing test case
> in django's test suite is perfect, a sample project demonstrating the
> problem is good and verbal explanation will do.
>
> - Anssi
>
> On Feb 8, 10:27 pm, rok <spuzv...@gmail.com> wrote:
> > When executing the "manage.py syncdb" I get the following error:
> >
> > Creating tables ...
> > Installing custom SQL ...
> > Installing indexes ...
> > Traceback (most recent call last):
> > File "./manage.py", line 26, in <module>
> > execute_from_command_line(sys.argv)
> > File "/home/rok/apps/django-trunk/django/core/management/
> > __init__.py", line 440, in execute_from_command_line
> > utility.execute()
> > File "/home/rok/apps/django-trunk/django/core/management/
> > __init__.py", line 379, in execute
> > self.fetch_command(subcommand).run_from_argv(self.argv)
> > File "/home/rok/apps/django-trunk/django/core/management/base.py",
> > line 196, in run_from_argv
> > self.execute(*args, **options.__dict__)
> > File "/home/rok/apps/django-trunk/django/core/management/base.py",
> > line 232, in execute
> > output = self.handle(*args, **options)
> > File "/home/rok/apps/django-trunk/django/core/management/base.py",
> > line 371, in handle
> > return self.handle_noargs(**options)
> > File "/home/rok/apps/django-trunk/django/core/management/commands/
> > syncdb.py", line 164, in handle_noargs
> > call_command('loaddata', 'initial_data', verbosity=verbosity,
> > database=db)
> > File "/home/rok/apps/django-trunk/django/core/management/
> > __init__.py", line 147, in call_command
> > return klass.execute(*args, **defaults)
> > File "/home/rok/apps/django-trunk/django/core/management/base.py",
> > line 232, in execute
> > output = self.handle(*args, **options)
> > File "/home/rok/apps/django-trunk/django/core/management/commands/
> > loaddata.py", line 239, in handle
> > (full_path, ''.join(traceback.format_exception(sys.exc_type,
> > UnboundLocalError: local variable 'full_path' referenced before
> > assignment
> >
> > Does this ring a bell to anyone? I'm running the django trunk from Feb
> > 8th (so 1.4 candidate).
> > Rok
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-users/-/ficmZhhNIL0J.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
