Hi Fernando,
A user reported this bug: http://trac.sagemath.org/sage_trac/ticket/6650
They think
1;
shouldn't print anything since it doesn't on the command line.
In IPython indeed it doesn't print anything. But in *Python* it does
print something:
bash$ ipython
Python 2.6.2 (r262:71600, J
Hi,
DSage is now gone from Sage. See
http://trac.sagemath.org/sage_trac/ticket/7975
-- William
On Mon, Jan 18, 2010 at 11:16 PM, Craig Citro wrote:
>> [X] Yes, I don't use DSage (don't even know what it is...), and
>> think it should be removed from Sage.
>>
>
> I'm in this group, but
Hi Nils,
On Mon, 18 Jan 2010 22:47:48 -0800 (PST)
Nils Bruin wrote:
> In sage's symbolic module, forget() is supposed to forget all
> assumptions. It mainly does this by passing "forget(facts())" to the
> calculus instance of the maxima-interface. However, forget(facts());
> is often not valid i
> [X] Yes, I don't use DSage (don't even know what it is...), and
> think it should be removed from Sage.
>
I'm in this group, but I do know one (possibly the only?) DSage user
-- John Voight. Does anyone know if he still uses it?
-cc
--
To post to this group, send an email to sage-devel@goog
Hello,
[ ] Yes, I don't use DSage (don't even know what it is...), and
think it should be removed from Sage.
I've never used it, and it's been broken for a long time.
On Mon, Jan 18, 2010 at 8:47 PM, William Stein wrote:
> Hello,
>
> I officially propose removing DSage from the Sage distrib
In sage's symbolic module, forget() is supposed to forget all
assumptions. It mainly does this by passing "forget(facts())" to the
calculus instance of the maxima-interface. However, forget(facts());
is often not valid in maxima: facts also reports facts that have been
introduced by "declare();", a
So the error seems to be coming from this command:
> building 'sage.schemes.elliptic_curves.descent_two_isogeny' extension
> /usr/local/gcc-4.4.1-sun-linker/bin/gcc -fno-strict-aliasing -DNDEBUG -g -O3
> -Wall -Wstrict-prototypes -fPIC
> -I/export/home/drkirkby/sage-4.3.1.rc0/local/include/FLINT/
[X] Yes, for removal. I tried with little success to use dsage some
years ago, but quickly switched to the "processing" module.
Nathan
--
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
Sorry about this. I meant to send this to the cython-users list.
On Jan 18, 7:26 pm, Michael Yurko wrote:
> I've figured out what Dag meant in his original post. I've attached a quick
> example in case anyone else is having the same issue.
>
> --
> Mike Yurko
>
> cnp_tester.py
> < 1KViewDownload
There seems to be another problem which is stopping the Sage library building on
Solaris 10. At first glance it would appear to be totally unrelated to Roberts
complex maths code, though I'm not 100% sure. I've installed his patch.
I've created a ticket for this.
http://trac.sagemath.org/sage_
On Mon, Jan 18, 2010 at 4:59 PM, John H Palmieri wrote:
> Ticket #7532 deals with this issue: in ring.pyx, code says "return
> NotImplementedError" where it should say "raise NotImplementedError".
> But if I make this change:
>
> diff -r c86168806012 -r 919f3924ef5c sage/rings/
> ring.pyx
> --- a/
On Mon, Jan 18, 2010 at 4:15 PM, Dr. David Kirkby
wrote:
> William Stein wrote
>>>
>>> How does this sound then.
>>>
>>> Set SAGE_COMMON_FLAGS
>>>
>>> to be a reasonable set of CFLAGS for most packages, so most .spkg's can
>>> simply use
>>>
>>> CFLAGS=$SAGE_COMMON_FLAGS
>>>
>>> which will have -g
Ticket #7532 deals with this issue: in ring.pyx, code says "return
NotImplementedError" where it should say "raise NotImplementedError".
But if I make this change:
diff -r c86168806012 -r 919f3924ef5c sage/rings/
ring.pyx
--- a/sage/rings/ring.pyx Mon Jan 18 12:40:07 2010 -0800
+++ b/sage/ri
I've figured out what Dag meant in his original post. I've attached a quick
example in case anyone else is having the same issue.
--
Mike Yurko
--
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...@googlegr
William Stein wrote
How does this sound then.
Set SAGE_COMMON_FLAGS
to be a reasonable set of CFLAGS for most packages, so most .spkg's can
simply use
CFLAGS=$SAGE_COMMON_FLAGS
which will have -g, -Wall, and if necessary -m64, when using gcc. For other
compilers, the options will be different
Thank you for pointing out the ticket. I have been thinking about
which classes of warning could be useful in a general warnings
framework. Please have a look at the reworked file and the brief
comment on it. Could you tell me what you think about it?
There should be some follow up tickets which re
Dear Sage/Sage-combinat devs,
On Mon, Jan 18, 2010 at 10:40:18AM +0100, Nicolas M. Thiery wrote:
> * #7980: Extract basic support for the "concrete representation of an
>abstract algebra" relation out of the ncsf patch (Jason?)
This is a concept that we have used much in MuPAD-Combina
On Mon, Jan 18, 2010 at 12:22 PM, Dr. David Kirkby
wrote:
> William Stein wrote:
>>
>> On Sun, Jan 17, 2010 at 11:20 PM, Dr. David Kirkby
>> wrote:
>>>
>>> Last week was a pretty annoying week for Solaris support. Two quite major
>>> obstacles came up.
>>>
>>> 1) #7932: _Complex_I undeclared - a
On Jan 18, 2010, at 12:22 PM, Dr. David Kirkby wrote:
William Stein wrote:
On Sun, Jan 17, 2010 at 11:20 PM, Dr. David Kirkby
wrote:
Last week was a pretty annoying week for Solaris support. Two
quite major
obstacles came up.
1) #7932: _Complex_I undeclared - a new bug totally stops a
So
On Jan 18, 2010, at 4:47 AM, William Stein wrote:
Hello,
I officially propose removing DSage from the Sage distribution.
Why?
1. Nobody has worked on the code for years.
2. The guy who originally worked on the code is gone, and can't
work on the code even if he wanted to (due to conditio
Hello everyone,
I worked during months with my computer lab director trying to make
dsage work... We managed once to make it work properly.
In dsage:
-Documentation is anemic;
-Many not implemented functions;
-Bizarre behaviours
-...
My vote is:
[x] - Remove dSage from Sage "and use something e
William Stein wrote:
On Sun, Jan 17, 2010 at 11:20 PM, Dr. David Kirkby
wrote:
Last week was a pretty annoying week for Solaris support. Two quite major
obstacles came up.
1) #7932: _Complex_I undeclared - a new bug totally stops a Solaris 10
build.
has introduced code which exploits a bug in
Minh Nguyen wrote:
Hi David,
On Tue, Jan 19, 2010 at 2:35 AM, Dr. David Kirkby
wrote:
The issue William mentioned got me thinking that it would be useful to add a
web page something like:
"Ideas for student projects"
This might be related to William's Sage "Grand Tour" [1] from June
2009. T
William Stein wrote:
[X] Yes, I don't use DSage (don't even know what it is...), and
think it should be removed from Sage.
Well, I do know vaguely what it is, but I don't think it should get back
into standard without the usual review process---definitely not for free.
Moving it to experimen
-- Forwarded message --
From: John Cremona
Date: 2010/1/18
Subject: Re: [sage-devel] Re: [sage-combinat-devel]
sage/combinat/iet/template.py
To: sage-devel@googlegroups.com
Cc: sage-combinat-de...@googlegroups.com
The other common error is misuse of the :: (double colon) which yo
You didn't offer:
[x] Yes, I've used DSage extensively in the past, and I wholeheartedly
agree with removing it from Sage.
The only use I have for dsage anymore is "Hey! The dsage spkg is
compiling! Sage must be almost finished building!"
--
Robert L. Miller
http://www.rlmiller.org/
--
To post
Hi David,
On Tue, Jan 19, 2010 at 2:35 AM, Dr. David Kirkby
wrote:
> The issue William mentioned got me thinking that it would be useful to add a
> web page something like:
>
> "Ideas for student projects"
This might be related to William's Sage "Grand Tour" [1] from June
2009. That tour lists m
The issue William mentioned got me thinking that it would be useful to add a web
page something like:
"Ideas for student projects"
where things could be listed which would be useful, but where nobody is working
on. A bit like this one
http://www.itu.dk/~kfl/student-projects.html
but state t
William Stein wrote:
Hello,
I officially propose removing DSage from the Sage distribution.
Why?
1. Nobody has worked on the code for years.
2. The guy who originally worked on the code is gone, and can't
work on the code even if he wanted to (due to conditions of his job).
3. So fa
The other common error is misuse of the :: (double colon) which you
should only put immediately before a block of doctests (starting with
sage: prompts). So if your EAMPLES block goes right into an example,
use EXAMPLES:: but if the first example has some other explanatory
text first, keep a singl
William Stein wrote:
Hello,
I officially propose removing DSage from the Sage distribution.
Why?
1. Nobody has worked on the code for years.
2. The guy who originally worked on the code is gone, and can't
work on the code even if he wanted to (due to conditions of his job).
3. So fa
orphaning. I remember thinking it looked great, at a time when I
didn't have a machine on which I could use it.
John
2010/1/18 Nathann Cohen :
> Same question.. What is it ? ;-)
>
> Nathann
>
> --
> To post to this group, send an email to sage-devel@googlegroups.com
> To unsubscribe from this gr
On Mon, Jan 18, 2010 at 10:40:18AM +0100, Nicolas M. Thiery wrote:
> I also added a list of core features I really would like to see in
> Sage, or at least in Sage-Combinat, before Sage Days 20 (Feb. 22nd),
> since they will be building blocks for the work planned there.
> Here is a copy:
>
> *
Hi Vincent,
On Mon, Jan 18, 2010 at 8:41 PM, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
> Is there anywhere strict specification/possibilities for the docstring
> of functions ? My only source was the devel guide but it does not
> mention the ".. math:" ReST tag
Ticket #7977 [1] cont
Jaap Spies wrote:
Hi,
A patched version of numpy-1.3.0 seems to build and install On Open
Solaris 06/09
real 0m46.014s
user 0m41.791s
sys 0m2.656s
Successfully installed numpy-1.3.0.p3
[...]
from numpy.linalg import lapack_lite
ImportError: ld.so.1: python: fatal: relocation error: file
/ex
Same question.. What is it ? ;-)
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, visit this group at http://groups.google.com/group/sage-devel
URL: http://www
On Mon, Jan 18, 2010 at 5:32 AM, Simon King wrote:
> On Jan 18, 12:47 pm, William Stein wrote:
>> If you care, please vote.
>
> I don't know if I care, but if I did, my answer would be
>
> [X] Yes, I don't use DSage (don't even know what it is...), and
> think it should be removed from Sage.
On Jan 18, 12:47 pm, William Stein wrote:
> If you care, please vote.
I don't know if I care, but if I did, my answer would be
[X] Yes, I don't use DSage (don't even know what it is...), and
think it should be removed from Sage.
And what is it?
Cheers
Simon
--
To post to this group, send
> If you care, please vote.
>
> [ ] Yes, I don't use DSage (don't even know what it is...), and
> think it should be removed from Sage.
>
> [ ] No, I think DSage should stay as is. I love using DSage!
>
> [ ] Sort of -- delete Dsage for now, but if a maintainer/developer
> comes along
On Mon, Jan 18, 2010 at 7:47 AM, William Stein wrote:
> Hello,
>
> I officially propose removing DSage from the Sage distribution.
>
> Why?
>
> 1. Nobody has worked on the code for years.
>
> 2. The guy who originally worked on the code is gone, and can't
> work on the code even if he wanted t
Hello,
I officially propose removing DSage from the Sage distribution.
Why?
1. Nobody has worked on the code for years.
2. The guy who originally worked on the code is gone, and can't
work on the code even if he wanted to (due to conditions of his job).
3. So far as I can tell, DSage
Dear Sage and Sage-Combinat devs,
I just updated http://sagetrac.org/sage_trac/wiki/SageCombinatRoadMap
to reflect the big pile of work that has been done in 2009. I
certainly have forgotten things; in particular, I did not list
anything about words and the like. Please edit further!
I al
On Sun, Jan 17, 2010 at 11:20 PM, Dr. David Kirkby
wrote:
> Last week was a pretty annoying week for Solaris support. Two quite major
> obstacles came up.
>
> 1) #7932: _Complex_I undeclared - a new bug totally stops a Solaris 10
> build.
>
> has introduced code which exploits a bug in gcc, which
43 matches
Mail list logo
