Re: Application decoupling - project architecture question

There is a good tutorial on this in Practical Django Projects http://www.amazon.com/Practical-Django-Projects-Pratical/dp/1590599969 It goes a bit more into theory that I found helpful. On Aug 6, 8:07 am, Andrin Riiet wrote: > Hi, I'd like to shed some light on the

Re: Comment Detail URI

> I've read through the two posts above several times now and I'm still > not at all clear what you're asking for. What do you mean by 'queryset > for a particular comment'? A comment isn't associated with a queryset, > it's associated with a particular instance. You're right worded badly and

Re: Comment Detail URI

I guess what I'm really looking for is someone who has an example of a reverse() lookup for generic relationships like the ones created in the django comments, just to be clear. Maybe this is just one of those instances where I need to write the query in SQL? Since I'm a django noob, I wanted to

Comment Detail URI

One thing I'm trying to do is have an view that shows an individual comment. So for instance I will have a list of comments and then you could link that to a page that pulled up a view that just displayed that individual comment. So I have urls that look something like:

Using two different Comment Instances

I'm familiar with modifying comments to change functionality, that's well documented. But what I want to do is use a modified version of comments on a model and also the standard comments. So I have a model "post" and I want to enable comments, easy enough, and then I want to enable mod_comments

Re: Type Error str is not callable in base.py

Thanks Karen - I think I will start doing that from now on. Thanks everyone else - For now I'm just rolling back a bit before I started getting the error and go from there. It seems that my project scope has changed a bit midstream anyway so I guess this really isn't the end of the world. If I

Re: Type Error str is not callable in base.py

Alex Sorry I wasn't more clear, but I wasn't suggesting that the fact I'm getting the error is a bug, but it seems as though this error message results in an uncaught error and that is something they are working on already - see this http://code.djangoproject.com/ticket/6442 Here is the entire

Re: Type Error str is not callable in base.py

Paul Actually this is what I already have in all my model definitions - as suggested in some of the documentation and it's been working so far on several different projects. def __unicode__(self): return u'%s' % (self.title) Please also note that no changes were made to

Re: Type Error str is not callable in base.py

Yeah, I couldn't figure it out either since the error message is not so helpful and it seems that this is actually a django bug that they are currently working on, but according to the documentation of the error reporting bug it should be coming from my view file. Weird thing is I've used this

Type Error str is not callable in base.py

I found the tickets regarding this error on the bug reports and noticed that it comes up when there is something wrong with your view, but I can't seem to find anything off. Here is my view.py in that app. Weird thing is I'm just copying this over from another project and it was working fine