Re: [Zope-dev] [Proposal] Drop Mount.py from ZODB 3.5

Tim Peters wrote: http://www.zope.org/Collectors/Zope/1800 describes some of the code problems with Zope's current way of mounting databases. ZODB 3.4 (still) has a Mount.py module, unused and untested by ZODB. Jim and I were both surprised today to discover that Zope (2.8) still

Re: [Zope-dev] [Proposal] Drop Mount.py from ZODB 3.5

Tim Peters wrote: http://www.zope.org/Collectors/Zope/1800 describes some of the code problems with Zope's current way of mounting databases. ZODB 3.4 (still) has a Mount.py module, unused and untested by ZODB. Jim and I were both surprised today to discover that Zope (2.8) still imports

Re: [Zope-dev] [Proposal] Drop Mount.py from ZODB 3.5

Shane Hathaway wrote: Tim Peters wrote: http://www.zope.org/Collectors/Zope/1800 describes some of the code problems with Zope's current way of mounting databases. ZODB 3.4 (still) has a Mount.py module, unused and untested by ZODB. Jim and I were both surprised today to discover that

RE: [Zope-dev] [Proposal] Drop Mount.py from ZODB 3.5

[Jim Fulton] Tim, you should have noted, for the benefit of Zope users, that the itent was to move this module into Zope, where it belongs. If I knew I was sending the msg to zope-dev, I would have wink. That is, this message was _intended_ to go to zodb-dev, but I got fooled into accepting my