Use the raw string preface to avoid backslash hell. print r'' gives
--Matthew Goodman
=
Check Out My Website: http://craneium.net
Find me on LinkedIn: http://tinyurl.com/d6wlch
On Tue, Jan 25, 2011 at 5:46 PM, Ryan Grout wrote:
> On 01/25/2011 06:14 PM, Dox wrote:
On 1/25/11 5:46 PM, Ryan Grout wrote:
On 01/25/2011 06:14 PM, Dox wrote:
Hi everyone,
Today I was writing a SAGE tip for my blog, about using customized
ticks in plots, and I realize that,
sage: p = plot(sin(x), (x, -7, 7), ticks=pi/2, tick_formatter=pi,
axes_labels=['$x$','$\\sin(x)$'], fonts
On Tue, Jan 25, 2011 at 3:33 PM, rjf wrote:
>
>
> On Jan 25, 9:40 pm, Robert Bradshaw
> wrote:
>
> ...
>
>> No variable should be
>> required for callable functions in one variable, nor univariate
>> polynomials.
>>
>> - Robert
>
> Well, a symbolic expression that happens to be a univariate polyn
On 01/25/2011 06:14 PM, Dox wrote:
Hi everyone,
Today I was writing a SAGE tip for my blog, about using customized
ticks in plots, and I realize that,
sage: p = plot(sin(x), (x, -7, 7), ticks=pi/2, tick_formatter=pi,
axes_labels=['$x$','$\\sin(x)$'], fontsize=14, color='red')
sage: p.save('/ho
Hi everyone,
Today I was writing a SAGE tip for my blog, about using customized
ticks in plots, and I realize that,
sage: p = plot(sin(x), (x, -7, 7), ticks=pi/2, tick_formatter=pi,
axes_labels=['$x$','$\\sin(x)$'], fontsize=14, color='red')
sage: p.save('/home/me/fig1.pdf')
sage: q = plot(2*x+
On Jan 25, 9:40 pm, Robert Bradshaw
wrote:
...
> No variable should be
> required for callable functions in one variable, nor univariate
> polynomials.
>
> - Robert
Well, a symbolic expression that happens to be a univariate polynomial
is one thing.
A member of an algebraic category is, I sup
On Jan 25, 4:40 pm, Robert Bradshaw
wrote:
> On Tue, Jan 25, 2011 at 1:23 PM, rjf wrote:
> > diff(x^2+y^2) in Maxima returns 2*x*del(x)+2*y*del(y).
> > in mathematica it returns x^2+y^2
>
> > integrate(x^2+y^2) is an error in both systems.
>
> > I prefer Maxima's response, though the appearan
On Tue, Jan 25, 2011 at 1:23 PM, rjf wrote:
> diff(x^2+y^2) in Maxima returns 2*x*del(x)+2*y*del(y).
> in mathematica it returns x^2+y^2
>
> integrate(x^2+y^2) is an error in both systems.
>
> I prefer Maxima's response, though the appearance of something
> like del(x) means, to me, that there w
On Tue, 25 Jan 2011 11:48:35 -0600
Jason Grout wrote:
> > On Jan 25, 12:27 pm, Jason Grout
> > wrote:
> >>
> >> var('x,y')
> >> a=x+y
> >> b=-y
> >>
> >> then it seems you would have integrate(a+b) behave differently than
> >> integrate(a). That's why it makes less sense to me; to avoid
> >> con
diff(x^2+y^2) in Maxima returns 2*x*del(x)+2*y*del(y).
in mathematica it returns x^2+y^2
integrate(x^2+y^2) is an error in both systems.
I prefer Maxima's response, though the appearance of something
like del(x) means, to me, that there was very probably
some user error.
--
To post to this gr
On Jan 25, 12:59 pm, John Cremona wrote:
> > Let me be more clear. I think that:
>
> > integrate(a) and diff(a) should be deprecated/not supported
> > integrate(b) and diff(b) be deprecated/not supported
> > integrate(a+b) and diff(a+b) be deprecated/not supported
>
> > (each of these should re
> >> var('x,y')
> >> a=x+y
> >> b=-y
>
>
> integrate(a) and diff(a) should be deprecated/not supported
Yes.
> integrate(b) and diff(b) be deprecated/not supported
> integrate(a+b) and diff(a+b) be deprecated/not supported
These cases have to be identical, because of how Pynac simplifies
first, pr
>>
>
> Let me be more clear. I think that:
>
> integrate(a) and diff(a) should be deprecated/not supported
> integrate(b) and diff(b) be deprecated/not supported
> integrate(a+b) and diff(a+b) be deprecated/not supported
>
> (each of these should require a explicit variable specified)
>
I agree.
On 2011-01-25 15:22, Jeroen Demeyer wrote:
> I will check what happens when one simply removes the weave spkg from
> Sage: see http://trac.sagemath.org/sage_trac/ticket/10688
I did that and there is no problem at all: Sage builds, all doctests
pass *without the weave spkg*.
So I guess this means
On 1/25/11 11:38 AM, kcrisman wrote:
On Jan 25, 12:27 pm, Jason Grout wrote:
On 1/25/11 11:17 AM, kcrisman wrote:
If f is a function explicitly of one variable (e.g., f(x)=x^3+1), then
it makes sense to use this variable as a default for differentiation or
integration. However, if we are
On Jan 25, 12:27 pm, Jason Grout wrote:
> On 1/25/11 11:17 AM, kcrisman wrote:
>
>
>
> >> If f is a function explicitly of one variable (e.g., f(x)=x^3+1), then
> >> it makes sense to use this variable as a default for differentiation or
> >> integration. However, if we are dealing with just a
On 1/25/11 11:17 AM, kcrisman wrote:
If f is a function explicitly of one variable (e.g., f(x)=x^3+1), then
it makes sense to use this variable as a default for differentiation or
integration. However, if we are dealing with just a symbolic expression
(e.g., f=x^3+1), then a default makes less
>
> If f is a function explicitly of one variable (e.g., f(x)=x^3+1), then
> it makes sense to use this variable as a default for differentiation or
> integration. However, if we are dealing with just a symbolic expression
> (e.g., f=x^3+1), then a default makes less sense to me.
Correct, that wa
> Or the dig6_string when working with digraphs :)
(Whistling, looking at the sky )
Thaanks :-D
Nathann
--
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...@googlegroups.com
For more options, vis
On Tue, Jan 25, 2011 at 6:06 AM, Nathann Cohen wrote:
>> I just noticed that DiGraph produces graphs that are mutable. Is there
>> any alternative implementation of digraphs (with multiple edges) in
>> Sage that are immutable?
>
> Not to my knowledge Though you're not the first one to ask, and
On 1/25/11 8:44 AM, kcrisman wrote:
Reasoning this might happen is as follows:
sage: f(x)=x^3+1
sage: f.derivative()
x |--> 3*x^2
sage: f.integral()
/Users/.../sage-4.6.2.alpha1/local/bin/sage-ipython:1:
DeprecationWarning: Variable of integration should be specified
explicitly.
#!/usr/bin/e
On Jan 25, 7:41 am, kcrisman wrote:
> Robert, is it possible this is the same as Maxima bug 3036579, which I
> filed a while ago on a related issue? Just checking.
Well, I guess it's possible. I'd say go ahead and make a new report,
though.
best
Robert Dodier
--
To post to this group, send a
Would be good to know!
I updated the corresponding documentation in numerical sage:
http://trac.sagemath.org/sage_trac/ticket/10689
these examples should work now. You could simply test waeve with the
repaired examples ^^
(sorry for possible double posting ^^")
greez,
maldun
On Jan 25, 3:22 pm
The patch buildbot is documented here:
http://wiki.sagemath.org/buildbot
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com
Update: I allowed myself to update the docu:
http://trac.sagemath.org/sage_trac/ticket/10689
would need review.
greez maldun
On Jan 25, 3:16 pm, maldun wrote:
> As mentioned in the other post, it's included in scipy and can be
> imported via
>
> from scipy import weave
>
> so I think this packa
Reasoning this might happen is as follows:
sage: f(x)=x^3+1
sage: f.derivative()
x |--> 3*x^2
sage: f.integral()
/Users/.../sage-4.6.2.alpha1/local/bin/sage-ipython:1:
DeprecationWarning: Variable of integration should be specified
explicitly.
#!/usr/bin/env python
x |--> 1/4*x^4 + x
Argument f
On Jan 25, 12:14 am, Robert Dodier wrote:
> On Jan 24, 10:16 am, Francois Maltey wrote:
>
> > sage: var ('n,k')
> > sage: sum (binomial(n,k)*k^2, k, 0, n) # seems right
> > sage: sum (binomial(n,k)*k^2, k, 1, n) # seems right n(n+1)2^(n-2)
> > sage: sum (binomial(n,k)*k^2, k, 2, n) # is fals
On 2011-01-25 14:46, maldun wrote:
> Question: Isn't a version of weave included in scipy, or would
> deleting the weave in Sage,
> also cripple the weave in Scipy? (I personally don't think so)
I will check what happens when one simply removes the weave spkg from
Sage: see http://trac.sagemath.or
As mentioned in the other post, it's included in scipy and can be
imported via
from scipy import weave
so I think this package is simply outdated.
greez,
maldun
On Jan 22, 3:48 pm, Jeroen Demeyer wrote:
> There is some documentation about using Weave, but it doesn't work.
> Anybody knows about
>
> I just noticed that DiGraph produces graphs that are mutable. Is there
> any alternative implementation of digraphs (with multiple edges) in
> Sage that are immutable?
>
Not to my knowledge Though you're not the first one to ask, and it may
be sound to implement it eventually ^^;
When
Update: In my normal Python I have Scipy but not Weave installed, and
importing worked.
So normally deleting weave shouldn't cause troubles because it's
included in scipy.
Perhaps the import statements have to be changed.
(But we should test it in sage too, just to be sure)
On Jan 25, 2:46 pm, mal
Question: Isn't a version of weave included in scipy, or would
deleting the weave in Sage,
also cripple the weave in Scipy? (I personally don't think so)
I only import weave from scipy via from scipy import weave
so if removing weave doesn't do any harm to the weave in scipy, I have
no problems wi
Also +1 for keeping.
Many people which are more familiar with Matlab expect this behavior
in Sage too.
(I recently introduced Sage to some people)
Of course it's safer to specify the variable, but if I need to I can
do it. I think
this should always be a users choice and never the choice of the
de
Hi!
I just noticed that DiGraph produces graphs that are mutable. Is there
any alternative implementation of digraphs (with multiple edges) in
Sage that are immutable?
Best regards,
Simon
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send
Hi Jeroen!
On 25 Jan., 09:32, Jeroen Demeyer wrote:
> on a ticket, when it depends on other tickets or when only specific
> patches from a big list of patches need to be applied, please make it
> clear in the *ticket description* as opposed to buried somewhere in
> comment 57.
Will the patchbot
, google ate my answer... here it goes again:
General instructions are at:
http://sagemath.org/doc/developer/producing_spkgs.html
You should start by downloading the old version at:
http://sagemath.org/packages/standard/sphinx-1.0.4.p5.spkg
and unpack it. You'll find a file SPKG.txt with r
On Jan 25, 7:41 am, Minh Nguyen wrote:
> Hi,
>
> On Tue, Jan 25, 2011 at 3:05 PM, Mike wrote:
> > I have recently compiled sage-4.6.1 for opensuse 11.3 (see below for
> > details). I would be happy to upload the resulting binary
> > distribution, but have not been able to find either instructi
Hello Sage developers,
A small request from your release manager:
on a ticket, when it depends on other tickets or when only specific
patches from a big list of patches need to be applied, please make it
clear in the *ticket description* as opposed to buried somewhere in
comment 57.
Thanks,
Jeroe
38 matches
Mail list logo
