Tony Meyer wrote:
[Sean Darcy]

Now I wonder if the problem is that setup.py install is only installing dibbler.py in site packages. See below. Is this because it thinks ( knows? ) all the rest are already installed and dibbler.py is the only one changed ( from last night's cvs ) ?


I'm not sure what distutils uses to see if files need replacing or not, but
that was presumably the reason.  Instead of deleting the directory, you
could have also (IIRC) used --force or -f in the command-line to force
replacement.


I'll remember that.

[later]

On a related topic. This is an amd64 running fedora core 3 x86_64. I have /usr/lib for legacy 32bit apps and /usr/lib64 for 64 bit apps. I've built and installed python as a 64 bit app. There is no /usr/lib/python2.4/site-packages - at least until spambayes creates it.

Now sb works installed in /usr/lib - but it's in the Wrong Place.


This might get better answered either with a different subject or on
comp.lang.python.  I don't know enough about *nix installs of Python to know
what it normally does with libraries in this case.  You can run setup.py
with --install-lib=/usr/lib64/python2.4/site-packages (or is it
/usr/lib64/python2.4/site-packages/spambayes?) to get it to install the

Aha. I only come to this list when I have a problem. I ought to come more often.
package there if you like.  I don't know whether your Python is setup to
look there by default or not.  (There's a similar arg for changing where the
scripts end up).


Thanks. I really appreciate all the work you do on sb.

sean

_______________________________________________
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/spambayes
Check the FAQ before asking: http://spambayes.sf.net/faq.html

Reply via email to