On Nov 29, 9:23 pm, Michael Merickel mmeri...@gmail.com wrote:
Regardless, I hope this is way too much information about Pyramid internals
and I'm curious what you're planning on doing that you'd need to trace the
undocumented apis.
First, thanks a TON!
This is *way* too much info indeed!
I just wanted to take a stab at trying to make decorators like:
@require_logged_in
In pyramid I don't think you need a require_logged_in decorator for a view
because you can just do:
class RootFactory(object):
@property
def __acl__(self):
return [
(Allow,
@John Anderson
You could do that, but then you're using the Pyramid auth/security
framewor - and i want to stay away from it. i'm not a fan of its
design, and it won't work easily/quickly with how I like to build
apps.
--
You received this message because you are subscribed to the Google
it's in the Configurator an the action_method decorator
just wondering what it is, i'm knee deep trying to understand the
architecture
--
You received this message because you are subscribed to the Google Groups
pylons-discuss group.
To post to this group, send email to
I should point out that it's slightly more general than just tracking
user code. At any given point in time it has knowledge of what line of
code invoked each action within the call stack.
Regardless, I hope this is way too much information about Pyramid internals
and I'm curious what you're
