In Python 2.3.3, importing optparse triggers a
FutureWarning on line 668:

> /usr/local/lib/python2.3/optparse.py:668:
FutureWarning:                  
> %u/%o/%x/%X of negative int will return a signed
string in 
> Python 2.4 and up 
>   return ("<%s at 0x%x: %r>" 

Logged In: YES 
user_id=14422

You didn't specify which OS this happens on; I bet it was
Fedora Core or RHEL 3.0, right?  (I found a related thread
on python-dev, and ISTR it was related to the SE-Linux
changes fiddling how the userspace heap fits into VM.)

I'm checking in a change to optik/lib/option.py that should
suppress the warning.  I'm not sure this is the right thing
to do, though, since 1) I can't reproduce it, and 2) I don't
think it will be an issue under Python 2.4, with the
continuing unification of int and long.

See
http://mail.python.org/pipermail/python-dev/2003-November/039952.html
and following messages.

Perhaps the right thing to do is just fix this in
optparse.py on the Python 2.3 branch and forget about Optik
or Python 2.4.  Hmmm.

Logged In: YES 
user_id=14422

Marking this fixed, but not closing it, pending a checkin to
optparse.py on Python 2.3 branch and confirmation that it
actually helped.

Logged In: YES 
user_id=2788

I for one have seen the warning with a Python 2.3.4 I compiled myself 
(based on SuSE's 2.3.3 source RPM) on SuSE Linux 9.1. 

Logged In: YES 
user_id=14422

Closing since (I think) I fixed this in Optik 1.5a2.

Logged In: YES 
user_id=685946

I am still seeing issues with Python 2.3.5 with getmail 4.3.3

Logged In: YES 
user_id=14422

It's highly unlikely there will be another Python 2.3
release.  If you still see this behaviour with 2.4 or 2.4.1,
let me know and I'll consider fixing it in 2.4.  Otherwise,
this bug stayss closed.  Sorry.