On Fri, Jul 22, 2011 at 11:37 PM, Eviatar wrote:
> I guess by "modular" I meant that the different components can be
> installed separately, which is not really the case with Sage (except
> with the extra spkgs). I like the all-in-one approach better anyways
> but, like you said, there is also an
On Fri, Jul 22, 2011 at 8:57 PM, Eviatar wrote:
> Oh, I see. It would be nice if Sage was more modular.
>
> Good luck with Qsnake!
And things like Qsnake are possible... because Python is very modular.
-- William
> On Jul 22, 7:51 pm, Ondřej Čertík wrote:
>> On Fri, Jul 22, 2011 at 6:19 PM, W
On Fri, Jul 22, 2011 at 6:19 PM, William Stein wrote:
> On Fri, Jul 22, 2011 at 5:56 PM, Eviatar wrote:
>> Just out of curiosity: why are you forking a separate project instead
>> of developing Sage?
>
> I think the main issue is that Sage contains a lot of dependencies and
> code that are not ne
On Fri, Jul 22, 2011 at 5:56 PM, Eviatar wrote:
> Just out of curiosity: why are you forking a separate project instead
> of developing Sage?
I think the main issue is that Sage contains a lot of dependencies and
code that are not needed for people doing Finite Element Method (say)
work. But non
On Wed, Feb 17, 2010 at 11:47 AM, Ondrej Certik wrote:
> On Wed, Feb 17, 2010 at 11:34 AM, Ethan Coon wrote:
>> Ok, so I uploaded an spkg, but it's not exactly right yet. A few issues:
>>
>> 1. my stupidity -- the flag should actually be --FLIBS="f95" , not
>> --FFLAGS="-lf95*". This isn't nece
