On Tue, Sep 22, 2009 at 14:51, Ryan Krauss wrote:
> I just lost a few hours of my day to a problem that turn out to be cse
> returning things like
>
> expr**(3/2)
>
> I wrote some code to take the cse output and autogenerate some Python code I
> was using with numpy and numerical analysis. How d
I just lost a few hours of my day to a problem that turn out to be cse
returning things like
expr**(3/2)
I wrote some code to take the cse output and autogenerate some Python code I
was using with numpy and numerical analysis. How difficult would it be to
add an option to cse to make it output e
On Tue, Sep 22, 2009 at 12:51 PM, Ryan Krauss wrote:
> I just lost a few hours of my day to a problem that turn out to be cse
> returning things like
>
> expr**(3/2)
>
> I wrote some code to take the cse output and autogenerate some Python code I
> was using with numpy and numerical analysis. Ho
On Tue, Sep 22, 2009 at 1:07 PM, Ondrej Certik wrote:
> On Tue, Sep 22, 2009 at 12:51 PM, Ryan Krauss wrote:
>> I just lost a few hours of my day to a problem that turn out to be cse
>> returning things like
>>
>> expr**(3/2)
>>
>> I wrote some code to take the cse output and autogenerate some P
I am using my own codegeneration tool. Basically, I take the output of cse
and convert it all to strings and save it to a file. My stuff can be fixed
with
from __future__ import division
in the module. So, I guess it isn't critical. I don't want the module that
gets generated to depend on sym
On Tue, Sep 22, 2009 at 8:07 PM, Ryan Krauss wrote:
> I am using my own codegeneration tool. Basically, I take the output of cse
> and convert it all to strings and save it to a file. My stuff can be fixed
> with
>
> from __future__ import division
>
> in the module. So, I guess it isn't criti
