#10547 closed (fixed)
Delayed Loading Model Update Causes Recursive Errors
Reported by: | Owned by: | Malcolm Tredinnick | |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | 1.0 |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
I don't really have much insight to this right now but here is the stack trace.
File "/var/www/next_django/apps/django/core/cache/backends/filebased.py" in set 71. pickle.dump(value, f, pickle.HIGHEST_PROTOCOL) File "/var/www/next_django/apps/django/db/models/base.py" in __reduce__ 352. return super(Model, self).__reduce__() File "/var/www/next_django/apps/django/db/models/base.py" in __reduce__ 352. return super(Model, self).__reduce__() File "/var/www/next_django/apps/django/db/models/base.py" in __reduce__ 352. return super(Model, self).__reduce__() File "/var/www/next_django/apps/django/db/models/base.py" in __reduce__
Change History (7)
comment:1 by , 16 years ago
Description: | modified (diff) |
---|
comment:2 by , 16 years ago
I am running a stachmo store. One of the satchmo apps is called keyedcache eventually makes a call to cache.set(key, val, length) which sets off this whole chain.
comment:4 by , 16 years ago
Triage Stage: | Unreviewed → Accepted |
---|
Somebody's going to have to work out a slightly smaller example than "it happens somewhere in satchmo doing something unspecified". I can't see why recursive calls to __reduce__()
should be happening, so I'm going to need a repeatable case to debug this.
comment:5 by , 16 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
Ok, I've managed to replicate this now (the test suite does it, in fact) using Python 2.4.
comment:6 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Fixed formatting. What is it you're trying to do that causes this error?