http://code.djangoproject.com/ticket/14199
On Aug 30, 1:34 pm, Tim wrote:
> I don't think that's the issue, although the answer to that question
> is 'no'.
>
> Back on commit r13473 several changes were made, which introduced this
> inconsistency. the value was shifted from self._table to the lo
I don't think that's the issue, although the answer to that question
is 'no'.
Back on commit r13473 several changes were made, which introduced this
inconsistency. the value was shifted from self._table to the local
variable named just 'table', which each method was responsible to
derive via that
The only time i've seen this sort of thing happening was when i had an
app name that got in the way of something in the core/python namespace
('collections'). Do you have any apps that could be getting in the
way? Does the error occur with all your projects?
Stephen
On 30 Aug 2010, at 17:3
I'm on the latest trunk (updated this morning), and I'm getting a
Python NameError in django.core.cache.backends.db . Line 127 (http://
code.djangoproject.com/browser/django/trunk/django/core/cache/backends/
db.py#L127) references a variable 'table', but it's not locally
defined. All other method
