Your message dated Tue, 02 Jun 2015 12:03:46 +0200
with message-id <[email protected]>
and subject line closing bugs against ancient python2.4
has caused the Debian Bug report #334022,
regarding python2.4: incomplete numerical comparisons
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
334022: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=334022
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python2.4
Version: 2.4.2-1
Severity: normal
Hi,
I've been tracking down the regression failure in python-pgsql under
python2.4, and here's what it comes down to.
Python-pgsql includes a short int type named PgInt2, which allows itself
to be coerced into all of the usual numeric types.
The regression that fails is when a PgInt2 is compared with a float. In
this case python determines that the comparison is not implemented.
The problem is this:
- Under python2.4, the float type includes tp_richcompare but not
tp_compare.
- When calling try_rich_to_3way_compare(), python does not try any kind
of numeric coercion, and so the comparison fails.
- When calling try_3way_compare(), python successfully coerces the
PgInt2 into a float, but then the comparison fails because the float
type has no tp_compare routine.
Presumably what would fix things would be one of the following:
- Bring back the trivial float_compare() routine, which was removed with
python2.4 when they brought in the new float_richcompare() instead;
- In try_3way_compare(), if the coercion succeeds and neither object
has a tp_compare routine, try tp_richcompare before failing completely.
Does either of these solutions seem feasible?
Thanks - Ben.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages python2.4 depends on:
ii libc6 2.3.5-6 GNU C Library: Shared libraries an
ii libdb4.3 4.3.28-3 Berkeley v4.3 Database Libraries [
ii libncurses5 5.4-9 Shared libraries for terminal hand
ii libreadline5 5.0-11 GNU readline and history libraries
ii libssl0.9.7 0.9.7g-2 SSL shared libraries
ii python2.4-minimal 2.4.2-1 A minimal subset of the Python lan
python2.4 recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
python2.4 has been obsoleted in Debian long ago. I'm now closing the
remaining bugs against this ancient version, assuming they have been
fixed (or became irrelevant) in newer releases.
Feel free to provide more information and reopen the bugs if they are
still reproducible in the current versions (python2.7, python3.x).
Andreas
--- End Message ---
