#2205: Provide a simple way to evaluate repoze.what predicates
------------------------------------------------+---------------------------
 Reporter:  chrisz                              |        Owner:  Gustavo 
     Type:  enhancement                         |       Status:  assigned
 Priority:  high                                |    Milestone:  2.0b6   
Component:  TurboGears                          |      Version:  2.0b1   
 Severity:  major                               |   Resolution:          
 Keywords:  repoze.what predicates permissions  |  
------------------------------------------------+---------------------------
Comment (by Gustavo):

 Replying to [comment:4 chrisz]:
 > Replying to [comment:3 Gustavo]:
 > > Regardless of the decision we make on this, the solution is not going
 to be implemented in TG itself. Instead I will implemented it in the
 repoze.what-pylons package
 > Yes, Pylons could also benefit from such a mechanism, so that's a very
 good idea.

 Exactly :)

 > > Oh, I'm sorry, what I said about Option 4 was actually about Option 3,
 and vice versa. I'm getting crazy with so much proposals ;-)
 > >
 > > So, by "Option 4 is not forward compatible" I mean that in repoze.what
 v2 predicates have been reorganized in different modules because that
 "groups/permission-based authorization pattern" won't be ''the'' supported
 pattern anymore, but ''yet another'' supported pattern, so predicates
 specific to that pattern are now defined in a different module.
 >
 > Ok, clear now. Though this could be solved by modifying the
 `__getattr__()` method so that it checks all available modules for the
 passed predicate name (merging all the names together), or alternatively
 by passing the module name and then the predicate name as subattribute,
 like `access.permissions.has_permission('edit')`.

 Yes, but still 3) will be easier to implement and use.

 Do you agree that we go for 3)? It's so easy to implement that I'd do it
 tomorrow at the latest.

-- 
Ticket URL: <http://trac.turbogears.org/ticket/2205#comment:5>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to