[Zope-ZEO] How to get rid of the cPickle and asyncore dependency hassles

[Jim Fulton]

Hi,

I'm sure many of you have lamented the hassle of having to make odd
symbolic links or copies when setting up ZEO to make sure you get the 
right revision of cPickle and asyncore.

I'm considering introducing a new package, say ZopeSpecial
that contains special versions of modules for which
Zope, ZODB, or ZEO require revisions newer than those included
with Python.

Does anyone have any reaction to this? Alternate suggestions?

Here are some things to note:

  - cPickle can reliably be overwridden if it is given
    a different name or put in a package. This is because it
    is often a Python builtin module that can't be overridden
    by manipulating the Python path.

  - The asyncore module has mutable global data that is manipulated
    by various applications and modules. It's important that
    all users of asyncore use the *same* asyncore, or at least use the
    same global data.

Jim

--
Jim Fulton           mailto:jim@digicool.com   Python Powered!        
Technical Director   (888) 344-4332            http://www.python.org  
Digital Creations    http://www.digicool.com   http://www.zope.org    

Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email
address may not be added to any commercial mail list with out my
permission.  Violation of my privacy with advertising or SPAM will
result in a suit for a MINIMUM of $500 damages/incident, $1500 for
repeats.