Issue 997100: optparse.py:668 triggers FutureWarning (original) (raw)

Created on 2004-07-24 15:20 by melicertes, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (7)
msg21790 - (view)	Author: Charles (melicertes)	Date: 2004-07-24 15:20
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>"
msg21791 - (view)	Author: Greg Ward (gward)	Date: 2004-09-25 01:58
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.
msg21792 - (view)	Author: Greg Ward (gward)	Date: 2004-09-25 01:58
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.
msg21793 - (view)	Author: Matthias Andree (m-a)	Date: 2004-09-25 11:27
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.
msg21794 - (view)	Author: Greg Ward (gward)	Date: 2004-11-06 02:08
Logged In: YES user_id=14422 Closing since (I think) I fixed this in Optik 1.5a2.
msg21795 - (view)	Author: Ben Tyger (hydrian)	Date: 2005-04-01 18:35
Logged In: YES user_id=685946 I am still seeing issues with Python 2.3.5 with getmail 4.3.3
msg21796 - (view)	Author: Greg Ward (gward)	Date: 2005-04-02 03:00
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.