[ hpinson@indepthl.com]

My mistake, but given that, any sense if I can I safely ignore the warning?

It's a DeprecationWarning. All it means is that Python's `whrandom` module is going to go away in a future release -- it's advising applications to switch to using the `random` module if they want to continue to work under future releases. It's purely advisory, and in no sense points at "a problem".

So far, things seems to be running well under Python 2.4.2. The instance contains a Plone 2.1 site and lots of DTML/ZSQL stuff, which appear unaffected.

Python 2.4.2 works fine. That's not the concern. The Zope concern for moving to any new Python release isn't that Python may be buggy, it's that a new Python release may introduce new behaviors that open "security holes" in Zope. Until a security audit is performed (which is done by expert humans), and any new security holes that may be discovered get plugged, 2.4.2 will remain unsupported for use with Zope 2. In contrast, Python 2.4 is now _required_ for Zope 3 development. Zope 3 has a different approach to security, which isn't as sensitive to changes in Python.

Andreas, Aside from a "security audit" what problems have been reported using Python 2.4.X? Those of use who run Python 2.4.X do it becasue we want access to the language features and performance. If there are stability issues attributed to that choice, we'd like to know what they are. If the reason for trying to stick with 2.3.5 is to maintain a stable test and development environment for Zope 2.8, so be it. It is much much easier to fix one of the multitude of possible variables in a complex system. I, for one, have occasionally created a special instance of Zope running a different Python to ensure a problem I had discovered was not python version related. -d On Fri, 14 Oct 2005, Andreas Jung wrote:

--On 14. Oktober 2005 10:09:39 -0600 hpinson@indepthl.com wrote:

...

Hello. On starting and stopping Zope 2.8.2 (upgraded from 2.8.1, compiled with Python 2.4.2, running on Fedora Core 3) I get the following error. Performance does not seem to be affected. Resolution?

Quote from my announcement yesterday:

""" Please also keep in mind that Zope 2.8.2 requires Python 2.3.5. Zope 2.8.2 is not certified for any Python 2.4.x versions. So using Python 2.4 is neither recommended nor supported and any related questions or problems are likely to be ignored until 2.4 is an officially supported Python version for Zope. """

:-)

-aj

--

Aside from a "security audit" what problems have been reported using Python 2.4.X? Those of use who run Python 2.4.X do it becasue we want access to the language features and performance. If there are stability issues attributed to that choice, we'd like to know what they are.

Just one example: I tried running Zope 2.8.1 with Python 2.4.1 on a FreeBSD box and CalendarX barfed with some errors in the templates. Changing to Python 2.3.5 made these disappear. You will surely find more using google or gmane... Regards Maik

--On 16. Oktober 2005 11:27:36 -0700 Dennis Allison <allison@shasta.stanford.edu> wrote:

whrandom is a deprecated python library package which should be replaced by random. Python 2.3.5 does not produce the deprecation warning but lacks some of the features of the Python 2.4.X series.

It is already replaced on the trunk but there is no need to replace it on the 2.8 branch. Once again: Python 2.4 is not supported for Zope 2.8 and therefore there is no need to replace something for an unsupported configuration. Such changes can be made for major release but not after the seconds minor release. The 2.8 branch is in general closed for new features. This change is neither a bugfix nor a feature request...this warning is just a warning as the name says...if it worries you, close your eyes :-) -aj