Martian/grokkers should annotate configuration context with filenames, line numbers

Bug #173666 reported by Philipp von Weitershausen
4
Affects Status Importance Assigned to Milestone
grok
Opinion
Undecided
Jan Wijbrand Kolman
0.11
Won't Fix
Undecided
Unassigned
1.1
New
Undecided
Unassigned
Trunk
Invalid
Undecided
Unassigned

Bug Description

With grok 0.11, configuration actions were introduces to grokkers. That means you'll get conflicts if you have two conflicting components registered. While the error message is actually quite informative when using ZCML directives, it's not when using grokkers. The reason for that is that Martian and/or the grokkers don't annotate the configuration context with an appropriate 'info' object.

As far as I understand at this point (need to do some more digging through zope.configuration), Martian should create new configuration contexts at least for each new file that's processed, but probably even for each thing that's grokked.

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

Won't fix this in 0.11.

Changed in grok:
milestone: 1.0 → 1.1
Revision history for this message
todd (todd-infrae) wrote :

Marking as invalid because we want to stop assigning bugs to the 'trunk' series.

Revision history for this message
Christian Klinger (cklinger) wrote :

Martijn what do you think about it.?

Changed in grok:
status: New → Opinion
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.