<br><br><div class="gmail_quote">On Tue, Oct 20, 2009 at 07:57, Mark Dickinson <span dir="ltr"><<a href="mailto:dickinsm@gmail.com">dickinsm@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Tue, Oct 20, 2009 at 3:50 PM, Eric Smith <<a href="mailto:eric@trueblade.com">eric@trueblade.com</a>> wrote:<br>
>> The code was working a few months ago (with all Decimal tests<br>
>> passing), but there have been some changes and bugfixes since<br>
>> then. I might try to resurrect that code, dropping the _Decimal type and<br>
>> just concentrating on Deccoeff.<br>
><br>
> My only concern about this is the effect it would have on IronPython,<br>
> Jython, PyPy, and other alternate implementations that use the stdlib.<br>
<br>
</div>Yes, that worries me a bit, too. I have the same worry with the idea<br>
of rewriting the entire decimal module in C.<br>
<br>
The Deccoeff type is very simple, though. It would be easy to create<br>
a pure Python version of it, and then do something like:<br>
<br>
try:<br>
from _decimal import Deccoeff # try to get C version<br>
except ImportError:<br>
from deccoeff import Deccoeff # else use Python fallback code.</blockquote><div><br></div><div>And this is why you shouldn't have to worry. As long as the tests exercise both the pure Python and C versions then the other VMs are covered.</div>
<div><br></div><div>-Brett </div></div>