Dear Carl,
thank you for your explanations.
> The 'int' (and its bignum counterpart, 'long') are native Python
> types. As far as I know, we don't modify Python at all; removing
> 'int' would be major surgery, and we're not going to do it.
>
> 'Integer' is a Sage type. This means it ha
On Jan 22, 11:34 pm, Simon King <[EMAIL PROTECTED]> wrote:
> Dear Sage team,
>
> in reply to myself, in the hope to clearify things:
>
> > After installing gnutls, building was successful. However, I was
> > unable to run the notebook in the alpha-versions.
>
> I mean: saying "./sage -notebook",
Dear Sage team,
in reply to myself, in the hope to clearify things:
> After installing gnutls, building was successful. However, I was
> unable to run the notebook in the alpha-versions.
I mean: saying "./sage -notebook", i got a lot of error messages and
eventually an "Unhandled SIGSEGV".
See
On Jan 22, 2008 8:50 AM, kcrisman <[EMAIL PROTECTED]> wrote:
>
> Ideas:
>
> 1) Easy: Make a VMWare link on the download page (as in the past) in
> addition to the MS Windows link where it currently resides; we are
> trying to get Sage up and running on the local network using VMWare on
> Linux but
thanks -- I'll never use anything else from now on! (well ok, I'll
use rnage() for loop indices).
John
On 22/01/2008, William Stein <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> By the way, I very often use the [a..b] notation, which returns
> Sage integers, and is very fast and has the (a..b) generat
Hi,
By the way, I very often use the [a..b] notation, which returns
Sage integers, and is very fast and has the (a..b) generator
notation as well (and is very familiar to Magma users like me):
sage: [q for q in [1..100] if q.is_square()]
[1, 4, 9, 16, 25, 36, 49, 64, 81, 100]
sage: [q for q in (
John Cremona wrote:
> Thanks for the detailed explanation -- answering all points except
> "Why the s in srange?"!
>
srange = "sage range"?
Jason
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this
Thanks for the detailed explanation -- answering all points except
"Why the s in srange?"!
John
On 22/01/2008, Carl Witty <[EMAIL PROTECTED]> wrote:
>
> On Jan 22, 1:31 am, Paul Zimmermann <[EMAIL PROTECTED]> wrote:
> > I also "enjoyed" several times converting from 'int' to 'Integer' and back.
On Jan 22, 1:31 am, Paul Zimmermann <[EMAIL PROTECTED]> wrote:
> I also "enjoyed" several times converting from 'int' to 'Integer' and back.
> For beginners, this is a real difficulty, and in my opinion range? or xrange?
> should give a big warning that the "list of integers" output contains Pytho
Dear Sage team,
I downloaded the alpha-versions of sage-2.10.1. When trying to build,
i first had an error mentioning gnutls (this did not occur while
building sage-2.8.6 and upgrading to sage-2.10).
After installing gnutls, building was successful. However, I was
unable to run the notebook in t
Ideas:
1) Easy: Make a VMWare link on the download page (as in the past) in
addition to the MS Windows link where it currently resides; we are
trying to get Sage up and running on the local network using VMWare on
Linux but unfortunately the admin didn't know the binary was lurking
under Windows!
William said:
> Actually, the behavior of Sage for show(v), where v is a list of graphics
> objects, is pretty stupid. This is pretty dumb:
>
> sage: show([plot(sin,(0,1)), circle((0,0),1)])
> \begin{array}{l}[\text{Graphics object
> consisting of 1 graphics primitive},\\
> \text{Graphics object
John,
> sage: [q for q in range(100) if q.is_square()]
>
> --rather, one has to do this
>
> sage: [q for q in range(100) if Integer(q).is_square()]
> [0, 1, 4, 9, 16, 25, 36, 49, 64, 81]
>
> or even this:
> sage: [Integer(q) for q in range(100) if Integer(q).is_square()]
> [0, 1, 4, 9,
I knew that Sage converted literal integers to sage Integers on
preparsing input, but had not realized until recently that the
following would not work:
sage: [q for q in range(100) if q.is_square()]
---
Traceback (mo
14 matches
Mail list logo
