... which doesn't help people trying to run a current zope source
release all that much...
jens
On Monday, Aug 26, 2002, at 17:13 US/Eastern, Jeffrey P Shell wrote:
> On 8/26/02 11:49 AM, "Jens Vagelpohl" <[EMAIL PROTECTED]> wrote:
>
>> well, the basic cause is worse than that: they moved symb
On 8/26/02 11:49 AM, "Jens Vagelpohl" <[EMAIL PROTECTED]> wrote:
> well, the basic cause is worse than that: they moved symbols around
> between system libraries.
>
> jens
But nicely, they include Python (2.2, not even 2.2.1) on the Developer Tools
CD. Finally.
--
Jeffrey P Shell
www.cuemed
Hello:
In order to use the unit testing facility for my custom Zope Products under
FAT in win32, I had to do the following:
In the file name::
[ZOPE]\lib\python\Testing\custom_zodb.py
Where ZOPE stands for the directory in which you installed Zope,
Change line number seven::
St
well, the basic cause is worse than that: they moved symbols around
between system libraries.
jens
On Monday, Aug 26, 2002, at 12:11 US/Eastern, Barry A. Warsaw wrote:
>
>> "JV" == Jens Vagelpohl <[EMAIL PROTECTED]> writes:
>
> JV> sorry for the crossposting, here's a little heads-up f
> "JV" == Jens Vagelpohl <[EMAIL PROTECTED]> writes:
JV> sorry for the crossposting, here's a little heads-up for the
JV> mac OS X crowd:
JV> upon upgrading to 10.2 (jaguar) you will most likely find that
JV> your python binary (along with most other self-compiled
JV> so
sorry for the crossposting, here's a little heads-up for the mac OS X
crowd:
upon upgrading to 10.2 (jaguar) you will most likely find that your
python binary (along with most other self-compiled software) is broken.
in the case of python a simple re-build (if you compiled from source,
that i
On Friday 23 Aug 2002 3:59 pm, Jeremy Hylton wrote:
> We've just released ZEO 2.0 beta 1.It's available from
> http://www.zope.org/Products/ZEO.
>
> We think this release of ZEO 2 is fairly stable,
hurrah!
> although we may do
> one more beta release to add some performance improvements.
Do you
