http://www.jhm3.lowcostpillsx.com
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegr
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
> Pros of this solution:
> * The implementation is clear and short; 250 lines of code do the magic
> All the statements are exactly the python statements
Alex briefly mentioned the design decision of the template system, but
I think it'd be good to emphasize his point-- Django was designed to
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 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
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
At first let me say that I really appreciate your reply! Thanks.
On Aug 30, 6:48 pm, Tim wrote:
> Alex briefly mentioned the design decision of the template system, but
> I think it'd be good to emphasize his point-- Django was designed to
> have various layers, such as the urls, the views, the t
On Mon, Aug 30, 2010 at 7:31 PM, gabriele wrote:
> At first let me say that I really appreciate your reply! Thanks.
>
> On Aug 30, 6:48 pm, Tim wrote:
> > Alex briefly mentioned the design decision of the template system, but
> > I think it'd be good to emphasize his point-- Django was designed t
On Sat, Aug 28, 2010 at 10:47 PM, Gabriele Fantini
wrote:
> Hi,
>
> I've just joined this group. The reason is that I've recently
> developed a new django template system (and I'm still working on it)
> and I'm currently using it for my new sites.
> I hope this is the right place to discuss of suc
