Is it possible to have class methods on ZODB Persistent objects? I am
using 3.2 so that means I am using ExtensionClass.
I guess that moving to 3.3 would mean being able to use class methods?
What is the expected time that the 3.3 release will be ready for
production use?
Fred Drake wrote:
On Thursday 15 April 2004 13:22, Martijn Faassen wrote:
If somebody lets me know which API they want implemented for retrieving
imports (and use of imports) I could do this lifting work myself.
I'm not sure simply re-implementing one of the finddeps.py internal interfaces
is
Syver Enstad wrote:
Is it possible to have class methods on ZODB Persistent objects? I am
using 3.2 so that means I am using ExtensionClass.
I guess that moving to 3.3 would mean being able to use class methods?
What is the expected time that the 3.3 release will be ready for
production use?
I
On Thu, 15 Apr 2004 20:40:09 -0400 (EDT)
Shane Hathaway [EMAIL PROTECTED] wrote:
On Wed, 14 Apr 2004, Kapil Thangavelu wrote:
although i wonder if there is some hand waving in progress here that
i can't see. i guess my semantic notion of versions has been that of
long lived transactions,
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
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
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
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
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
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
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
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.
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 -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/04/2004, at 3:34 PM, Tres Seaver wrote:
I haven't looked at the code. Do you have actual experience using
core sessions over ZEO? I pondered that recently for a client, and
fell back to using a hacked together version of Anthony Baxter's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/04/2004, at 4:28 PM, Kapil Thangavelu wrote:
fwiw, Simon Eisenmann checked in a SessionStorage product into the
collective which does much the same. released under the zpl
http://cvs.sourceforge.net/viewcvs.py/collective/SessionCrumbler/
Looks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/04/2004, at 1:40 PM, Shane Hathaway wrote:
On 04/12/04 09:04, Chris Withers wrote:
For me, that's worth patching for, it's up to you if you want to
include it in an offical CookieCrumbler release or not ;-)
BTW, I wouldn't mind if you or Stuart
On Sat, 17 Apr 2004, Stuart Bishop wrote:
BTW, I wouldn't mind if you or Stuart took over maintainership of
CookieCrumbler after the next release. Then you'd be able to take it
any direction you want. I don't believe its model can support well
the things you're asking it to do, but
17 matches
Mail list logo