>
> Do you need mayavi2-3.x only or are there other enthought tools on your
> wish list?
>
> See:
> http://sage.math.washington.edu/home/jsp/SPKGS/Mayavi/
> http://sage.math.washington.edu/home/jsp/SPKGS/ETS/
>
> Jaap
Hi,
I downloaded the .spkg files that you pointed to, and got an error on
the
thanks
uncompatible types and poor error prompt really make me confused
在 Tue, 17 Mar 2009 22:19:07 +0800，Jason Grout
写道:
>
> dagss wrote:
>> On Mar 17, 10:40 am, "Guan Guofeng" wrote:
>>> that's not the key
>>> import numpy
>>> x=numpy.arange(0,1,.05)
>>> y=numpy.sin(x)
>>> still can't work
On Tue, Mar 17, 2009 at 4:46 PM, William Stein wrote:
>
> On Tue, Mar 17, 2009 at 4:41 PM, John H Palmieri
> wrote:
>> So I think it's easy to implement TeX macros into Sage: see > trac.sagemath.org/sage_trac/ticket/>. What macros should we
>> implement? I have \ZZ, \CC, \RR, and \QQ so far
On Tue, Mar 17, 2009 at 4:41 PM, John H Palmieri wrote:
>
> On Mar 17, 12:03 pm, Carl Witty wrote:
>> On Tue, Mar 17, 2009 at 11:55 AM, John H Palmieri
>>
>> wrote:
>> > Well, I've been trying to modify 'latex_preamble' in sage/doc/common/
>> > conf.py, and I'm having no luck at all: no changes
On Mar 17, 12:03 pm, Carl Witty wrote:
> On Tue, Mar 17, 2009 at 11:55 AM, John H Palmieri
>
> wrote:
> > Well, I've been trying to modify 'latex_preamble' in sage/doc/common/
> > conf.py, and I'm having no luck at all: no changes I make have any
> > effect. It seems like a good place to put a f
On Tue, Mar 17, 2009 at 5:14 AM, Simon King wrote:
>
> Dear William,
>
> On Mar 17, 12:03 pm, William Stein wrote:
> ...
>> > Nevertheless, out of curiosity: Why is there this restriction to the
>> > commutative case?
>>
>> There isn't. Seriously -- the file ideal.py has only one use of
>> is_
in case somebody is interested...
-- Forwarded message --
From: Lucio Lastra
Date: Tue, Mar 17, 2009 at 5:53 AM
Subject: Link to download .rar parts for the LiveCD ISO.
To: William Stein
William,
this is one link to download the all the .rar parts that
uncompressed are the S
On Mar 17, 2009, at 3:39 PM, Georg S. Weber wrote:
> I'm sorry to hear this.
>
> What exactly is that "libintl.3.dylib" problem you mention about?
I've lost track of the beginning of this thread, but if I understand
things correctly, the problem is the following:
You have a copy of libintl (
Hi sage-devel,
I'm sorry to hear this.
What exactly is that "libintl.3.dylib" problem you mention about?
I also have an old G4 PPC Mac (also with 10.4.11), that I could test
the PPC binary with. If I get the same failure (... incompatible cpu-
subtype ...), maybe it is an idea to build the 10.4
Alex Ghitza wrote:
>
>
> On Wed, Mar 18, 2009 at 4:07 AM, Nicolas M. Thiery
> mailto:nicolas.thi...@u-psud.fr>> wrote:
>
Sorry Alex, would you mind sending plain text mail and not html?
Cheers,
Jaap
--~--~-~--~~~---~--~~
To post to this group, send email to
On Wed, Mar 18, 2009 at 4:07 AM, Nicolas M. Thiery wrote:
>
> Just a mini-warning so that we don't stomp on each other's foot: I
> made a couple very minor changes in the schemes code for the
> categories (essentially in the parent's constructors/import lists). I
> also moved the corresponding ca
On Mar 17, 2009, at 11:42 AM, Carl Witty wrote:
>
> On Tue, Mar 17, 2009 at 11:28 AM, Justin Walker
> wrote:
>>
>>
>> On Mar 17, 2009, at 10:07 AM, Nicolas M. Thiery wrote:
>>> Just a mini-warning so that we don't stomp on each other's foot: I
>>> made a couple very minor changes in the schem
On Tue, Mar 17, 2009 at 11:55 AM, John H Palmieri
wrote:
> Well, I've been trying to modify 'latex_preamble' in sage/doc/common/
> conf.py, and I'm having no luck at all: no changes I make have any
> effect. It seems like a good place to put a few macros (like \ZZ), but
> maybe that variable isn'
On Mar 17, 11:16 am, Carl Witty wrote:
> On Tue, Mar 17, 2009 at 11:10 AM, John H Palmieri
>
> wrote:
> > I think \ZZ is a good option, too. Does anyone know if the file
> > $SAGE_ROOT/devel/sage/doc/common/macros.tex has any role, currently?
>
> I'm pretty sure it doesn't. (I searched through
On Tue, Mar 17, 2009 at 11:28 AM, Justin Walker wrote:
>
>
> On Mar 17, 2009, at 10:07 AM, Nicolas M. Thiery wrote:
>> Just a mini-warning so that we don't stomp on each other's foot: I
>> made a couple very minor changes in the schemes code for the
>> categories (essentially in the parent's cons
On Mar 17, 2009, at 10:07 AM, Nicolas M. Thiery wrote:
>
> Hi Alex!
>
> Just a mini-warning so that we don't stomp on each other's foot: I
> made a couple very minor changes in the schemes code for the
> categories (essentially in the parent's constructors/import lists). I
> also moved the
On Tue, Mar 17, 2009 at 11:10 AM, John H Palmieri
wrote:
> I think \ZZ is a good option, too. Does anyone know if the file
> $SAGE_ROOT/devel/sage/doc/common/macros.tex has any role, currently?
I'm pretty sure it doesn't. (I searched through the whole sage/doc
tree for the word "macros", and i
On Mar 17, 10:44 am, Robert Bradshaw
wrote:
> On Mar 17, 2009, at 10:39 AM, Martin Albrecht wrote:
>
>
>
>
>
> > On Tuesday 17 March 2009, Carl Witty wrote:
> >> On Tue, Mar 17, 2009 at 9:59 AM, Martin Albrecht
>
> >> wrote:
> >>> On Tuesday 17 March 2009, Carl Witty wrote:
> My vote would
On Mar 17, 2009, at 10:39 AM, Martin Albrecht wrote:
> On Tuesday 17 March 2009, Carl Witty wrote:
>> On Tue, Mar 17, 2009 at 9:59 AM, Martin Albrecht
>>
>> wrote:
>>> On Tuesday 17 March 2009, Carl Witty wrote:
My vote would be for `H_d(X, \ZZ)` (for easier typing), combined
with
>>
On Mar 17, 9:59 am, Martin Albrecht
wrote:
> On Tuesday 17 March 2009, Carl Witty wrote:
>
> > On Tue, Mar 17, 2009 at 9:35 AM, John H Palmieri
> wrote:
> > > Do we have any conventions or standards for the use of LaTeX in
> > > docstrings? Consider this:
>
> > > r"""
> > > This computes
On Tuesday 17 March 2009, Carl Witty wrote:
> On Tue, Mar 17, 2009 at 9:59 AM, Martin Albrecht
>
> wrote:
> > On Tuesday 17 March 2009, Carl Witty wrote:
> >> My vote would be for `H_d(X, \ZZ)` (for easier typing), combined with
> >> some sort of LaTeX-to-plain-text processing to change \ZZ to Z
On Mar 17, 8:34 am, Jaap Spies wrote:
> J Elaych wrote:
> > Hi All,
>
> [...]
> > I'm at least going to need Mayavi2 3.x functionality eventually and I
> > can see that's a work in progress, so perhaps I can help out there.
> > In any case, I'll be lurking here every day so I will be able to in
On Mar 17, 8:12 am, Carl Witty wrote:
> On Mon, Mar 16, 2009 at 9:58 PM, J Elaych wrote:
> > Also, I built sage-3.4 from source on 64bit Ubuntu 8.10 AMD XP2 with
> > 'export MAKE=make -j2' and I have to say that you folks have done an
> > amazing job in that it all just built. Not so lucky w
On Tue, Mar 17, 2009 at 9:59 AM, Martin Albrecht
wrote:
>
> On Tuesday 17 March 2009, Carl Witty wrote:
>> My vote would be for `H_d(X, \ZZ)` (for easier typing), combined with
>> some sort of LaTeX-to-plain-text processing to change \ZZ to Z or ZZ
>> (I'm not sure which). (We have some LaTeX-to
On Tuesday 17 March 2009, Carl Witty wrote:
> On Tue, Mar 17, 2009 at 9:35 AM, John H Palmieri
wrote:
> > Do we have any conventions or standards for the use of LaTeX in
> > docstrings? Consider this:
> >
> > r"""
> > This computes the integral homology `H_d(X, ZZ)` of `X` in
> > dimensio
Hi Alex!
Just a mini-warning so that we don't stomp on each other's foot: I
made a couple very minor changes in the schemes code for the
categories (essentially in the parent's constructors/import lists). I
also moved the corresponding categories in separate files. You may
want to double
On Tue, Mar 17, 2009 at 9:35 AM, John H Palmieri wrote:
>
> Do we have any conventions or standards for the use of LaTeX in
> docstrings? Consider this:
>
> r"""
> This computes the integral homology `H_d(X, ZZ)` of `X` in
> dimension `d`.
> """
>
> versus
>
> r"""
> This computes
Do we have any conventions or standards for the use of LaTeX in
docstrings? Consider this:
r"""
This computes the integral homology `H_d(X, ZZ)` of `X` in
dimension `d`.
"""
versus
r"""
This computes the integral homology `H_d(X, \mathbb{Z})` of `X` in
dimension `d`.
""
J Elaych wrote:
> Hi All,
>
[...]
> I'm at least going to need Mayavi2 3.x functionality eventually and I
> can see that's a work in progress, so perhaps I can help out there.
> In any case, I'll be lurking here every day so I will be able to input
> my first impressions.
>
Do you need mayavi2-
On Mon, Mar 16, 2009 at 9:58 PM, J Elaych wrote:
> Also, I built sage-3.4 from source on 64bit Ubuntu 8.10 AMD XP2 with
> 'export MAKE=make -j2' and I have to say that you folks have done an
> amazing job in that it all just built. Not so lucky with some 'sage -
> i' commands, but the problem w
dagss wrote:
> On Mar 17, 10:40 am, "Guan Guofeng" wrote:
>> that's not the key
>> import numpy
>> x=numpy.arange(0,1,.05)
>> y=numpy.sin(x)
>> still can't work
>
> Ahh right. NumPy is not compatible with the Sage number types. Either
> specify "%python" at the top of the cell, or do
>
> sage:
On Mar 17, 10:40 am, "Guan Guofeng" wrote:
> that's not the key
> import numpy
> x=numpy.arange(0,1,.05)
> y=numpy.sin(x)
> still can't work
Ahh right. NumPy is not compatible with the Sage number types. Either
specify "%python" at the top of the cell, or do
sage: import numpy
sage: Integer = i
Dear William,
On Mar 17, 12:03 pm, William Stein wrote:
...
> > Nevertheless, out of curiosity: Why is there this restriction to the
> > commutative case?
>
> There isn't. Seriously -- the file ideal.py has only one use of
> is_CommutativeRing and that is in the Ideal function.
See below how
This is already #5438, which could use a review in time for 3.4.1 :)
- kcrisman
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more o
Hi folks,
Before conspiracy theories on the subject get fully developed, let me give
an overview of things that transpired at Sage Days 14 and the plan of
dealing with them.
1. in preparation for my talk, I spent a significant amount of quality time
with the schemes/ directory, attempting to cate
Cool discovery! Both
sage: plot(sin(x), xmin=-2*pi, xmax=2*pi, fill=0.5)
and
sage: plot(sin(x), xmin=-2*pi, xmax=2*pi, fill="0.0")
are *exactly* the same plot!
On Tue, Mar 17, 2009 at 5:21 AM, Minh Nguyen wrote:
>
> Hi folks,
>
> With a function say f(x) = sin(x), one can fill the area bet
On Tue, Mar 17, 2009 at 2:37 AM, Simon King wrote:
>
> Dear developers,
>
> I implemented "Symmetric Polynomial Rings" -- these are polynomial
> rings with countably many variables plus a permutation action on the
> variables. Now I'd like to implement the algorithms of Aschenbrenner
> and Hillar
> Nevertheless, out of curiosity: Why is there this restriction to the
> commutative case?
>
> I mean, there are non-commutative Gröbner bases -- wouldn't it be
> better to deal with commutativity only in the classes that inherit
> from Ideal_generic, rather than in Ideal_generic itself? Being in
Just for the record, the things David mentioned were done by someone
else before I came on board!
John
2009/3/17 David Kohel :
>
> Hi,
>
> We can move this over the sage-nt, but let me reply here.
>
> One improvement should be to, in fact, follow what John [Cremona)]
> did for elliptic curves --
that's not the key
import numpy
x=numpy.arange(0,1,.05)
y=numpy.sin(x)
still can't work
在 Tue, 17 Mar 2009 17:23:53 +0800，dagss
写道:
>
> On Mar 17, 10:09 am, peak wrote:
>> When I run below code in SageNB, it rised error:
>>
>> import numpy
>> x=numpy.arange(0,1,.05)
>> y=numpy.sin(2*pi*x)
>>
Dear developers,
I implemented "Symmetric Polynomial Rings" -- these are polynomial
rings with countably many variables plus a permutation action on the
variables. Now I'd like to implement the algorithms of Aschenbrenner
and Hillar for computing Gröbner bases of Symmetric Ideals (i.e.,
ideals th
On Mar 17, 10:09 am, peak wrote:
> When I run below code in SageNB, it rised error:
>
> import numpy
> x=numpy.arange(0,1,.05)
> y=numpy.sin(2*pi*x)
>
> Traceback (click to the left for traceback)
> ...
> AttributeError: sin
>
> but the same code works well in python, how can I obtain array x & y
Hi folks,
With a function say f(x) = sin(x), one can fill the area between f and
a horizontal line y=c using the "fill" option of function plot(). To
get the desired effect, do I do this
fill=c # a numeric value, as suggested by
http://www.sagemath.org/doc/reference/sage/plot/plot.html#sage.plo
When I run below code in SageNB, it rised error:
import numpy
x=numpy.arange(0,1,.05)
y=numpy.sin(2*pi*x)
Traceback (click to the left for traceback)
...
AttributeError: sin
but the same code works well in python, how can I obtain array x & y
above except using [... for ... in range()] ?
than
Hi,
We can move this over the sage-nt, but let me reply here.
One improvement should be to, in fact, follow what John [Cremona)]
did for elliptic curves -- replace points-as-morphisms with points as
simple coordinates. In analogy with matrices and homomorphisms,
for reasons of efficiency (and
On Mar 17, 1:47 am, William Stein wrote:
> I think simply appending a text file of changes to this list would be
> fine for starters.
>
> William
OK. Here is my list so far:
Suggested Amendments to Sage Tutorial (Sage 3.4)
1. Functions, Indentation, and Counting
After
sage: def is_even(
I found another problem related to the documentation search: In the Sage
Reference Manual 3.4, sometimes there is a Quick search field at the top
left, sometimes there isn't. But even if there is, typing a search item
and clicking on the "Go" button only takes me to a page entitled
"Search" wh
Hi All,
At the end of the Sage 3.4 tutorial I was invited to send the list the
time I spent, so here it is:
sage: quit
Exiting SAGE (CPU time 0m52.07s, Wall time 43m1.91s).
Exiting spawned Maple process.
Exiting spawned Maxima process.
I drank the Kool-Aid (Flavor-Aid?) at the recent Sage Days
[ Some of you may have already seen this on the numpy/scipy/mpl lists.
I know it's a bit redundant because obviously if you use sage at the
command line, you use IPython, which is why I didn't originally post
here. But after suggestions from members of this list I changed my
mind. If you feel t
49 matches
Mail list logo
