On Wed, Aug 19, 2009 at 11:11 PM, Minh Nguyen wrote:
>
> Hi William,
>
> On Thu, Aug 20, 2009 at 4:03 PM, William Stein wrote:
>>
>> On Wed, Aug 19, 2009 at 10:28 PM, Minh Nguyen wrote:
>
>
>
>>> I feel that as release manager for Sage 4.1.1, I should devote some
>>> time to fix the issues caused
Hi William,
On Thu, Aug 20, 2009 at 4:03 PM, William Stein wrote:
>
> On Wed, Aug 19, 2009 at 10:28 PM, Minh Nguyen wrote:
>> I feel that as release manager for Sage 4.1.1, I should devote some
>> time to fix the issues caused by including cliquer. Following our
>> exchange on IRC last week co
On Wed, Aug 19, 2009 at 10:28 PM, Minh Nguyen wrote:
>
> Hi William,
>
> On Thu, Aug 20, 2009 at 3:20 PM, William Stein wrote:
>>
>> Hi Nathann (cc: sage-devel),
>>
>> I've noticed that including cliquer in Sage is unpleasant for some
>> people, e.g., me.
>>
>> http://trac.sagemath.org/sage_trac/t
Hi William,
On Thu, Aug 20, 2009 at 3:20 PM, William Stein wrote:
>
> Hi Nathann (cc: sage-devel),
>
> I've noticed that including cliquer in Sage is unpleasant for some
> people, e.g., me.
>
> http://trac.sagemath.org/sage_trac/ticket/6746
>
> and
>
> http://trac.sagemath.org/sage_trac/ticket/66
Hi Nathann (cc: sage-devel),
I've noticed that including cliquer in Sage is unpleasant for some
people, e.g., me.
http://trac.sagemath.org/sage_trac/ticket/6746
and
http://trac.sagemath.org/sage_trac/ticket/6681
For example, I just upgraded Sage on my 64-bit OS X laptop, and I'm
not happened
Robert Bradshaw wrote:
>
> Not surprising. Also, I forgot about the GIL, which truely limits the
> performance benifits of threading in Python. If anything ever kills
> Python, I bet it'll be the GIL (but I'm hopeful that it'll get removed
> before it causes an untimely death...)
>
Has anyone
Robert Miller wrote:
> Hello all,
>
> For those of you not in Seattle today / not at Chris's talk at the
> Sage seminar, here is a copy of his slides.
>
Thanks! (and thanks, Chris, if you are listening too).
Some comments/questions:
1. What did Chris use to draw the graphs on page 48? The
2009/8/19 Golam Mortuza Hossain :
>
> Hi,
>
>
> On Wed, Aug 19, 2009 at 2:30 PM, William Stein wrote:
>>
>> On Tue, Aug 18, 2009 at 11:00 PM, Ondrej Certik wrote:
>
>>>
>>> well, I would interpret it differently:
>>>
>>> int f(x) d(x^2) = int f(x) 2 x dx
>>> = 2 integrate(x*f(
2009/8/19 Robert Bradshaw :
> On Wed, 19 Aug 2009, William Stein wrote:
>
>>
>> 2009/8/19 Robert Bradshaw :
>>>
>>> On Wed, 19 Aug 2009, William Stein wrote:
>>>
On Wed, Aug 19, 2009 at 1:19 AM, Robert
Bradshaw wrote:
> Multithreading will have to be introduced at one
> leve
On Wed, Aug 19, 2009 at 3:17 AM, Robert Dodier wrote:
>
> William Stein wrote:
>
>> Unless you can give a explanation of what you want integrating wrt x^2
>> to mean, I think we should also raise an error in Sage.
>
> That would be unfortunate. Faced with some unrecognized construct,
> the mathema
Thanks Minh!
On Wed, Aug 19, 2009 at 7:58 PM, Minh Nguyen wrote:
>
> Hi David,
>
> On Thu, Aug 20, 2009 at 9:55 AM, David Joyner wrote:
>>
>> Can these be posted to the wiki somewhere?
>
> See this talks wiki page
>
> http://wiki.sagemath.org/Talks
>
> --
> Regards
> Minh Van Nguyen
>
> >
>
--~
Hi David,
On Thu, Aug 20, 2009 at 9:55 AM, David Joyner wrote:
>
> Can these be posted to the wiki somewhere?
See this talks wiki page
http://wiki.sagemath.org/Talks
--
Regards
Minh Van Nguyen
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-
2009/8/19 Minh Nguyen :
>
> Hi folks,
>
> Today, I borrowed a copy of L.C. Washington's book "Elliptic Curves:
> Number Theory and Cryptography", 2nd edition. And it's good to know
> that Sage appears in its own section within an appendix of that book.
> The section is about using Sage's support f
Hi Robert,
On Thu, Aug 20, 2009 at 8:04 AM, Robert Miller wrote:
> Hello all,
>
> For those of you not in Seattle today / not at Chris's talk at the
> Sage seminar, here is a copy of his slides.
The talk slides are up at the talks wiki page
http://wiki.sagemath.org/Talks
> -- Forwarde
Can these be posted to the wiki somewhere?
On Wed, Aug 19, 2009 at 6:04 PM, Robert Miller wrote:
> Hello all,
>
> For those of you not in Seattle today / not at Chris's talk at the
> Sage seminar, here is a copy of his slides.
>
>
> -- Forwarded message --
> From: Chris Godsil
>
On Wed, 19 Aug 2009, William Stein wrote:
>
> 2009/8/19 Robert Bradshaw :
>>
>> On Wed, 19 Aug 2009, William Stein wrote:
>>
>>>
>>> On Wed, Aug 19, 2009 at 1:19 AM, Robert
>>> Bradshaw wrote:
Multithreading will have to be introduced at one
level or another to scale the notebook to more
2009/8/19 Robert Bradshaw :
>
> On Wed, 19 Aug 2009, William Stein wrote:
>
>>
>> On Wed, Aug 19, 2009 at 1:19 AM, Robert
>> Bradshaw wrote:
>>> Multithreading will have to be introduced at one
>>> level or another to scale the notebook to more than a single
>>> processor anyways.
>>>
>>> - Robert
On Wed, 19 Aug 2009, William Stein wrote:
>
> On Wed, Aug 19, 2009 at 1:19 AM, Robert
> Bradshaw wrote:
>> Multithreading will have to be introduced at one
>> level or another to scale the notebook to more than a single
>> processor anyways.
>>
>> - Robert
>
> Huh? Why? I don't see any need fo
On Wed, Aug 19, 2009 at 1:19 AM, Robert
Bradshaw wrote:
> Multithreading will have to be introduced at one
> level or another to scale the notebook to more than a single
> processor anyways.
>
> - Robert
Huh? Why? I don't see any need for multithreading to solve the
above problem, or rather I
Dear category fans,
David Kohel won't be available in the next two weeks for working on
the category review. Is there any volunteer for reviewing (some of
the) 40 categories listed under his name on:
http://sagetrac.org/sage_trac/wiki/CategoriesCategoriesReview
The files are all
On Aug 19, 8:56 pm, Nick Alexander wrote:
> This is merely dynamic versus lexical scope. When you need dynamic
> scope, it's not easy to fake it. Of course, most of the time, you
> don't need it and in fact don't want it :)
Yes, my proposal was to introduce a new method that takes all de
On Wed, 19 Aug 2009, Simon King wrote:
>
> Hi Robert,
>
> On 19 Aug., 22:43, Robert Bradshaw
> wrote:
>> Is u.subs(globals()) good enough?
>
> You mean like this:
> sage: u=1+x
> sage: x=1
> sage: u.subs(globals())
> Traceback (most recent call last):
> ...
> TypeError: no canonical coercion fro
Hi Robert,
On 19 Aug., 22:43, Robert Bradshaw
wrote:
> Is u.subs(globals()) good enough?
You mean like this:
sage: u=1+x
sage: x=1
sage: u.subs(globals())
Traceback (most recent call last):
...
TypeError: no canonical coercion from to Symbolic Ring
sage: globals()['x']
1
This is certainly not
Is u.subs(globals()) good enough?
On Wed, 19 Aug 2009, Harald Schilly wrote:
>
> forwarding Patrick Lacasse:
>
> As being the user we are talking about,
> I want to remember my original wish,
> that u.n() evaluates to 2, not u evaluates to 2.
> I also want u to keep its symbolic meaning of 'k+1'
forwarding Patrick Lacasse:
As being the user we are talking about,
I want to remember my original wish,
that u.n() evaluates to 2, not u evaluates to 2.
I also want u to keep its symbolic meaning of 'k+1'
so I can change k and u will change together.
Harold proposes a new method ".evaluate()".
Hi,
On Wed, Aug 19, 2009 at 2:30 PM, William Stein wrote:
>
> On Tue, Aug 18, 2009 at 11:00 PM, Ondrej Certik wrote:
>>
>> well, I would interpret it differently:
>>
>> int f(x) d(x^2) = int f(x) 2 x dx
>> = 2 integrate(x*f(x),x)
>
> That's exactly what I meant. I was just
> The computer scientist in me just can't believe Maple and
> Mathematica are designed that way. It's just sad.
This is merely dynamic versus lexical scope. When you need dynamic
scope, it's not easy to fake it. Of course, most of the time, you
don't need it and in fact don't want it :)
On Aug 19, 2009, at 1:59 PM, William Stein wrote:
>
>
> MATHEMATICA:
> In[1]:= u := 1 + k; u
> Out[1]= 1 + k
> In[2]:= k := 1;
> In[3]:= u
> Out[3]= 2
>
> MAPLE:
>> u := 1+k;
> u := 1 + k
>> u;
> 1 + k
>> k := 1;
>
On Wed, Aug 19, 2009 at 6:30 AM, Harald Schilly wrote:
>
> here is another "report a problem" message from the notebook
> interface. It's not a bug (i think) but it gives insight in how Sage
> is used and over what users stumble when using it for simple things.
>
> --
> This doesn'
On Aug 19, 2009, at 1:30 PM, William Stein wrote:
>
> That's exactly what I meant. I was just being very sloppy because I
> was in a hurry. The point is that "int f(x) d(x^2) = int f(x) 2 x
> dx" seems very reasonable.We could easily make Sage use this
> interpretation even though Maxima
On Tue, Aug 18, 2009 at 11:00 PM, Ondrej Certik wrote:
>
> On Tue, Aug 18, 2009 at 5:27 PM, William Stein wrote:
>>
>> On Tue, Aug 18, 2009 at 3:51 AM, Golam Mortuza
>> Hossain wrote:
>>>
>>> Hi,
>>>
>>> While testing new integral SFunction class for Sage,
>>> I encountered this weird bug.
>>>
>>>
Hi!
On Aug 19, 3:53 pm, rjf wrote:
> Consider
> integrate(f(x,y),x*y).
>
> do you compute d(x*y) as x*dy+y*dx and compute integrate(f(x)
> *x,y) + integrate(f(x)*y,x)?
>
> Here's another interpretation of variable = x^2...
>
> integrate(f(x),x^2) = integrate(integrate(f(x),x),x).
> that
Nathann Cohen wrote:
> Hello everybody !!!
>
> I have been working with graphs in Sage for some time now, and I have
> a few remarks about how labels are defined in Graphs ( I may be wrong
> as I do not think I know ALL about graphs in Sage, so please tell me
> when I'm wrong ) :
>
> - Vertices
Consider
integrate(f(x,y),x*y).
do you compute d(x*y) as x*dy+y*dx and computeintegrate(f(x)
*x,y) + integrate(f(x)*y,x)?
Here's another interpretation of variable = x^2...
integrate(f(x),x^2) = integrate(integrate(f(x),x),x).
that is, an iterated integral. This is like
(d ^2 f(x))
Hello everybody !!!
I have been working with graphs in Sage for some time now, and I have
a few remarks about how labels are defined in Graphs ( I may be wrong
as I do not think I know ALL about graphs in Sage, so please tell me
when I'm wrong ) :
- Vertices do not have any kind label. They just
here is another "report a problem" message from the notebook
interface. It's not a bug (i think) but it gives insight in how Sage
is used and over what users stumble when using it for simple things.
--
This doesn't work:
var('k')
u = 1 + k
k = 1
u.n()
--
It is may
Hello Dave, hello Martin,
unfortunately, I didn't find the time to have a look at that the issue,
but
> The Sage install makefile defines CXX to be g++ so no code should ignore that.
In order to obey this, the following lines should be added to
patch/custom.py:
---
try:
CC = os.environ['CC'
Hi,
On Tue, Aug 18, 2009 at 8:02 PM, Jason Grout wrote:
>
> Fredrik Johansson wrote:
>>> Given we are moving to a new settings, I am proposing that we make
>>> integration syntax bit stricter and consistent now. In particular, we allow
>>> only
>>> following inputs as valid
>>>
>>> (1) integrate
On Wed, Aug 19, 2009 at 3:17 AM, Robert Dodier wrote:
>
> William Stein wrote:
>
>> Unless you can give a explanation of what you want integrating wrt x^2
>> to mean, I think we should also raise an error in Sage.
>
> That would be unfortunate. Faced with some unrecognized construct,
> the mathema
On 19 Aug., 08:34, Ondrej Certik wrote:
...
> Is there any other interpretation besides:
>
> int f(x) d g(x) = int f(x) * dg/dx dx
>
> ? Example used in physics:
>
> int P(cos(x)) sin(x) dx = int P(cos(x)) dcos(x)
>
> where P is a Legendre polynomial.
Indeed this seems like a natural inte
In Larry's second edition there is also a reference to a result I
proved while implementing the abelian_group() function for elliptic
curves over finite fields in Sage, which will appear in Journal de
Théorie des nombres de Bordeaux (joint with Drew Sutherland, see
http://arxiv.org/abs/0901.0120v1
Hi folks,
Today, I borrowed a copy of L.C. Washington's book "Elliptic Curves:
Number Theory and Cryptography", 2nd edition. And it's good to know
that Sage appears in its own section within an appendix of that book.
The section is about using Sage's support for elliptic curves to show
how one ca
On Jul 22, 2009, at 11:12 AM, ghtdak wrote:
> On Jul 21, 6:40 pm, "Dr. David Kirkby"
> wrote:
>> ghtdak wrote:
>>
>>> This thread has gotten long and there are many subjects embedded
>>> within.
>>
>>> One of the problems I've had with the notebook implementation is
>>> that
>>> the sage proce
On Aug 19, 2009, at 12:18 AM, Pat LeSmithe wrote:
>
> On Jul 22, 9:23 pm, William Stein wrote:
>> On Wed, Jul 22, 2009 at 2:19 PM, ghtdak wrote:
>>> My primary problem is that the Sage subprocess is blocking
>>> forever on
>>> the other side of the pipe when its not computing... Therefore, I
>
I've been working on shifting our axes and gridline plotting work to use
matplotlib native constructs. The result is way, way simpler code with
much, much nicer pictures. This also clears up a lot of bugs and
annoyances that have been expressed for a long time. I'd like some
comment on the
Pat LeSmithe wrote:
> On Jul 22, 9:23 pm, William Stein wrote:
>> On Wed, Jul 22, 2009 at 2:19 PM, ghtdak wrote:
>>> My primary problem is that the Sage subprocess is blocking forever on
>>> the other side of the pipe when its not computing... Therefore, I
>>> can't have a Sage sub-process that I
On Jul 22, 9:23 pm, William Stein wrote:
> On Wed, Jul 22, 2009 at 2:19 PM, ghtdak wrote:
> > My primary problem is that the Sage subprocess is blocking forever on
> > the other side of the pipe when its not computing... Therefore, I
> > can't have a Sage sub-process that I'm using in the noteboo
47 matches
Mail list logo
