Proposal: Rename zope package
Based on recent discussions, I've created a proposal: http://dev.zope.org/Zope3/RenameTheZopePackage to rename the "zope" package to "z". Unless there are strong objections, we'll do this after we move the Zope repository head to subversion at the end of the month. Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org
Jim Fulton wrote:
Based on recent discussions, I've created a proposal:
http://dev.zope.org/Zope3/RenameTheZopePackage
to rename the "zope" package to "z". Unless there are strong objections, we'll do this after we move the Zope repository head to subversion at the end of the month.
From a consistency in nomenclature POV, I find 'z' jars a bit with ZConfig, zdaemon, ZEO, zLog, and ZODB, which one might expect to find nested within 'z' (as 'z.Config' for example). This is admittedly only an issue for the newest newbies still trying to guess at where stuff is located. However, rather than suggest a wholesale moving and renaming of these packages within 'z', I'd like to suggest an alternative short name for the 'zope' package, 'OPE', which avoids this issue: import OPE.interface from OPE.app import zapi from OPE.app.event import publish from OPE.app.event.objectevent import ObjectModifiedEvent Cheers, -- - Michael R. Bernstein
On Friday 16 April 2004 01:31 pm, Michael Bernstein wrote:
From a consistency in nomenclature POV, I find 'z' jars a bit with ZConfig, zdaemon, ZEO, zLog, and ZODB, which one might expect to find nested within 'z' (as 'z.Config' for example). This is admittedly only an issue for the newest newbies still trying to guess at where stuff is located.
I don't know what zLog is; presumably you mean zLOG? zLOG is dead in Zope 2.8, and will remain only for API compatibility. I don't think there's any real consistency now for what's in the Zope 2 head, so I don't think that's a big deal.
However, rather than suggest a wholesale moving and renaming of these packages within 'z', I'd like to suggest an alternative short name for the 'zope' package, 'OPE', which avoids this issue:
import OPE.interface from OPE.app import zapi from OPE.app.event import publish from OPE.app.event.objectevent import ObjectModifiedEvent
Hehe. ;-) (I do hope you're joking!) -Fred -- Fred L. Drake, Jr. <fred at zope.com> PythonLabs at Zope Corporation
Fred Drake wrote:
On Friday 16 April 2004 01:31 pm, Michael Bernstein wrote:
From a consistency in nomenclature POV, I find 'z' jars a bit with ZConfig, zdaemon, ZEO, zLog, and ZODB, which one might expect to find nested within 'z' (as 'z.Config' for example). This is admittedly only an issue for the newest newbies still trying to guess at where stuff is located.
I don't know what zLog is; presumably you mean zLOG?
Yep.
zLOG is dead in Zope 2.8, and will remain only for API compatibility.
I don't think there's any real consistency now for what's in the Zope 2 head, so I don't think that's a big deal.
Shouldn't we strive for consistency in nomenclature going forward?
However, rather than suggest a wholesale moving and renaming of these packages within 'z', I'd like to suggest an alternative short name for the 'zope' package, 'OPE', which avoids this issue:
import OPE.interface from OPE.app import zapi from OPE.app.event import publish from OPE.app.event.objectevent import ObjectModifiedEvent
Hehe. ;-)
(I do hope you're joking!)
About even considering a 'wholesale moving and renaming' yes, obviously, but as far as suggesting 'OPE' as an alternative to 'z' (insofar as it is still necessary to avoid a name-clash with 'Zope'), no. 'OPE' (as an acronym for Object Publishing Environment) seems like it fits better conceptually than 'z'. Did I miss something? Did I just manage to embarrass myself? Is this a dream where I find I am wearing nothing but underwear in public and then wake up? -- - Michael R. Bernstein michaelbernstein.com Author of Zope Bible
On Friday 16 April 2004 03:06 pm, Michael Bernstein wrote:
Shouldn't we strive for consistency in nomenclature going forward?
Definately. My point was that we don't have anything to base it on, not that we shouldn't be. Zope 3 kindly specifies some guidelines for naming, including module and package names. I'm not convinced "z" follows those guidelines (actually, I'm also not convinced it doesn't, given that the official expansion for ZOPE is the "Z Object Publishing Environment").
About even considering a 'wholesale moving and renaming' yes, obviously, but as far as suggesting 'OPE' as an alternative to 'z' (insofar as it is still necessary to avoid a name-clash with 'Zope'), no. 'OPE' (as an acronym for Object Publishing Environment) seems like it fits better conceptually than 'z'.
From where I stand, calling it "OPE" (or "ope", or "Ope") are all the same mistake as "Interface", "transaction", "persistent", "Persistence", etc: taking a very general term and using that for a specific implementation. We're not dealing with some abstract or archtypical object publishing environment, we're dealing with a specific one. Whether or not "z" is a good name for it is another question altogether. ;-)
Did I miss something? Did I just manage to embarrass myself? Is this a dream where I find I am wearing nothing but underwear in public and then wake up?
That's better than dreaming you're wearing a suit in a dream, and waking up wearing nothing but your underwear in public. ;-) -Fred -- Fred L. Drake, Jr. <fred at zope.com> PythonLabs at Zope Corporation
Michael Bernstein wrote:
Fred Drake wrote:
Hehe. ;-)
(I do hope you're joking!)
About even considering a 'wholesale moving and renaming' yes, obviously, but as far as suggesting 'OPE' as an alternative to 'z' (insofar as it is still necessary to avoid a name-clash with 'Zope'), no. 'OPE' (as an acronym for Object Publishing Environment) seems like it fits better conceptually than 'z'.
Did I miss something? Did I just manage to embarrass myself? Is this a dream where I find I am wearing nothing but underwear in public and then wake up?
Well, OPE made me think of: - Opie on The Andy Griffith Show - http://www.imdb.com/title/tt0053479/ - Spelling it "zOPE" to take advantage of a frequent mishap involving the cAPS lOCK key - Shouting the name of the product repeatedly in code as a method of advertising - Friday afternoon I thought it was funny. :-) Shane
On Friday 16 April 2004 03:24 pm, Shane Hathaway wrote:
- Spelling it "zOPE" to take advantage of a frequent mishap involving the cAPS lOCK key
That must be what happened for zLOG, and I declared that dead. I don't think anyone's ready for that for Zope 3 just yet. ;-) -Fred -- Fred L. Drake, Jr. <fred at zope.com> PythonLabs at Zope Corporation
Shane Hathaway wrote:
Michael Bernstein wrote:
Did I miss something? Did I just manage to embarrass myself? Is this a dream where I find I am wearing nothing but underwear in public and then wake up?
Well, OPE made me think of:
- Opie on The Andy Griffith Show - http://www.imdb.com/title/tt0053479/
- Spelling it "zOPE" to take advantage of a frequent mishap involving the cAPS lOCK key
- Shouting the name of the product repeatedly in code as a method of advertising
How about 'ope', then? Actually, I don't really care what it's changed to. Jim is right in that it needs to be changed, and I thought 'z' to be not-so-great a choice for the reasons I already gave (in addition to some of the cons that Jim lists in his proposal). An optimal choice probably doesn't exist, though.
I thought it was funny. :-)
Do I *amuse* you? ;-) -- - Michael R. Bernstein michaelbernstein.com Author of Zope Bible
Michael Bernstein wrote:
However, rather than suggest a wholesale moving and renaming of these packages within 'z', I'd like to suggest an alternative short name for the 'zope' package, 'OPE', which avoids this issue:
import OPE.interface from OPE.app import zapi from OPE.app.event import publish from OPE.app.event.objectevent import ObjectModifiedEvent
In that case, let's consider renaming it "zopepoz": Z Object Publishing Environment with Persistent Object Zystem. Palindromic and all. Or maybe just Bobo. Gotta be backward compatible. :-) Shane
participants (4)
-
Fred Drake -
Jim Fulton -
Michael Bernstein -
Shane Hathaway