On Mar 27, 9:09 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > This is a known mini-problem and something we need to / will sort out > prior to 1.0. There are a *lot* of places in Django that wrap views up > and then expose them to the world. Once you get used to the idiom, it's > not a bad way of programming, although it does make your brain leak out > your ears sometimes trying to work out who is actually doing the real > work. The drawback of this approach is that it's hard to get access to > the underlying function. > > At the moment we try to remember to fill in most of the details on the > wrapped object, but this isn't always possible (for example, the > __name__ attribute of a function is read-only in python 2.3). One
hum, that's a problem because I'm trying to develop a security middleware to allow/deny applications. So authenticated users could or not be able to get an application if they've got a permission to do that. I want to do it using the function name that the user is going to access and I don't want to do it using urls because sometimes urls are different than apps names. That's way I _need_ the function name :-( > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
