[Zope-dev] Re: [Zope3-dev] Re: Zope and zope

[Chris McDonough]

Note that the reason I suggested renaming Zope to "zope2" (or whatever) as
opposed to "zope" to "zope3" is because Zope 3 uses absolute imports almost
everywhere; it would be far less work to change "Zope" to "Zope2" because
Zope 2 either uses relative imports or assumes it can find what it needs on
sys.path.  I think the breakage, although literally "incalculable" (as is
every change to Zope 2, given that it has no canonical API), would be
manageable given enough lead time.  In fact, if we did change the module
name, we could just leave a "bruce" package in place that, when imported,
raised a "ObsoleteError" with a descriptive message.

I *hate* the idea of having two packages named "zope" where case is the only
thing different.  It's would be insanely difficult (not to mention
embarrassing) to document, should the two codebases merge in some unholy
fashion at some point as is on the 2.9 roadmap.

- C

----- Original Message ----- 
From: "Tres Seaver" <tseaver at zope.com>
To: <stephan.richter at tufts.edu>
Cc: <zope3-dev at zope.org>; <zope-dev at zope.org>
Sent: Tuesday, April 13, 2004 11:08 PM
Subject: Re: [Zope3-dev] Re: Zope and zope


> Stephan Richter wrote:
> > On Tuesday 13 April 2004 22:17, Tres Seaver wrote:
> >
> >><snip>
> >>
> >>>>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?
> >>
> >>-1 to renaming 'Zope';  the amount of third-party code which we would
> >>break is incalculable.  -0 to renaming 'zope' to 'z3', or something;  at
> >>least third party code for Zope3 was built in the test-driven culture,
> >>and has at least some chance of migrating cleanly with confidence.
> >
> >
> > You wanna rename 'zope' to 'z3' for the purpose of merging the two? I
really
> > hope that will not be the case. Or is this for Zope 2 only?
>
> Note that I am -0 to the idea.
>
> > I would hate to have imports like "z3.app.foo" or even "z3.i18n". I am
> > definitely -1 on this option, if it also applies to standalone Zope 3.
>
> I am just arguing that it would be saner to rename 'zope' to 'z3' (or
> 'zope3', or whatever) than to rename 'Zope' to 'zope2' (or whatever).
>
> Tres.
> -- 
> ===============================================================
> Tres Seaver                                tseaver at zope.com
> Zope Corporation      "Zope Dealers"       http://www.zope.com
>
> _______________________________________________
> Zope3-dev mailing list
> Zope3-dev at zope.org
> http://mail.zope.org/mailman/listinfo/zope3-dev
>