[spambayes-dev] RE: [Spambayes] Spambayes 1.0a7 - windowsproxy_tray installation

Tony Meyer tameyer at ihug.co.nz
Sun Nov 16 22:17:20 EST 2003


> At some point in the not-too-distant past, a decision was 
> made that the Windows scripts pop3proxy_service.py and 
> pop3proxy_tray.py should be installed to the Python Scripts 
> directory along with the other command-line scripts.  It 
> seems this was a bit premature, as pop3proxy_tray obviously 
> isn't designed to be run that way.

This is my fault - I forgot about the icons.  The problem was (several
people reported it after the 1.0a6 release) that everything else *is*
installed into the python scripts directory, and so the readme tells people
to then discard the expanded archive - but they then didn't have the
contents of the (spambayes) windows directory.

> I've CC'd the 
> spambayes-dev list in hopes that someone can take a look at 
> this.

A few comments:
 * For the vast majority of people, this won't be a problem, because they'll
use the binary installer for spambayes and it'll install a frozen
pop3proxy_tray in the requested place.
 * Could the tray handle the icon files like the web ui handles it's non
python files?  (with resourcepackage)?  Would this be desirable?
 * What do other python programs do that have 'support' files?

> At the very least, we should probably stop copying it 
> to the Python\Scripts directory until the problem is fixed.

I would rather that we just came up with a solution to the missing icon
files problem and checked that in, rather than stop copying it.  After all,
it's only a copy - running the script from the expanded archive will work
fine.  If we do stop copying it, then the readme (and website?) needs to be
updated to explain which files need to be kept from the expanded archive,
and which don't.

=Tony Meyer




More information about the spambayes-dev mailing list