While grep'ing the source tree, I found that Neutron does something similar to Trove and may suffer the same fate when upper-constraints.txt allows Routes 2.3 ... amrith at amrith-work:/opt/stack/neutron$ grep -n -r submap.connect . ./neutron/api/extensions.py:286: submap.connect(path) ./neutron/api/extensions.py:287: submap.connect("%s.:(format)" % path) ./neutron/api/extensions.py:296: submap.connect(path) ./neutron/api/extensions.py:297: submap.connect("%s.:(format)" % path) Heads up! -amrith > -----Original Message----- > From: bounces at canonical.com [mailto:bounces at canonical.com] On Behalf Of > OpenStack Infra > Sent: Monday, March 28, 2016 4:12 PM > To: Amrith Kumar <amrith at tesora.com> > Subject: [Bug 1563028] Re: Routes version 2.3 broke the way we register > routes > > Fix proposed to branch: master > Review: https://review.openstack.org/298419 > > ** Changed in: trove > Status: New => In Progress > > -- > You received this bug notification because you are subscribed to the bug > report. > Matching subscriptions: trove-bugs > https://bugs.launchpad.net/bugs/1563028 > > Title: > Routes version 2.3 broke the way we register routes > > Status in Trove: > In Progress > > Bug description: > Routes v2.3 which just came out included this change > > > https://github.com/bbangert/routes/commit/0a417004be7e2d950bdcd629ccf24cf9 > f56ef817 > > which changed submap.connect() in a way that broke the way Trove > registers routes. > > We now need to provide a routename and a path as independent > arguments. > > I tried to make sense of the documentation at > http://routes.readthedocs.org/en/v2.3/setting_up.html#submappers and > got nowhere in a hurry, but reading the code for connect() provided a > possible solution. > > This will likely need to go to stable/mitaka as well. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/trove/+bug/1563028/+subscriptions