Re: "getattr(): attribute name must be string"

> The ticket itself is the best guide to any knowledge about the problem; in > this case, I'm guessing that the answer is no - there isn't a patch or > workaround. Any help you can provide in tracking the problem (and/or fixing > it) would be greatfully accepted. Here's a more complete traceback:

Re: generic-auth and extensible QuerySet filtering

On 11/27/06, Joseph Kocherhans <[EMAIL PROTECTED]> wrote: > I'm not sure that this should be a function however. It may also make > sense as a Manager and/or QuerySet method. It *feels* like something that'd make sense as a manager method; maybe call 'QuerySetFilter' to 'AuthorizationManager' or

Re: "getattr(): attribute name must be string"

On 11/29/06, James <[EMAIL PROTECTED]> wrote: > > > This bug was submitted a couple of months ago: > > http://code.djangoproject.com/ticket/2828 > > but unfortunately I just got bitten by it :( Is there a fix, or will > one be forthcoming? Or is there a workaround (the one in the ticket > doesn't w

Re: generic-auth and extensible QuerySet filtering

> Does anyone have ideas for what to name this function/method? I > haven't been able to come up with anything I've been happy with. Joseph, I'm not flush with naming ideas at the moment, but thought I would try to brain storm a little. List of my bad names: - FilterPerms - PermFilte

Re: Custom User/Groups/Permissions...is this possible?

[EMAIL PROTECTED] wrote: > I'm porting another application over to django...while the admin tools > built into django will be nice for some of my tables... I'd prefer to > stick with my old User/Groups/Permissions for a lot of it ... as we > have different users that will be logging in to do diffe

Re: Django Layout Model

oops... sorry I missed the link on the main page... --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe

Django Layout Model

Hello, I have a few newbie questions. I am well rounded in Rails but I'm trying to also learn django. I am having a hard time understanding the Django layout model. I followed all the tutorial, but still I am confused about how do I define a particular layout (not template). Then how does views.

"getattr(): attribute name must be string"

This bug was submitted a couple of months ago: http://code.djangoproject.com/ticket/2828 but unfortunately I just got bitten by it :( Is there a fix, or will one be forthcoming? Or is there a workaround (the one in the ticket doesn't work, in fact)? TIA. -- James --~--~-~--~~

new: django middleware to integrate with Firestats web analysis tool

Hello django-ers, I wrote a small middleware to log each django site pageview with Firestats log analysis tool (Homepage: http://firestats.cc/wiki). Its not the most efficient integration method, but it works. Firestats is a log analysis tool (like AWstats, webalizer, Google Analytics). Its writt