[Zope-dev] Zope and zope

[Chris McDonough]

+1

It looks like in the Zope 2 trunk, there are only a very few places that
rely on "import Zope" or "from Zope import".

It looks like it would be possible to change the name of the "Zope"
package in Zope 2 to "zope2" or something without a tremendous amount of
work.  And as long as a module alias was created to alias that to
"Zope", 3rd party products would continue to work.  This strategy would
only work if we didn't plan on supporting systems where PYTHONCASEOK
(see python -h) was set to be case-ignoring (are there any?).

One potentially nasty problem is that the Zope 2 bootstrap code lives
inside the Zope package within Zope.Setup, and some 3rd-party utilities
(like the Plone Controller and many 3rd party tests that don't use the
testrunner/test.py framework) rely on being able to "import Zope". 
Renaming the package pushes the responsibility for knowing about the
name change out to those utilities (because there's really just nowhere
to insert a module alias shim before they attempt to "import Zope"). 
Considering the pain that I know would be involved with doing a "zope"
-> "zope3" rename, however, this might be an acceptable breakage (except
of course to those whose code it breaks, so they should speak up).

- C


On Tue, 2004-04-13 at 10:40, Jim Fulton wrote:
> Zope 2 has a package named "Zope". Zope 3 has a package named "zope".
> Starting with Zope 2.8, parts of Zope 3 will be included in Zope 2.
> As things stand, this will require having both "Zope" and "zope" packages.
> Python can handle this fine, however, it will require putting the packages
> in separate directories (for Windows).  A typical Zope installation will
> probably add at least two directories to the Python path, for:
> 
> - The Zope software
> 
> - Instance (site) specific packages
> 
> So adding two directories, rather than one for the Zope software isn't
> a big deal.
> 
> Of course, having two packages with names differing only in case is a
> bit ugly.
> 
> Do we want to consider renaming one or both of these packages
> to avoid the conflict?
> 
> Jim