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

 Replying to [comment:25 chrisz]:
 > Replying to [comment:24 Gustavo]:
 > > I think that from a I-dont-care-how-its-implemented point of view,
 it's just making predicates booleans. ;-)
 >
 > Not really. They can be ''evaluated'' as booleans, but they ''are'' no
 booleans, similar to lists and strings which are false if they are empty.

 What I meant is that they can act as booleans.

 Anyway, I see no big deal with those tiny functions which most people
 won't even use directly.

 > > Because I was getting import errors, even if the dist name was "repoze
 .what-pylons":
 >
 > Maybe a general problem with namespace packages? I think we should look
 into that.

 I've heard so. I hit that problem while developing the repoze.who
 SQLAlchemy plugin: hence it's called repoze.who.plugins.sa instead of
 repoze.who.plugins.sqlalchemy.

-- 
Ticket URL: <http://trac.turbogears.org/ticket/2205#comment:26>
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