So I upped the verbosity like you said, and basically all it got me was a
bunch of text telling me all the places Django didn't find my fixture
before it finally did, and then the same error. Here's the full text of the
error:
Traceback (most recent call last):
File
"/home/menusadmin/.pythonbrew/pythons/Python-2.7.3/lib/python2.7/site-packages/django/core/management/commands/loaddata.py",
line 190, in handle
for obj in objects:
File
"/home/menusadmin/.pythonbrew/pythons/Python-2.7.3/lib/python2.7/site-packages/django/core/serializers/pyyaml.py",
line 62, in Deserializer
raise DeserializationError(e)
DeserializationError: maximum recursion depth exceeded while calling a
Python object
I tried changing commit to False in loaddata.py, I tried adding a manager
class to the one model I have that another model refers to with a natural
key (e.g., 'name,' a CharField, as opposed to the primary key). I read
something about loaddata having some unicode-related problems, so I added
custom Manager classes for all my models that coerce appropriate fields to
strings, e.g.:
class MenuManager(models.Manager):
def create_Menu(self,restaurant,year,location,status,pk,period,language):
menu =
self.create(restaurant=str(restaurant),year=int(year),location=str(location),status=str(status),pk=int(pk),period=str(period),language=str(language))
return menu
I'm still getting the exact same error. Help?
On Sun, Dec 30, 2012 at 1:28 PM, donarb <[email protected]> wrote:
> On Sunday, December 30, 2012 9:54:45 AM UTC-8, Sam Raker wrote:
>>
>> Thanks for your suggestions.
>>
>> I eliminated the underscores and got rid of the __unicode__ methods
>> entirely, cleaned up my except statement, and changed the order of stuff
>> such that all of each model's fields are defined before any methods. (As
>> for the pk field: The csvs I'm using are actually dumps from another
>> database, so everything has its own primary key already, and I realized
>> it's way easier to just leave them alone rather than waste the processing
>> time and memory reconnecting everything via Python.)
>>
>> I'm still having the same problem. I don't think it's related to the
>> length of the files or something in simplejson, as even a dozen-line yaml
>> file gives me the same exception when I try to load it with loaddata.
>>
>> Any more ideas?
>>
>
>
> Next, I would post the stack trace, there's probably something in there
> that points to the problem, if the yaml parser thinks there is recursion in
> the data. And up the verbosity when running the loaddata command:
>
> --verbosity 3
>
> --
> 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/-/pq_mI5E031EJ.
>
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
