[pypy-dev] problems compiling with complex

Christian Tismer tismer at stackless.com
Sat Feb 11 22:44:43 CET 2006


Armin Rigo wrote:
> Hi Christian,

Wrong address. You are right, of course.

>> You are also raising standard exceptions with argumens, which
>> is not supported (thanks Samuele).
> 
> Raising then is fine, in the sense that you can say
> 
>     raise ValueError("some message")
> 
> but the message itself is lost in RPython, so you cannot read it back in
> complextype.py:159:
> 
>     except ValueError, e:
>         raise OperationError(space.w_ValueError, space.wrap(e.msg))
> 
> Also note that space.float_w() isn't supposed to raise ValueErrors,
> either.  It should directly raise the correct OperationError, and you
> shouldn't have to worry about catching it.  If it's not the case then
> something is wrong with float_w().

This is fine, but you shouldn't tell me, I'm just the trainer, here.

-- 
Christian Tismer             :^)   <mailto:tismer at stackless.com>
tismerysoft GmbH             :     Have a break! Take a ride on Python's
Johannes-Niemeyer-Weg 9A     :    *Starship* http://starship.python.net/
14109 Berlin                 :     PGP key -> http://wwwkeys.pgp.net/
work +49 30 802 86 56  mobile +49 173 24 18 776  fax +49 30 80 90 57 05
PGP 0x57F3BF04       9064 F4E1 D754 C2FF 1619  305B C09C 5A3B 57F3 BF04
      whom do you want to sponsor today?   http://www.stackless.com/



More information about the Pypy-dev mailing list