+1 I had thought about exactly this idea during the weekend but I thought the "z" alternative had such traction that it wasn't worth mentioning. The only difference is that I thought about renaming Zope to ZopeClassic or ZopeLegacy instead of Zope2 (keeping version numbers out of packages and all that...)
Cheers, On Tue, 2004-04-20 at 13:08, Jim Fulton wrote: > [...] > I've gotten enough negative feedback to "z", that I've added an alternative 4 > to the proposal: > > 4. Rename the Zope package to Zope2 and provide a legacy Zope > package > > - Rename the "Zope" package to "Zope2" > > - Put the Zope 3 "zope" package into the same location as > "Zope2" in a combined installation. > > - Provide a legacy directory containing a "Zope" package. > There will be an option to add this to the Python path. This > option will be enabled by default in Zope 2.8 and disabled by > default in Zope 2.9. > > Importing Zope will cause a deprecation warning. > > The legacy Zope package will have a README.txt file that > explains what it is and refers people to the zope and Zope2 > packages. > > This would mainly impact Zope 2. > > What do people think about alternative 4? > > Jim -- Leonardo Rochael Almeida <[EMAIL PROTECTED]> _______________________________________________ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
