Chris McDonough wrote:

Hi Craeg,

2.6.X appears to work great with Python 2.2. We even removed the startup warning lately. I'd go this way were I you as 2.7 is probably still some time away and you almost certainly don't want to be tracking the trunk, as its relatively volatile at the moment.

Hi Craeg, I run 2.6.1 with Python 2.2.2 with several additional products without any problems. I learnt my lessons from upgrading to early major releases of Zope, so I would go for 2.6.1 with Python 2.2.2 instead of waiting for a (maybe) buggy release of 2.7.0... Cheers, Maik

Craeg - The safest thing to do is to build Zope from source using Python 2.2. I do not recommend replacing the binary distro's Python with Python 2.2 (using C extensions compiled with earlier versions of Python will at least generate warnings and may actually cause problems). This is obviously going to be a problem Windows. I don't have any answers for you there. This is one of the reasons that Zope is 'not officially supported' under Python 2.2. There are no Py22/Zope2.6.X binary distros available and no step-by-step upgrade procedures to retrofit an existing 2.6 binary installation with Python 2.2. About the best you can hope for is to persuade someone to compile Zope on Windows under Python 2.2 for you, and even then it's not clear that Zope will be guaranteed to run as a service (the Wise installer script ZC uses to make binary Windows releases does all of this magic and is not distributed with Zope). Or wait for 2.7. - C PS - this is a good excuse to ditch Windows. ;-) On Fri, 2003-03-21 at 12:23, Craeg K Strong wrote:

Thanks much for the quick response. And good news, too!

Hum. In your opinion, what is the best way to do this? My constraints:

- I use both windows 2000 and Red Hat Linux 8 - I do *not* have a C/C++ compiler on Windows

Do I need to build Zope from source in order to use Python 2.2? Or can I simply get rid of $ZOPE/lib/python2.1 and replace it with $ZOPE/lib/python2.2 (retrofit)? What are the ramifications of this choice?

Sorry for so many questions; I am trying to get the most stable setup I can, while doing the least amount of setup work :-)

Thanks very much!

--Craeg

BTW, The answers to these questions should probably be on zope.org or in a wiki somewhere, do you agree?

Chris McDonough wrote:

...

Hi Craeg,

2.6.X appears to work great with Python 2.2. We even removed the startup warning lately. I'd go this way were I you as 2.7 is probably still some time away and you almost certainly don't want to be tracking the trunk, as its relatively volatile at the moment.

- C

On Fri, 2003-03-21 at 02:42, Craeg K Strong wrote:

...

Hello:

I am using multiple third party Python libraries with Zope, and they are no longer supporting Python 2.1.X at all. I am forced to upgrade to Python 2.2.X

copies -- including electronic copies -- of the original message.

_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )

Yes, a build of Zope 2.6.1 using Python 2.2.2 would be fantastic! I understand it would not be officially supported, but it would give me the chance to test out my zope products using the latest Python. I am not sure if you could post the binaries somewhere public, but my guess is that they would probably be useful for others in the same situation. Of course you would want to put a disclaimer there about support in BOLD letters :) Thanks again for the offer! --Craeg Chris Withers wrote:

Craeg K Strong wrote:

...

Thanks much for the quick response. And good news, too!

Hum. In your opinion, what is the best way to do this? My constraints:

- I use both windows 2000 and Red Hat Linux 8 - I do *not* have a C/C++ compiler on Windows

I do ;-)

Anything in particular you'd like a build of?

cheers,

Chris