zope.app.publisher.browser.viewmeta.simple doesn't provide browserDefault

Bug #129296 reported by Philipp von Weitershausen
2
Affects Status Importance Assigned to Milestone
Zope 3
Won't Fix
Low
Unassigned
zope.app.publisher
Won't Fix
Low
Unassigned
zope.browserpage
Invalid
Low
Christian Theune

Bug Description

zope.app.publisher.browser.viewmeta.simple claims it implements IBrowserPublisher but it doesn't implement the required browserDefault method.

Changed in zope3:
status: New → Won't Fix
Changed in zope.browserpage:
status: New → Confirmed
Changed in zope.app.publisher:
status: New → Won't Fix
Changed in zope.browserpage:
status: Confirmed → In Progress
Changed in zope3:
importance: Undecided → Low
Changed in zope.app.publisher:
importance: Undecided → Low
Changed in zope.browserpage:
importance: Undecided → Low
assignee: nobody → Christian Theune (ct-gocept)
Revision history for this message
Christian Theune (ctheune) wrote :

Interesting. There is an explicit test (testNamedViewNoPagesForNonCallable) that verifies that the existing behaviour. Does anybody know why this is?

Changed in zope.browserpage:
status: In Progress → Confirmed
Revision history for this message
Colin Watson (cjwatson) wrote :

The zope.browserpage project on Launchpad has been archived at the request of the Zope developers (see https://answers.launchpad.net/launchpad/+question/683589 and https://answers.launchpad.net/launchpad/+question/685285). If this bug is still relevant, please refile it at https://github.com/zopefoundation/zope.browserpage.

Changed in zope.browserpage:
status: Confirmed → Invalid
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.