Hi,
all the sudden we are hitting the same problem on sagemath.org:
20459 sage 16 0 11.2g 7.2g 1660 S2 92.7 81:52.22 python
i.e. we are using 11.2g virtual memory where we used to use a lot
less. Maybe it is time to do some poking around there :)
Cheers,
Michael
--~--~-~--
On Sep 13, 12:23 am, mabshoff <[EMAIL PROTECTED]> wrote:
> Hi,
>
> all the sudden we are hitting the same problem on sagemath.org:
>
> 20459 sage 16 0 11.2g 7.2g 1660 S 2 92.7 81:52.22 python
>
> i.e. we are using 11.2g virtual memory where we used to use a lot
> less. Maybe it is tim
(question for Ralf at the bottom of the mail :-)
"Mike Hansen" <[EMAIL PROTECTED]> writes:
> >> * Given a domain like "Polynomial Integer", how do I get the base ring
> >> "Integer" programatically? This would be like the base_ring method in
> >> Sage.
> >
> > You cannot, currently. One possibi
I agree with everything Jason said. It would be useful if you could
find one of the
lead developers who would be willing to review your code, once written, and
you could ask them about how to implement ideas. Bobby Moretti used to be
great for that but I don't know if he is still doing Sage stuff.
Hello folks,
here is the somewhat delayed 3.1.2.rc2. We fixed some build issues,
fixed a bunch of annoying doctest failures and updated Cython due to
some recently discovered cpdef issues. So this rc2 contains a couple
more fixed than initially planned. There are a couple known issues we
have to
I've tested the new poset drawings now, and I like what I see. Good
work!
Anders
On Aug 11, 8:19 pm, "Franco Saliola" <[EMAIL PROTECTED]> wrote:
> Hello Anders,
>
> On Mon, Aug 11, 2008 at 5:23 AM, Anders Claesson
>
> <[EMAIL PROTECTED]> wrote:
>
> > Thanks Franco, I do understand how this work
On Sat, Sep 13, 2008 at 4:01 AM, David Joyner <[EMAIL PROTECTED]> wrote:
>
> I agree with everything Jason said. It would be useful if you could
> find one of the
> lead developers who would be willing to review your code, once written, and
> you could ask them about how to implement ideas. Bobby
I see the trac items, but I do not see how to get the latest version of
axiom.py...
Thanks,
Martin
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more opt
Martin,
The patches are at:
http://trac.sagemath.org/sage_trac/attachment/ticket/4036
Click on for example: trac_4036-2.patch
http://trac.sagemath.org/sage_trac/attachment/ticket/4036/trac_4036-2.patch
This displays the patch with additions and deletions highlighted.
At the bottom of the pag
"Bill Page" <[EMAIL PROTECTED]> writes:
> Martin,
>
> The patches are at:
>
> http://trac.sagemath.org/sage_trac/attachment/ticket/4036
>
> Click on for example: trac_4036-2.patch
>
> http://trac.sagemath.org/sage_trac/attachment/ticket/4036/trac_4036-2.patch
>
> This displays the patch with
Hi Martin,
> Great! I applied this, but
>
> a = axiom(x^2 + 1)
> a.sage()
>
> still does not work. I guess I have to tell sage somehow to reconfigure or
> so?
You need to run start Sage with "sage -br" (for build and run) to make
the changes active.
--Mike
--~--~-~--~~---
On Sat, Sep 13, 2008 at 11:41 AM, Martin Rubey
<[EMAIL PROTECTED]> wrote:
>
> "Bill Page" <[EMAIL PROTECTED]> writes:
>
>> Martin,
>>
>> The patches are at:
>>
>> http://trac.sagemath.org/sage_trac/attachment/ticket/4036
>>
>> Click on for example: trac_4036-2.patch
>>
>> http://trac.sagemath.org/
On Sep 13, 7:04 am, mabshoff <[EMAIL PROTECTED]> wrote:
> Hello folks,
>
> here is the somewhat delayed 3.1.2.rc2. We fixed some build issues,
> fixed a bunch of annoying doctest failures and updated Cython due to
> some recently discovered cpdef issues. So this rc2 contains a couple
> more fixed
"Mike Hansen" <[EMAIL PROTECTED]> writes:
> Hi Martin,
>
> > Great! I applied this, but
> >
> > a = axiom(x^2 + 1)
> > a.sage()
> >
> > still does not work. I guess I have to tell sage somehow to reconfigure or
> > so?
>
> You need to run start Sage with "sage -br" (for build and run) to make
OK, thanks to Bill, Mike and William the axiom interface is now mostly working
on my computer.
Mostly, because I think the following *should* work...
sage: a = axiom.sin(x)
sage: a
sin(x)
sage: a.sage()
---
NotImplementedErr
Hi,
I'm Cristian Consonni. I wish to contribute to Sage documentations
unless I'm a new user.
(I've produced a very brief Maxima presentation (in italian), you can
find it in Maxima's documentation page)
I hope to hear some news from you soon.
Ciao ciao
Cristian
--~--~-~--~~-
built fine on amd64 hardy heron but this test failed:
The following tests failed:
sage -t devel/sage/sage/modules/free_module.py
Total time for all tests: 5285.8 seconds
Please see /home/wdj/sagefiles/sage-3.1.2.rc2/tmp/test.log for the
complete log from this test.
[EMAIL PROTECTED]:~
Martin,
> The only slight awkwardness I can imagine is as follows: If I export, say, in
> Polynomial
>
> coefficientRing: () -> Ring
>
> then the result of baseRing will be a Ring, and may have "forgotten" all the
> other categories it possibly satisfies. Hm, it seems I will never understand
>
On Sep 13, 1:39 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
> built fine on amd64 hardy heron but this test failed:
>
> The following tests failed:
>
> sage -t devel/sage/sage/modules/free_module.py
> Total time for all tests: 5285.8 seconds
> Please see /home/wdj/sagefiles/sage-3.1.2
On Sep 13, 10:54 am, Jason Merrill <[EMAIL PROTECTED]> wrote:
> On Sep 13, 7:04 am, mabshoff <[EMAIL PROTECTED]> wrote:
>
> > Hello folks,
Hi Jason,
> > here is the somewhat delayed 3.1.2.rc2. We fixed some build issues,
> > fixed a bunch of annoying doctest failures and updated Cython due to
Martin Rubey <[EMAIL PROTECTED]> writes:
> OK, thanks to Bill, Mike and William the axiom interface is now mostly working
> on my computer.
>
> Mostly, because I think the following *should* work...
>
> sage: a = axiom.sin(x)
I hacked around axiom.py a little, and came up with the following:
William Stein wrote:
> On Sat, Sep 13, 2008 at 4:01 AM, David Joyner <[EMAIL PROTECTED]> wrote:
> Jason, one thing to be honest is that when you suggest sweeping changes
> that are too big for one person to do, this seriously scares people. We've
> had many people over the last few years do just
On Sep 13, 5:02 pm, mabshoff <[EMAIL PROTECTED]> wrote:
> On Sep 13, 10:54 am, Jason Merrill <[EMAIL PROTECTED]> wrote:
> Hi Jason,
>
> > I tried to build 3.1.2.rc2 on OS X 10.5.4 intel macbook. As with the
> > previous release candidate, the build choked while building the clisp
> > documentatio
On Sep 13, 2:00 pm, mabshoff <[EMAIL PROTECTED]> wrote:
> On Sep 13, 1:39 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
>
> > built fine on amd64 hardy heron but this test failed:
>
> > The following tests failed:
>
> > sage -t devel/sage/sage/modules/free_module.py
> > Total time for a
On Sep 13, 7:09 pm, ghtdak <[EMAIL PROTECTED]> wrote:
> On Sep 13, 2:00 pm, mabshoff <[EMAIL PROTECTED]> wrote:
>
> > On Sep 13, 1:39 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
>
> > > built fine on amd64 hardy heron but this test failed:
>
> > > The following tests failed:
Hi Glenn,
> > >
On Sep 13, 7:06 pm, Jason Merrill <[EMAIL PROTECTED]> wrote:
Hi Jason
> > You have other crap either in DYLD_LIBRARY_PATH and/or /usr/local. In
> > addition if you have Fink installed make sure before starting to
> > build Sage that it is not in $PATH. Can you post a link to your log so
> >
Is there a convention for "see also" information? I thought I'd fix
http://trac.sagemath.org/sage_trac/ticket/3422 . The doc has
\begin{seealso}
See \seeurl{http://www.dtc.umn.edu/\~{}odlyzko/zeta_tables/}{}
\end{seealso}
But when I run
sage: search_doc('seealso')
the odlyzko fil
All tests passed on my 10.5.4 intel macbook. Seems a little odd that
Jason Merrill had problems with what sounds like the same kind of
machine.
-M. Hampton
On Sep 13, 6:04 am, mabshoff <[EMAIL PROTECTED]> wrote:
> Hello folks,
>
> here is the somewhat delayed 3.1.2.rc2. We fixed some build issu
On Sep 13, 8:55 pm, mhampton <[EMAIL PROTECTED]> wrote:
> All tests passed on my 10.5.4 intel macbook. Seems a little odd that
> Jason Merrill had problems with what sounds like the same kind of
> machine.
It was an issue with MacPorts - without it in PATH and
DYLD_LIBRARY_PATH it passes and w
On Sat, Sep 13, 2008 at 8:35 PM, Jason Merrill <[EMAIL PROTECTED]> wrote:
>
> Is there a convention for "see also" information? I thought I'd fix
> http://trac.sagemath.org/sage_trac/ticket/3422 . The doc has
>
>\begin{seealso}
>See \seeurl{http://www.dtc.umn.edu/\~{}odlyzko/zeta_tables/
On Sat, Sep 13, 2008 at 4:47 PM, Jason Grout <[EMAIL PROTECTED]> wrote:
> William,
>
> Do you still have the worksheets from the public Sage server? Are they
> accessible from somewhere on sage.math? If not, can you send me the
> worksheets for user jason3?
Please see
http://sage.math.washingt
Hi,
Is http://hg.sagemath.org/ the current Mercurial repository? I ask
because the last changes are 3 weeks ago which given the various rc
releases seems like a long time. If not, where should I go to get the
latest repository?
Thanks,
Tim Lahey
---
Tim Lahey
PhD Candidate, Systems Desi
On Sat, Sep 13, 2008 at 10:53 PM, Tim Lahey <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Is http://hg.sagemath.org/ the current Mercurial repository? I ask because
> the last changes are 3 weeks ago which given the various rc releases seems
> like a long time. If not, where should I go to get the latest r
Regarding sage-3.1.2.rc2, ...
I saw a few of the same little noise issues people reported above.
One *major* issue that remains is that the lisp.py doctest hangs forever
on OS X ppc 10.5:
sage -t -long devel/sage/sage/interfaces/lie.py
[5.5 s]
sage -t -long devel/sage/sage/interfaces/li
Thanks,
I was wondering since the Hg repository listed in
the on-line docs didn't work and I only found the
hg.sagemath.org after finding a trac ticket to
update the docs.
Cheers,
Tim Lahey
On Sep 14, 2008, at 1:57 AM, William Stein wrote:
Get the sage-* spkg in the current rc release. E.
On Sep 13, 10:57 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Sat, Sep 13, 2008 at 10:53 PM, Tim Lahey <[EMAIL PROTECTED]> wrote:
> > Hi,
>
> > Ishttp://hg.sagemath.org/the current Mercurial repository? I ask because
> > the last changes are 3 weeks ago which given the various rc releases
Hi,
while hunting some memleak in gen.pyx I noticed that some functions
that call new_gen do not call _sig_on where they should. A list is
below. There also seem to be a couple places where _sig_off is called
where it should be not, but I do not have a list.
Cheers,
Michael
def getattr(sel
37 matches
Mail list logo
