Error on creating initial versions if __unicode__ points to foreign key

[etianen]

Error on creating initial versions if __unicode__ points to foreign key

[etianen]

Odd.

What code are you using to register the models with django-reversion. Or, if you're using the Django admin integration what is your Django admin code?

[etianen]

Ah, ignore me, I know what the problem is.

To be fair, though, your unicode method should probably return a unicode object, rather than a Django model!

return unicode(self.question)

[etianen]

I've just been looking over the codebase, and I think you're code is incorrect. Reversion is just calling unicode(obj) on the model, which then blows up because your unicode implementation is invalid. unicode should return a string or buffer object, as the stack trace suggests.

Potentially Python should be more tolerant in this regard, and keep recursively calling unicode until a string or buffer object is reached. That's a beef to take up with the Python devs, however. :)

I'm closing the issue for now. If you think reversion should be handling things differently, please re-raise and we can talk.

In any case, the post_syncdb hook for creating initial revisions is becoming an actual admin command in the next reversion release, so this problem will soon be going away!