[Zope] Zope "picky" on Redhat Linux with Python1.5.2 and 2.2

[Shriek@gmx.co.uk]

> > install with the command 
> > /usr/bin/python2 w_pcgi.py
> > 
> > But then it failed with a rather funny-sounding "if i and picky" error.
> 
> IIRC, this is a directory permissions error. ISTR that if I chown -R the
> Zope source tree such that the whole tree is owned by the current user,
> it goes away.

Thanks for the tip. Tried that (chown -R root.root Zope-2.5.0) and then
/usr/bin/python2 w_pcgi.py but still the same error unfortunately.

cp /usr/lib/python2.2/config/Makefile.pre.in .
cp: cannot stat `/usr/lib/python2.2/config/Makefile.pre.in': No such file or
directory
Traceback (most recent call last):
  File "/usr/local/Zope-2.5.0/w_pcgi.py", line 39, in ?
    if __name__=='__main__': main(sys.argv[0])
  File "/usr/local/Zope-2.5.0/w_pcgi.py", line 37, in main
    import wo_pcgi; wo_pcgi.main(me)
  File "/usr/local/Zope-2.5.0/wo_pcgi.py", line 33, in main
    import build_extensions
  File "/usr/local/Zope-2.5.0/inst/build_extensions.py", line 30, in ?
    make('lib','python')
  File "/usr/local/Zope-2.5.0/inst/do.py", line 61, in make
    do("cp %s ." % wheres_Makefile_pre_in())
  File "/usr/local/Zope-2.5.0/inst/do.py", line 32, in do
    if i and picky: raise SystemError, i
SystemError: 256

No worries, I'm going to use the binary instead (although I've yet to work
out whether the MySQLdb module _mysql can be installed into it - that's
usually why I prefer installing from source).


> > So, I'm wondering how should I install Python2.5 on Redhat linux ? 
> > Use the binary Zope-2.5.0-linux2-x86 but then change my default Python
> to
> > Python2 and risk breaking some Redhat programs (!) ? 
> 
> It isn't a "risk" it's a guarantee. 

That's what I feared. :(

>You basically break all of their
> printing system, as well as much of their configuration tools. I've done
> this on machines, and rebuilt their tools to use python2, but it wasn't
> exactly pretty. They *need* to make their stuff explicitly call the
> appropriate python if it isn't (for some odd reason) forward compatible.

They'd probably say it was due to python2 not being backwards compatible :)
Either way, it's a shame for everybody. 

> Another option may be to change the /usr/bin/python to
> /usr/bin/python1,5 in all their scripts.

Yowzers, think I'll stick to the Zope binary :)

Stephen

-- 
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net