I think it is a good idea consolidate the capabilities of all these
functions in show(). However, is there a way to deprecate a function
but still make old code evaluate correctly if it calls this function?
Perhaps it would just be a matter of changing the docstring to
'deprecated, see show()' or
On Dec 5, 1:42 am, Stan Schymanski <[EMAIL PROTECTED]> wrote:
Hi Stan,
> I think it is a good idea consolidate the capabilities of all these
> functions in show().
Some sprint cleaning in that area would be pretty good. I don't think
there are too many users, but deprecation is the way to go.
Hello folks,
here goes 3.2.2.alpha0. We have been steadily merging patches and
gotten some of the larger and more disruptive patches in. The most
visible change is #717 by Gary Furnish which finally fixes a long
standing problem with time out issues in doctests, i.e. with this
release any hanging
Hello folks,
as the subject states there are currently roughly 31 tickets in need
of review in trac. See
http://trac.sagemath.org/sage_trac/report/14
for a listing by components. Some of them are already spoken for and
are waiting on some feedback while others are up for grabs. If you are
the
Hello folks,
the extcode repo in Sage is somewhat of a dumping ground what doesn't
really fit anywhere else. Below is the disk use of all directories
that aren't more or less empty:
44K dist
36K gap
24K images
1.2Mjavascript
228Kmagma
52K maxima
3.0Mnotebook
1.9Mp
I think I can rewrite the gap code in Sage now. However, it would be a
rather large
patch (read "patch bomb") though.I could also just delete it and the
method in the class which uses it.
On Fri, Dec 5, 2008 at 5:54 AM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> Hello folks,
>
> the extcode repo in
mabshoff wrote:
> Hello folks,
>
> here goes 3.2.2.alpha0. We have been steadily merging patches and
> gotten some of the larger and more disruptive patches in. The most
> visible change is #717 by Gary Furnish which finally fixes a long
> standing problem with time out issues in doctests, i.e. w
How worrying is this:
In 3.2.1 we have:
{{{
sage: K.=QuadraticField(2310)
sage: C=K.class_group()
sage: I=C.0
sage: I^-1
AttributeError
...
AttributeError: 'FractionalIdealClass' object has no attribute 'is_one'
}}}
(cf #1052).
Now I add one line in sage/rings/number_field/class_group.py, namely
On a related note, for those who remember the Connected Curriculum
Project at Duke and/or Project Calc, the PIs from that have a new (and
nice) online text for calculus from a diffeq perspective, and are
explicitly asking for:
Additional CAS Options. Currently the activities, checkpoints, and
exe
I'm just forwarding this to sage-edu because I think that's really
where the discussion belongs (although there is some overlap). I
would be interested in discussing this at the joint meetings as well.
-Marshall
On Dec 5, 11:42 am, kcrisman <[EMAIL PROTECTED]> wrote:
> On a related note, for th
On Intel Mac OS X 10.5, I'm getting failures after upgrading from
3.2.1: the first time I did './sage -testall -long', it hung after the
tutorial, but I haven't been able to reproduce this. The other times,
I'm getting
"A mysterious error (perphaps a memory error?) occurred, which may
have crashe
Installed fine and all tests passed on amd64 hardy heron.
On Fri, Dec 5, 2008 at 5:19 AM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> Hello folks,
>
> here goes 3.2.2.alpha0. We have been steadily merging patches and
> gotten some of the larger and more disruptive patches in. The most
> visible chan
On Dec 5, 9:58 am, John H Palmieri <[EMAIL PROTECTED]> wrote:
Hi John,
> On Intel Mac OS X 10.5, I'm getting failures after upgrading from
> 3.2.1: the first time I did './sage -testall -long', it hung after the
> tutorial, but I haven't been able to reproduce this. The other times,
> I'm gett
On Dec 5, 7:19 am, Jaap Spies <[EMAIL PROTECTED]> wrote:
Hi Jaap,
>
> Om Fedora 9, 32 bits after an upgrade from 3.2.1-rc1:
>
> --
> The following tests failed:
>
> sage -t "devel/sage/sage/rings/polynomial/multi_poly
On Dec 5, 4:49 am, "David Joyner" <[EMAIL PROTECTED]> wrote:
Hi David,
> I think I can rewrite the gap code in Sage now. However, it would be a
> rather large
> patch (read "patch bomb") though.I could also just delete it and the
> method in the class which uses it.
What does the code do and wh
On Dec 5, 10:35 am, mabshoff <[EMAIL PROTECTED]> wrote:
> On Dec 5, 9:58 am, John H Palmieri <[EMAIL PROTECTED]> wrote:
>
> Hi John,
>
> > On Intel Mac OS X 10.5, I'm getting failures after upgrading from
> > 3.2.1: the first time I did './sage -testall -long', it hung after the
> > tutorial, but
I think you've uncovered a bug that had been masked by the is_one bug.
If I'm not mistaken, I^-1 calls MultiplicativeGroupElement.__invert__,
which tests whether self is one and if not returns 1/self. Obligingly,
the coercion model (being asked to calculate 1/self) calls __invert__
again!
(I conv
On Fri, Dec 5, 2008 at 1:37 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> On Dec 5, 4:49 am, "David Joyner" <[EMAIL PROTECTED]> wrote:
>
> Hi David,
>
>> I think I can rewrite the gap code in Sage now. However, it would be a
>> rather large
>> patch (read "patch bomb") though.I could also just delet
I've also been getting the "mysterious error may have crashed doctest"
messages, and on closer inspection I think there's actually a bug *in
the doctest framework*, which causes it to report all failed doctests
as "mysterious errors". I tested this myself by creating a Python file
with a single fu
On Dec 5, 11:06 am, daveloeffler <[EMAIL PROTECTED]> wrote:
Hi David,
> I've also been getting the "mysterious error may have crashed doctest"
> messages, and on closer inspection I think there's actually a bug *in
> the doctest framework*, which causes it to report all failed doctests
> as "mys
daveloeffler wrote:
> I've also been getting the "mysterious error may have crashed doctest"
> messages, and on closer inspection I think there's actually a bug *in
> the doctest framework*, which causes it to report all failed doctests
> as "mysterious errors".
I think you are right!
Jaap
--~
On Fri, Dec 5, 2008 at 2:54 AM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> Hello folks,
>
> the extcode repo in Sage is somewhat of a dumping ground what doesn't
> really fit anywhere else. Below is the disk use of all directories
> that aren't more or less empty:
>
> 44K dist
> 36K gap
> 24K
On Dec 5, 11:27 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Fri, Dec 5, 2008 at 2:54 AM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> > Hello folks,
>
> > the extcode repo in Sage is somewhat of a dumping ground what doesn't
> > really fit anywhere else. Below is the disk use of all directori
That sounds right (and I'm sure it is).
What is worrying me slightly is that I have a vague memory that I once
edited that generic __invert__() code (possibly it was me who added
the is_one() test.
I would prbably be best to have __invert__() NotImplmented in the base
class, forcing all derived
mabshoff wrote:
> Hello folks,
>
> here goes 3.2.2.alpha0. We have been steadily merging patches and
> gotten some of the larger and more disruptive patches in. The most
> visible change is #717 by Gary Furnish which finally fixes a long
> standing problem with time out issues in doctests, i.e.
Two cents from me:
(1) the gp scripts called "cremona" are largely, but not entirely,
redundant now that what they do is either implemented directly in Sage
(e.g. group structure for elliptic curvesw over prime fields), never
wrapped anyway (Weil pairings for ditto), or better implemented
elsewhe
Fresh build on 64-bit Suse:
The following tests failed:
sage -t "devel/sage/sage/interfaces/sage0.py"
but a subsequent separate test passed. The original error message was:
sage -t "devel/sage/sage/interfaces/sage0.py"
A mysterious error (perphaps a memory error?) occurred, which may
2008/12/5 John Cremona <[EMAIL PROTECTED]>:
> Fresh build on 64-bit Suse:
>
> The following tests failed:
>sage -t "devel/sage/sage/interfaces/sage0.py"
>
> but a subsequent separate test passed. The original error message was:
> sage -t "devel/sage/sage/interfaces/sage0.py"
> A mysteri
I've opened a ticket (#4719) for doctest crashing on failures.
[mabshoff]
> OK. I am seeing the numerical noise issue at #4276, but I would also
> be curious about the cachefunc.py failure.
The failure I'm getting is in the doctest for
CachedFunction._sage_src_. Running with verbose mode on one
On Dec 5, 1:20 pm, daveloeffler <[EMAIL PROTECTED]> wrote:
Hi David,
> I've opened a ticket (#4719) for doctest crashing on failures.
Thanks, I commented on the ticket about the likely cause and CCed the
right people.
> > OK. I am seeing the numerical noise issue at #4276, but I would also
>
mabshoff wrote:
>
>
> On Dec 5, 7:19 am, Jaap Spies <[EMAIL PROTECTED]> wrote:
>
> Hi Jaap,
>
>
> Can you check if a "sage -ba" fixes those issues?
>
This did not help :(
Jaap
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegro
On Dec 5, 1:35 pm, Jaap Spies <[EMAIL PROTECTED]> wrote:
> mabshoff wrote:
>
> > On Dec 5, 7:19 am, Jaap Spies <[EMAIL PROTECTED]> wrote:
>
> > Hi Jaap,
>
> > Can you check if a "sage -ba" fixes those issues?
>
> This did not help :(
Yeah, no surprise here since David Loeffler nailed the proble
mabshoff wrote:
>
>
> On Dec 5, 1:35 pm, Jaap Spies <[EMAIL PROTECTED]> wrote:
>> mabshoff wrote:
>>
>>> On Dec 5, 7:19 am, Jaap Spies <[EMAIL PROTECTED]> wrote:
>>> Hi Jaap,
>>> Can you check if a "sage -ba" fixes those issues?
>> This did not help :(
>
> Yeah, no surprise here since David Loe
On Dec 5, 2:13 pm, Jaap Spies <[EMAIL PROTECTED]> wrote:
> mabshoff wrote:
Hi Jaap,
> > It would also be nice if you could open a ticket for the numerical
> > noise doctest issue you hit since the output from at least the first
> > example seemed truncated.
>
> It is now #4720.
Thanks.
> >
mabshoff wrote:
>
>
> On Dec 5, 2:13 pm, Jaap Spies <[EMAIL PROTECTED]> wrote:
>> mabshoff wrote:
[...]
>
>>> And if you are still hitting that odd failure in combinat on FC 10
>>> please open a ticket for that one, too. It might be a Heisenbug, but
>>> experience has taught me that this is som
On Fri, Dec 5, 2008 at 12:20 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
> On Dec 5, 11:27 am, "William Stein" <[EMAIL PROTECTED]> wrote:
>> On Fri, Dec 5, 2008 at 2:54 AM, mabshoff <[EMAIL PROTECTED]> wrote:
>>
>> > Hello folks,
>>
>> > the extcode repo in Sage is somewhat of a dumping ground w
Hi folks,
I'm a bit behind the times. I just upgraded to sage-3.2.1 on my various
machines and ran tests. All is fine except on
[EMAIL PROTECTED] sage]$ uname -a
Linux orphus.ms.unimelb.edu.au 2.6.9-78.0.1.ELsmp #1 SMP Tue Jul 22 18:01:05
EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
where tests/boo
Hello folks.
I'm afraid this is may be not possible, but however
here is a suggestion. I strive to compile Sage
on a somewhat weak/outdated hardware.
Actually, the problem is not at all that
compilation as a whole takes a very long time, but the
fact that when a compilation of a given package whi
On Dec 5, 10:35 am, mabshoff <[EMAIL PROTECTED]> wrote:
> On Dec 5, 9:58 am, John H Palmieri <[EMAIL PROTECTED]> wrote:
>
> Hi John,
>
> > On Intel Mac OS X 10.5, I'm getting failures after upgrading from
> > 3.2.1: the first time I did './sage -testall -long', it hung after the
> > tutorial, but
On Dec 5, 4:39 pm, John H Palmieri <[EMAIL PROTECTED]> wrote:
> On Dec 5, 10:35 am, mabshoff <[EMAIL PROTECTED]> wrote:
Hi John,
> > It would be interesting to see if anyone can reproduce the upgrade
> > problem on one hand and on the other if a -ba had fixed it.
>
> sage -ba crashes because i
On Dec 5, 4:24 pm, "Alex Ghitza" <[EMAIL PROTECTED]> wrote:
> Hi folks,
Hi Alex,
> I'm a bit behind the times.
Maybe it is that down under thing where winters are summers and the
water swirls the other direction? :)
> I just upgraded to sage-3.2.1 on my various
> machines and ran tests. Al
On Dec 5, 2:53 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
Hi William,
> I'm strongly in favor of this proposal.
Cool, I am keeping an eye on this then, also in hindsight regarding
John's comment about "his" pari code. The plan for 3.2.2 is to get the
javascript spkgs broken out (which i
On Fri, Dec 5, 2008 at 4:26 PM, bourbabis <[EMAIL PROTECTED]> wrote:
>
> Hello folks.
>
> I'm afraid this is may be not possible, but however
> here is a suggestion. I strive to compile Sage
> on a somewhat weak/outdated hardware.
> Actually, the problem is not at all that
> compilation as a whole
On Sat, Dec 6, 2008 at 11:53 AM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> Maybe it is that down under thing where winters are summers and the
> water swirls the other direction? :)
>
>
Yes, it must be the heat getting to me :) Good that I'm flying to Germany
in two weeks, that should cure me.
>
On Fri, Dec 5, 2008 at 4:39 PM, John H Palmieri <[EMAIL PROTECTED]> wrote:
>
> On Dec 5, 10:35 am, mabshoff <[EMAIL PROTECTED]> wrote:
>> On Dec 5, 9:58 am, John H Palmieri <[EMAIL PROTECTED]> wrote:
>>
>> Hi John,
>>
>> > On Intel Mac OS X 10.5, I'm getting failures after upgrading from
>> > 3.2.
On Fri, Dec 5, 2008 at 4:57 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
> On Dec 5, 2:53 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
>
> Hi William,
>
>
>
>> I'm strongly in favor of this proposal.
>
> Cool, I am keeping an eye on this then, also in hindsight regarding
> John's comment about
On Dec 5, 5:12 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Fri, Dec 5, 2008 at 4:57 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> > On Dec 5, 2:53 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
>
> > Hi William,
>
> >
>
> >> I'm strongly in favor of this proposal.
>
> > Cool, I am keeping
On Dec 5, 2008, at 02:19 , mabshoff wrote:
>
> Hello folks,
>
> here goes 3.2.2.alpha0. We have been steadily merging patches and
> gotten some of the larger and more disruptive patches in. The most
> visible change is #717 by Gary Furnish which finally fixes a long
> standing problem with time
Hello,
Sage Days 12 San Diego will be held January 21st-24th, 2009 at UCSD.
Its focus will be on improving the quality of Sage by fixing known
bugs from our tracker as well as ongoing work on an implementation of
Jean-Charles Faugere's F5 algorithm for computing Gröbner bases. There
are currently
Hi Michael,
On Fri, Dec 5, 2008 at 6:38 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> Sage Days 12 San Diego will be held January 21st-24th, 2009 at UCSD.
[...]
> The deadline for applications is December 12th, 2009, 5pm PST. The
I think you mean that the deadline is December 12th, 2008
On Dec 5, 7:06 pm, "Minh Nguyen" <[EMAIL PROTECTED]> wrote:
> Hi Michael,
>
>
>
> On Fri, Dec 5, 2008 at 6:38 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> > Hello,
>
> > Sage Days 12 San Diego will be held January 21st-24th, 2009 at UCSD.
> [...]
> > The deadline for applications is December 12th
On 5-Dec-08, at 10:57 AM, daveloeffler wrote:
>
> I think you've uncovered a bug that had been masked by the is_one bug.
> If I'm not mistaken, I^-1 calls MultiplicativeGroupElement.__invert__,
> which tests whether self is one and if not returns 1/self. Obligingly,
> the coercion model (being a
This *sucks*:
--
| Sage Version 3.2.2.alpha0, Release Date: 2008-12-05|
| Type notebook() for the GUI, and license() for information.|
--
On Dec 5, 2008, at 02:19 , mabshoff wrote:
>
> Hello folks,
>
> here goes 3.2.2.alpha0. We have been steadily merging patches and
> gotten some of the larger and more disruptive patches in. The most
> visible change is #717 by Gary Furnish which finally fixes a long
> standing problem with time
54 matches
Mail list logo
