Re: [Zope-dev] naming Zope

2009-04-12 Thread Chris Rossi
On Sat, Apr 11, 2009 at 9:05 PM, Chris McDonough wrote: > On 4/11/09 7:32 PM, Roger Ineichen wrote: > > >> That much dependency cleanup would be fantastic. > > > > Yes, cool, but what exactly whould you like to cleanup? > > The bits that I use are already pretty nicely cleaned up. But in theory,

Re: [Zope-dev] naming Zope

2009-04-09 Thread Chris Rossi
I can't believe no one's suggested Zope Mega, yet. Chris On Thu, Apr 9, 2009 at 4:25 PM, Martijn Faassen wrote: > Hey, > > Joy, another naming discussion. Oh well, I started it. :) > > Zope Toolkit is better name than Zope Framework. I'm fine with renaming > Zope Framework to Zope Toolkit if: >

Re: [Zope-dev] Constant values defined in interfaces

2009-04-04 Thread Chris Rossi
On Sat, Apr 4, 2009 at 6:04 PM, Chris McDonough wrote: > Using an interface class for a constant "container" would often be handy > but it > might be an inappropriate use of interface classes. I would argue that it is appropriate, but that's probably related to my experience with languages othe

Re: [Zope-dev] Constant values defined in interfaces

2009-04-04 Thread Chris Rossi
On Fri, Apr 3, 2009 at 7:21 PM, Wichert Akkerman wrote: > Previously Chris Rossi wrote: > > I was wondering if the Zope collective had given any consideration to > > allowing constants to be defined in interfaces. To be clear, these are > > constant values that make up th

Re: [Zope-dev] Constant values defined in interfaces

2009-04-03 Thread Chris Rossi
On Fri, Apr 3, 2009 at 1:55 PM, Gary Poster wrote: > > How would that be a win for you (or anybody else) over just putting the > constant in the interfaces module? > Standard practice seems to favor putting several interfaces in a single "interfaces" module, so just putting the constants in the

[Zope-dev] Constant values defined in interfaces

2009-04-03 Thread Chris Rossi
Hello, I was wondering if the Zope collective had given any consideration to allowing constants to be defined in interfaces. To be clear, these are constant values that make up the protocol defined by the interface. Just to have a concrete example, let's say we're modeling an http response: cla

Re: [Zope-dev] Two small convenience suggestions for zope.interface and zope.component

2009-04-01 Thread Chris Rossi
Additionally, if I was grokking Lennart correctly yesterday, __metaclass__ is going away, so the current metaclass implementation is going to need some rejiggering. What was unclear was whether a single implementation could support both <=2.5 and >=2.6. Chris On Wed, Apr 1, 2009 at 1:09 PM, Mar