-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 17 Apr 2006, at 12:02, Jerry Westrick wrote:
On Monday 17 April 2006 11:10, Jens Vagelpohl wrote:
My question now is this a bug in Zope 2.9.2 installation, or in
SUSE 10.1 RC1?
The answer to that will decide where I look to fix it....
Very simple test: Compile Python yourself. Do not use the
distribution package. Then try building Zope 2.9.2 against the self-
compiled Python. If it works fine then it's a SuSE fault.
Python packages shipped with distributions are known to show various
weirdnesses. For production setups I would never even consider using
the built-in Python, regardless of distribution.
jens
Well Jens, I disagree.
If I where to build my own python, I would have to do formal testing
on all packages which require python, which are quite a few.
I think you misunderstand what I am saying. I did not tell you to
*replace* the system Python. By default, the Python source package
installs into /usr/local.
jens
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFEQ2kgRAx5nvEhZLIRAupFAKCiognz3aR1lPgIrot1GTeg0/MyowCgl3hG
SaWjfJcGIrp7sG5wEg5JRmU=
=qeWc
-----END PGP SIGNATURE-----
_______________________________________________
Zope maillist - [email protected]
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
