On 06/24/2011 04:51 PM, Chris McDonough wrote:
For better or worse, Pyramid is very explicit, and very few of its APIs are optimized for less typing. I think you're suggesting that passing parameters is too hard and too much typing, because you already have the API you want (has_permission), it just takes more typing than you'd like to use it. Am I right? Or are you missing functionality you want?
No, the functionality is there. Perhaps I'm just concerned with performance, having to call has_permission() many times on single page (supplying both request and request.context to each, lazy me :) ) OR write my own wrapper that computes these once and then presents an easy to access list for checking. And since checking for individual permission is not an exception in a web app, I thought it could be made more straightforward and efficient, available out of the box.
But that's jumping to conclusions, though, if Pyramid is slated for authn/authz subsystems overhaul for 2.0.
I personally have had some rather poor experiences with other frameworks that are more implicit. While they're great for some use cases, for others, the implicitness is really troublesome and makes evolving the framework over time extremely difficult. So my usual knee-jerk reaction to adding convenience features is conservatism. Over time, though, we'll move more towards convenience where it doesn't hurt maintainability, so I'm happy to talk about it.
Well yes, good point. .: V :. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
