On Thu, May 03, 2001, [EMAIL PROTECTED] wrote:
> All the while, Mike referred to the
> Red Hat systems as broken (which may be true for all I know, but there
> is no evidence of it), without considering the possibility that plucker
> may be broken. I don't know if it is, but we should all be open to the
> possibility. Mike clearly isn't, which was my complaint.
You're so full of it.
According to you the fact that I don't do some firsthand debugging
means I neither care about this problem or accept the possibility
that it could be a bug in the python parser.
However, in another message you write that I have offered several
things to try (seems like I care after all) and that you don't
expect me to be able to do some debugging since I can't reproduce
the problem.
Hmmm...
Whatever you are smoking you better stop before it hurts your logical
senses even more.
When you reported this problem last year I told you from the very
beginning that I'm not a python developer and that I would leave it
to the python experts to tell us why this happens. Still, you start
attacking me for not doing something about this problem. Go figure.
Now about this "fact" that I should dislike (maybe even hate) Red
Hat. What do you base that on? An item in the FAQ (which is more
or less a verbatim copy of a message Jon �slund sent to plucker-list
and he is a Red Hat user so you can't accuse him of hating Red Hat)
and a couple of messages to the mailing list where I state that it
*seems* like there is a problem in Red Hat's version of python and
offer a workaround for it.
The fact remains that it is ONLY Red Hat 7.0 and now also 7.1 users
that report this problem and installing python 2.0 available from
python.sourceforge.net solves the problem.
I will continue to tell RH users about the workaround for the python
problem. If that makes you upset, then that's your problem. I don't
care.
BTW, if you get so pissed about my messages to the mailing list,
then for heaven's sake stop reading them. No one force you to read
my messages.
/Mike
