[Zope] Python 1.5.2 on Slackware 4.0

[Alexander Staubo]

Zope requires libc6. That is, glibc-2.x.x. Although glibc-2 is in a flux
these days -- knowledgeable people have been unable to furnish me with a
good answer to the question "Which should I use?", but 2.0.6 (iirc) should
be the most stable. 2.0.7 (again, iirc) fixes some threading problems but
isn't done. This was a month ago or so; things may have changed since then.

Python can live happily with the libc5 that comes with Slackware, but some
features -- like the time module -- will not be available.

Unfortunately, the tale does not end here. We've had problems with Python
1.5.2 and glibc 2.0.6 on Slackware. Zope 1.x seems to work fine in this
environment, but Zope 2.x simply crashes with a core dump. Same thing
happens with dynamically loaded (.so) Python extension modules, including my
own which work perfectly elsewhere. There is evidently a glitch somewhere
that makes libc6 unstable on Slackware.

The response from Digital Creations has essentially been "Sorry, no
Slackware support". They don't run it themselves, so they can't test it out.

For more information, you might want to give the Python and/or Linux
newsgroups a shot. Also see the glibc documentation. And if you find a way
to run glibc-2 flawlessly on Slackware, could you please let us know?

--
Alexander Staubo  |  http://www.mop.no/~alex/
"What the hell, he thought, you're only young once, and threw
himself out of the window. That would at least keep the element of
surprise on his side."
--Douglas Adams, _The Hitchhiker's Guide to the Galaxy_

>-----Original Message-----
>From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of news
>Sent: 9. september 1999 16:02
>To: zope@zope.org; support@slackware.com
>Subject: [Zope] Python 1.5.2 on Slackware 4.0
>
>
>Has anyone been sucessful in installing Python 1.5.2 on Slackware 4.0?
>A good part of it runs without any problem, however, some of the
>key modules
>do not work.
>
>Some have suggested that my Python installed was hosed. I've checked Deja
>and the web and have not found reference to this problem. Python folks have
>said it's a glibc version problem.  Having some trouble with the
>time module
>specifically when I run the following test:
>
> /tmp/Python-1.5.2$ python
> Python 1.5.2 (#3, Sep  8 1999, 17:29:29)  [GCC 2.7.2.3] on linux2
> Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam
> >>> import time
> >>> time.daylight
> Traceback (innermost last):
>   File "<stdin>", line 1, in ?
> AttributeError: daylight
> >>>
>
> Here's how & what I installed.
>
>Slackware 4
>Linux version 2.2.6(gcc version 2.7.2.3) #11 Wed Jul
>Console: colour VGA+ 80x25
>Memory: 30592k/32576k available (956k kernel code, 412k reserved,
>568k data,
>48k init)
>CPU: Intel Mobile Pentium MMX stepping 01
>
>Downloaded py152.tgz from ftp.python.org and uncompressed/untarred it into
>/tmp/Python-1.5.2
>
>
>
>
>_______________________________________________
>Zope maillist  -  Zope@zope.org
>http://www.zope.org/mailman/listinfo/zope
>
>(To receive general Zope announcements, see:
>http://www.zope.org/mailman/listinfo/zope-announce
>
>For developer-specific issues, zope-dev@zope.org -
>http://www.zope.org/mailman/listinfo/zope-dev )
>