grok.Permission: grok ordering broken

Bug #188701 reported by Christian Theune
2
Affects Status Importance Assigned to Milestone
grok
Fix Released
High
Martijn Faassen

Bug Description

This is a problem that was introduced when switching to base classes for permissions:

grok's processing order seems to depend on the name of the object in the module's namespace. Therefore this construct will fail:

class Manage(grok.Permission):
    grok.name('manage')

class Edit(grok.View):
    grok.require('manage')

When changing the name of the `Manage` class to `AManage` it will work.

todd (todd-infrae)
Changed in grok:
assignee: nobody → faassen
milestone: none → 1.0
Revision history for this message
Martijn Faassen (faassen) wrote :

We fixed this issue a while ago, so closing it.

Changed in grok:
importance: Undecided → High
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.