#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:2 chrisz]:
> Yes, unfortunately, if we cannot reach a broad consensus quickly, we'll
have to set the milestone to 2.1.
Well, strictly speaking, now I realize that actually we may use it in 2.0
although possibly not by default: Regardless of the decision we make on
this, the solution is not going to be implemented in TurboGears itself.
Instead I will implemented it in the [http://code.gustavonarea.net/repoze
.what-pylons/ repoze.what-pylons] package, an independent project which
now TG uses for its repoze.what integration.
If we don't reach a consensus on time, we can still have the functionality
in v2.0 from repoze.what-pylons.
> 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?
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.
--
Ticket URL: <http://trac.turbogears.org/ticket/2205#comment:3>
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
-~----------~----~----~----~------~----~------~--~---
