Recent changes to feature-requests

Patch for fixedpoint to respect locale settings

Harald Armin Massa — Mon, 10 May 2004 08:26:58 -0000

fixedpoint is currentyl "locale agnostic"

That is: here in Germany the decimal_point is comma.
Fixedpoint ignores it and is so basically useless when
converting strings to fixedpoint (no, replace(",",".")
is not an option)

The following patch around _parser can fix this issue.

Open Issue locale must be set before importing
fixedpoint. Getting dynamic changes would require
re-compiling the parser string.

New Code:

import locale

_t=r"""
\s*
(?P<sign>[-+])?
(
(?P<int>\d+) (\%(decimal_point)s (?P<frac>\d*))?
|
\%(decimal_point)s (?P<onlyfrac>\d+)
)
([eE](?P<exp>[-+]? \d+))?
\s* $
""" % locale.localeconv()

_parser = re.compile(_t, re.VERBOSE).match

del re
del locale

Power: fp ** n

Anonymous — Tue, 14 Oct 2003 04:14:57 -0000

I suggest to add a primitive for '**'. Something like

def __pow__(self, exponent):
try:
exp = int(exponent)
except:
raise TypeError("exponent not convertable to int: "
+ `exponent`)
temp = self.copy()
if exp < 1:
while exp < 1:
temp /= self
exp += 1
else:
while exp > 1:
temp *= self
exp -= 1
return temp

Auto detect precision from value

Dennis Chuah — Wed, 29 Jan 2003 20:08:11 -0000

If FixedPoint is constructed with:

FixedPoint ("123.456"), you actually get FixedPoint
("123.45", 2), or whatever the default precision is.

It would be better if the precision is not specified, that
the constructor recognised that value is string and set
the precision according to the number of decimal places
in the string.

Same comment for when it it constructed with another
FixedPoint object:

a = FixedPoint ("123.456", 3)
b = FixedPoint (a)

b should be set to the same precision as a.