On 2009-Nov-02 13:35:05 +, "Dr. David Kirkby"
wrote:
>I would suggest a pull-down on the track where one could select from
>
>1) N/A - Not an upstream bug.
>2) Not yet reported upstream, but should be.
>3) Reported upstream.
>4) Fixed upstream
Sounds good to me.
>In the case of #3, the trac
On Nov 3, 2009, at 6:39 PM, Dr. David Kirkby wrote:
> Robert Bradshaw wrote:
>> On Nov 3, 2009, at 5:28 PM, Dr. David Kirkby wrote:
>>
>>> If one tries to build Sage on OpenSolaris, python will not build,
>>> complaining
>>> about a missing md5 module.
>>>
>>>
>>> File "", line 1, in
>>> File
> Symbolic Ring
> sage: SR(1) > SR(2)
> 1 > 2
> because it returns:
> sage: x > 2
> x > 2
> if x is symbolic.
Right. And of course it doesn't say whether that is true or false.
That's just an expression. Only when one asks to transform that into a
boolean value, computation is started.
Challen
Robert Bradshaw wrote:
> On Nov 3, 2009, at 5:28 PM, Dr. David Kirkby wrote:
>
>> If one tries to build Sage on OpenSolaris, python will not build,
>> complaining
>> about a missing md5 module.
>>
>>
>> File "", line 1, in
>> File "/export/home/drkirkby/sage-4.2/local/lib/python/hashlib.py
>
> Note the call to meval. That is really just a pointer to the LISP
> function meval that corresponds to Maxima's expression evaluator.
> For the ECL developers, the fact that it is so easy to develop such a
> tight interface between python and ECL could really be used as a major
> advertising p
As I and William have discovered, gnutls will not build on OpenSolaris. I had a
look at this, and have some idea what the problem is. I'm just not sure the
best
way to solve it.
1) Sun provide libgcrypt and libgpg-error
2) The Sage source tree includes those two libraries.
3) When gnutls is li
Dear William,
> This is completely orthogonal to the real question, which is about
> design. You've replaced the question of whether or not sqrt(2) > 1
> should be *simplified* automatically, by the question of how to do
> such simplifications. How to do them, is a black box that can cha
On Tue, Nov 3, 2009 at 3:22 PM, Florent Hivert
wrote:
> +1 to no simplification...
>
> Rationale: I think indeed that it is very important that the type of the
> result of an operator depends only of the type of the operands and not of
> their actual values. If > is a constructor for symbolic equ
On Tue, Nov 3, 2009 at 3:05 PM, William Stein wrote:
> This reminds me of / being a constructor for elements of QQ, no matter
> what, i.e., a/b for a and b both integers (with b!=0) is a rational,
> no matter what:
>
> sage: type(2/3)
>
> sage: type(2/1)
>
>
> This was an important design decis
> The current policy of 1 year + major release seems reasonable to me in
> practice. It might make sense to lengthen that in a few years though.
>
Yeah, this seems okay to me at this point, even though I know I
usually argue for longer and longer. Part of my practical concern is
that, from the
As a proof of concept, there is now some code attached to:
http://trac.sagemath.org/sage_trac/ticket/7377
It is just a separate python module, not explicitly placed in the sage
tree. It depends on two tickets that are ready for review. Kcrisman
has already looked at them, but they could use some
On Tue, Nov 3, 2009 at 1:02 AM, Florent Hivert
wrote:
>
> Hi
>
>> > IMHO, Sage should be aiming to be more like the professional maths
>> > package, not
>> > itunes or Firefox.
>>
>> What are they like? My main experience with deprecation in the Ma's
>> is with Maple and Magma.
>>
>> -
On Tue, Nov 3, 2009 at 4:32 AM, David Kohel wrote:
>
> I've verified that I can build sage-4.2 on my laptop running 10.6,
> but
> that singular fails (with similar errors reported in the above
> logfile) on
> two recent Mac desktop machines with the latest XCode.
>
> A pending software update to
Alex,
Nicely done, and I really like how you move from designs to graphs to
groups - it does a great job of illustrating the versatility and
breadth of Sage.
I hope a final version makes it to the right part of the wiki when you
are done with it.
Rob
--~--~-~--~~~-
If one tries to build Sage on OpenSolaris, python will not build, complaining
about a missing md5 module.
File "", line 1, in
File "/export/home/drkirkby/sage-4.2/local/lib/python/hashlib.py", line 136,
in
md5 = __get_builtin_constructor('md5')
File "/export/home/drkirkby/sage-
Hi,
I just verified that my home Mac desktop is 10.6.1 (and current for
all Mac updates). I need to kill all of my jobs to update my office
machine, so I deferred this step at work. However this is not the
source of the problem.
Instead it seems that the problem is due to running MacOSX in
64
I believe that its possible, but I wasn't able to get it to work.
There are no examples of Manipulate control layouts in your link, and
I can't find any examples in the Manipulate help. The standard
controls cannot simply be wrapped by Row.
So I guess my point is, while such layouts may be suppo
On Tue, Nov 3, 2009 at 9:44 AM, Alex Ghitza wrote:
>
>
> Hi,
>
> I'll give a 25-minute talk on doing algebra in Sage, at the Victorian
> Algebra Conference in about 36 hours. I decided to just use a
> notebook worksheet this time, which you are invited to check out at
>
> http://standalone.sagen
William Stein wrote:
> On Tue, Nov 3, 2009 at 1:04 AM, Jason Grout
> wrote:
>> I just spent some time thinking about how to specify layouts for
>> interact controls. Here's a possible syntax:
>>
>> @interact(layout=[['a','b'],['c','d']])
>> def _(a=1,b=(2,3),c="hi",d=x+1):
>> print a,b,c,d
On Nov 3, 2009, at 5:28 PM, Dr. David Kirkby wrote:
> If one tries to build Sage on OpenSolaris, python will not build,
> complaining
> about a missing md5 module.
>
>
> File "", line 1, in
> File "/export/home/drkirkby/sage-4.2/local/lib/python/hashlib.py",
> line 136,
> in
> md5 =
Hi folks,
if you reside in the San Francisco Bay Area, you may be interested in
a meeting we'll be having tomorrow November 4 (2-4 pm), as part of our
regular py4science meeting series. Guido van Rossum, the creator of
the Python language, will visit for a session where we will first do a
very r
mhampton wrote:
> Awesome! I've been wishing for this for some time. I like the first
> option you presented the best. I'll check out the patch.
The patch definitely isn't polished yet, but it functionally works.
Thanks,
Jason
>
> -Marshall
>
> On Nov 3, 3:57 am, Jason Grout wrote:
>>
Burcin Erocal wrote:
> Hi Jason,
>
> On Sat, 31 Oct 2009 19:58:56 -0500
> Jason Grout wrote:
>
>> I think it's kind of weird that:
>>
>> sqrt(2)>1
>>
>> does not return True automatically. I realize it's because symbolic
>> expressions do not automatically do comparisons, but maybe we ought
>
Hi,
I'll give a 25-minute talk on doing algebra in Sage, at the Victorian
Algebra Conference in about 36 hours. I decided to just use a
notebook worksheet this time, which you are invited to check out at
http://standalone.sagenb.org/home/pub/0/
or, if that doesn't work, download it from
http
I am trying to make/find collision response code for arbitrary 2D
rigid bodies with rotation and friction (single point collisions).
I posted a question to the message board
https://sourceforge.net/projects/mjbworld/forums/forum/122133/topic/3448212/index/page/1
for the site
http://www.euclidean
Thanks, I'll try to get a look at it. This appears to be what I
needed to find. No promises, as I'm pretty swamped, but now I have
somewhere to start.
Jonathan
On Nov 3, 1:02 am, Jason Grout wrote:
> Jonathan wrote:
> > Jason,
> > I think this is a great idea. As I use Sage a bit in my te
Awesome! I've been wishing for this for some time. I like the first
option you presented the best. I'll check out the patch.
-Marshall
On Nov 3, 3:57 am, Jason Grout wrote:
> Jason Grout wrote:
> > I just spent some time thinking about how to specify layouts for
> > interact controls. Here's
I agree. The situation is far from uniform, and while parts of sage
are quite mature, others need enough work that supporting long-term
compatibility seems counterproductive.
One thing that helps is having python as a model for core
functionality, for example lists. Your stories of Maple
incomp
I've verified that I can build sage-4.2 on my laptop running 10.6,
but
that singular fails (with similar errors reported in the above
logfile) on
two recent Mac desktop machines with the latest XCode.
A pending software update to 10.6.1 (requires a reboot) could explain
the difference, but the sp
Hi,
On Sun, 1 Nov 2009 03:54:05 -0800 (PST)
Vincent Delecroix <20100.delecr...@gmail.com> wrote:
> I agree that sqrt(2) > 1 ;) the problem is the one Jason has
> developed : the comparison returns a symbolic expression !
>
> Morever, It works well for min and max functions :
> {{{
> sage: max(
Hi Jason,
On Sat, 31 Oct 2009 19:58:56 -0500
Jason Grout wrote:
> I think it's kind of weird that:
>
> sqrt(2)>1
>
> does not return True automatically. I realize it's because symbolic
> expressions do not automatically do comparisons, but maybe we ought
> to make an exception for symbolic
On Tue, 3 Nov 2009 11:00:33 +0100
Nathann Cohen wrote:
> He then told me there existed an actively developped library in C++
> for Geometry, which is called CGAL ( Computational Geometry
> Algorithms Library ). He added that it was a very efficient one, and
> that it was a bit difficult to use
One might also want to look at these existing python bindings:
http://cgal-python.gforge.inria.fr
Yann
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubscr..
Hello everybody !!!
I was once more doing advertisement for Sage, when I met someone who is
interested by Sage's Graph library, and would be even more if there were
some tools for Geometry. I went to Sage's reference manual on geometry, to
learn that we were not that developped in this area.
He t
Jason Grout wrote:
> I just spent some time thinking about how to specify layouts for
> interact controls. Here's a possible syntax:
>
> @interact(layout=[['a','b'],['c','d']])
> def _(a=1,b=(2,3),c="hi",d=x+1):
> print a,b,c,d
>
>
> This would lay out a table with a and b in the same ro
On Nov 3, 2009, at 12:55 AM, Ralf Hemmecke wrote:
>> How does WRI "support deprecated code"? And for how long?
>
> One difference between a company like WRI and the Sage project is that
> WRI charges for its product to get money to do (among other things)
> maintenance of old versions or caring
I just spent some time thinking about how to specify layouts for
interact controls. Here's a possible syntax:
@interact(layout=[['a','b'],['c','d']])
def _(a=1,b=(2,3),c="hi",d=x+1):
print a,b,c,d
This would lay out a table with a and b in the same row, then c and d in
the same row.
Mo
Hi
> > IMHO, Sage should be aiming to be more like the professional maths package,
> > not
> > itunes or Firefox.
>
> What are they like? My main experience with deprecation in the Ma's
> is with Maple and Magma.
>
>- Maple -- has an idiotic, confusing and contradictory mix of upper
> How does WRI "support deprecated code"? And for how long?
One difference between a company like WRI and the Sage project is that
WRI charges for its product to get money to do (among other things)
maintenance of old versions or caring about upgrade procedures.
A pragmatic approach for Sage
39 matches
Mail list logo
