On Tue, Jul 1, 2008 at 8:03 AM, Robert Miller <[EMAIL PROTECTED]> wrote:
> William,
>
> There were several awesome projects in your Sage class last quarter
> that I haven't seen any trac tickets about. For example, did Ryan
> Dingman ever send you a patch for his tree generation stuff? What
> abou
On Tue, 1 Jul 2008, Carl Witty wrote:
>
>>> I can't find any caching for fast_float objects (I can't see anywhere
>>> they would get attached to a symbolic expression or a polynomial). Am
>>> I just not looking in the right place?
>>
>> Compiled polynomials get attached to polynomial objects,
> > I can't find any caching for fast_float objects (I can't see anywhere
> > they would get attached to a symbolic expression or a polynomial). Am
> > I just not looking in the right place?
>
> Compiled polynomials get attached to polynomial objects, but if
> you're not seeing fast floats gett
>> I think common subexpressions should be (loosely) checked for
>> equality, *not* restricting to the same Python instance only.
>
> Hmm... this is a tradeoff between speed in constructing the
> fast_callable and speed in using it. Do other people think that
> common subexpressions are likely?
On Jun 30, 11:44 pm, Robert Bradshaw <[EMAIL PROTECTED]>
wrote:
> As the author of the original fast_float stuff, I want to give a big
> +1 to this project. I've been wanting to do something like this for
> some time but it's never gotten high enough on my priority list to
> actually code up
Great !
Thanks ! (i must have missed something in the docs ;-)
Philippe
On Tue, Jul 1, 2008 at 2:37 AM, William Stein <[EMAIL PROTECTED]> wrote:
>>
>> but i couldn't successfully pass options to -notebook
>>
>> Can anybody give me a hint ?
>
> Use
>
> sage -c "notebook(options...)"
>
> inste
> So, where does this leave giac? You're probably no going to find
> someone currently involved with Sage who wants to work on it with you.
> If you want to further its incorporation into Sage, here's what you
> can do. The first step would be making giac an experimental spkg.
> Personally, I k
> At every stage of this process, you should be able to find help in
> answering questions that come up. Whether you can find someone else
> to chip in and contribute to the work depends on who else is excited
> about getting giac into Sage. But you should feel free to go ahead
> and go through
> BTW, I have also modified giac source, it should now compile with gcc
> 4.3.1.
Excellent!
> As I said earlier, I'm ready to invest time for that, but I can't do
> it alone, there must be someone on the python side who has time and
> interest to do it with my help.
I've seen a lot of acrimonio
