> So, should we prepare a TG 1.1 rc1 release this weekend now that the > SQLAlchemy mapper issue is resolved? > > I would volunteer to carry out the preparations. If there are any > outstanding tickets, which you would like to resolve (i.e. provide a > solution for) before that, please speak up until this Friday.
Unfortunately I don't have a fix but what's the official point of view on this ticket? http://trac.turbogears.org/ticket/2207 Neither identity.SecureObject nor identity.SecureResource protects a whole URL tree currently. This is independent of catwalk, which I don't use anymore and it was indicated on this list that catwalk is anyway semi-deprecated and not recommended. But this problem of protecting a whole tree applies without catwalk too (I just mention this because in the ticket I was talking about catwalk, but the problem is more general). In other words, is there an officially blessed way of protecting a whole URL tree? Cheers, Daniel -- Psss, psss, put it down! - http://www.cafepress.com/putitdown --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
