#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 chrisz):
Yes, unfortunately, if we cannot reach a broad consensus quickly, we'll
have to set the milestone to 2.1.
I also don't like 4) too much, but 3) would be ok for me. It just needs
proper documentation. I don't see a big problem in "the TG way vs. the
standard way". It's just a facilitation of predicate usage and such
simplifications are also implemented in other areas, e.g. object dispatch
instead of routes, using decorators instead of rendering or validating
manually, etc. I think we are only following the TG paradigm of making
simple things simple and complex things possible. If everything would be
standard, then we could just as well use Pylons or use now framework at
all. I also don't see why 3) cannot not be made compatible with
repoze.what v2, can you elaborate a bit on this?
--
Ticket URL: <http://trac.turbogears.org/ticket/2205#comment:2>
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
-~----------~----~----~----~------~----~------~--~---
