On Tuesday 13 April 2004 22:17, Tres Seaver wrote:
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 [EMAIL PROTECTED] Zope Corporation "Zope Dealers" http://www.zope.com
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce