Are you sure about lines 670 and 671? These point to docstrings in my case.
Anyway, I have created a bug for this:
http://trac.sagemath.org/sage_trac/ticket/14451.
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group and
Thanks! This is sufficient for me to experiment with it.
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this
Hi,
I just discovered that a doctest in 5.9beta5 with the # tol keyword is not
able to use the ellipsis properly. In particular, I tried to patch the
doctest in
sage/numerical/mip.pyx
at line 2031. The expected output contains the version string of GLPK which
I want to replace with the
On Apr 12, 4:24 pm, Keshav Kini keshav.k...@gmail.com wrote:
Wow, this sounds really interesting. IMHO replacing our homegrown SPKG
system with a more general and commonly used system would be great. Reusing
code, and all that. It would also allow us to use the power of `emerge -C`
to, say,
Hi,
On Nov 11, 5:05 pm, Dr. David Kirkby david.kir...@onetel.net
wrote:
I was just looking at a file in Sage, which lists the dependencies for ECL:.
It has:
$(INST)/$(ECL): $(BASE) $(INST)/$(MPIR) $(INST)/$(TERMCAP) \
$(INST)/$(READLINE) $(INST)/$(BOEHM_GC)
which means
On Nov 12, 9:39 am, I csch...@students.uni-mainz.de wrote:
Hi,
On Nov 11, 5:05 pm, Dr. David Kirkby david.kir...@onetel.net
wrote:
I was just looking at a file in Sage, which lists the dependencies for
ECL:. It has:
$(INST)/$(ECL): $(BASE) $(INST)/$(MPIR) $(INST)/$(TERMCAP) \
I think it can be deleted from SAGE_ROOT (we did this on gentoo and it
works well), but of course you have to adjust some files: spkg-
install, sage-spkg-install and sage-make_devel_packages.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group,
Hi,
our work with sage-on-gentoo has seen great progress - we are now able
to supply fully working and recent versions of Sage which live in /
usr. We did this (among other things) by setting
SAGE_LOCAL=/usr
SAGE_ROOT=/usr/share/sage
This enables Sage to put all scripts and binaries into
There are six python files which would need a patch and more than five
(we need only small numbers of scripts from sage_scripts). You may
have look and the patches here:
-
http://www.students.uni-mainz.de/cschwan/sage-baselayout-4.5.1-fix-SAGE_LOCAL.patch
-
http://www.students.uni-mainz.de
On 30 Jun., 16:05, Georg S. Weber georgswe...@googlemail.com
wrote:
Great work!
Actually, it makes me think about installing Gentoo just to test this
(I do know I don't have the time for this, but it does wet my mouth
nevertheless).
I take this as a compliment - thanks !
Two further
On Jun 29, 1:03 pm, François Bissey f.r.bis...@massey.ac.nz wrote:
[..] excellent summary [..]
If have been reading this far - thank you for your time.
Christopher may add comments on anything that I forgot.
One thing:
- We do not install scipy_sandbox but instead apply the patches from
this
For the ebuild you may take a look at
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sci-libs/blas-atlas/blas-atlas-3.9.23.ebuild?revision=1.1view=markup
, which is the ebuild for 3.9.23 (there are newer ebuilds, but they
contain patches which most likely fail). If you are not used to
There are actually two:
http://trac.sagemath.org/sage_trac/ticket/9121
http://trac.sagemath.org/sage_trac/ticket/9004
--
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
this behaviour:
http://github.com/cschwan/sage-on-gentoo/blob/master/sci-mathematics/sympow/sympow-1.018.ebuild
(see lines 27 to 55).
I think this could be adapted for Sage, too, but this would be more
difficult because one cannot assume ${SAGE_LOCAL} to be /.
No idea why the current scheme
@Willem: I took the suppression file from Sage's valgrind.spkg - this
filtered a lot meesages.
@Paulo:
valgrind --db-attach=yes --freelist-vol=1 python
/usr/share/sage/local/bin/sage-ipython
does not work for me - valgrind prints only a message while starting,
but does not show summary
Hello,
porting Sage to Gentoo progresses well, we now have a split version
where all all dependencies of Sage are installed with portage.
Unfortunately, we experience serious problems on amd64 when exiting
Sage. When doing so, there is a slight chance of getting a SIGABRT
error, which is always
I already tried valgrind but it did not work - how do I exactly use
it ? When I run
sage -valgrind -t -force_lib devel/sage/doc/en/reference/sage/
categories/examples/algebras_with_basis.rst
I get:
--
| Sage Version 4.4.1,
Hello,
since this is my first post on this list I think it is a good idea to
briefly introduce myself: My name is Christopher Schwan, I am studying
physics at Uni Mainz (Germany) and I am one of the maintainers of
sage-on-gentoo (http://github.com/cschwan/sage-on-gentoo). Francois
Bissey
Though these would be good to fix, I'm wary of all of the above for a
stabilization release.
Oh, I overlooked the most important part: Stabilization release -
the tickets wouldnt serve that purpose, of course. Nevertheless, these
would be the ones which I would like to see fixed :) .
Sounds
19 matches
Mail list logo
