Short story: for me it was far more important *that* the problem got
fixed, not *how* it got fixed.
A situation where a ticket is merged but then problems are discovered is
a difficult situation to handle. In the past, I would have re-opened
the ticket and set it to needs_work but that seems to
Hello,
I am trying to compile sage-4.1.1 from source on a Gentoo Linux x86_64
system with the experimental gcc-4.5.0.
There are two issues, which are really the same problem.
*** FIRST ISSUE ***
gcc -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes
-fPIC
William Stein wrote:
On Wed, Sep 16, 2009 at 5:45 AM, Jeroen Demeyer jdeme...@cage.ugent.be
wrote:
I am trying to compile sage-4.1.1 from source on a Gentoo Linux x86_64
system with the experimental gcc-4.5.0.
There are two issues, which are really the same problem.
Are they the only
Hello sage-devel,
While working on #9343, I discovered that some of the doctests (in
particular, related to elliptic curves) use lots of memory (more than 1GB).
I know that Sage has a # long time option for tests which take a long
time. Maybe there should be an option # huge memory or something
On 2010-07-22 10:41, John Cremona wrote:
Perhaps Jeroen is using pari 2.4.3 and that behaves differently?
No, this was the old PARI from a non-patched Sage 4.5.1. As I said in
#9343, the new PARI seems to use even more memory than the old PARI, but
both of them use a lot.
The pari library does
Hello,
This question is motivated by #9343, but I think it fits here.
Suppose I have an external spkg written in C using a lot of #define's.
How do I get these #define's to work in Cython?
More concretely: in the pari source file src/headers/parigen.h, there is
#define lgefint(x)
On 2010-07-27 21:25, David Kirkby wrote:
Currently if a test fails in the doctest, one can never be sure if the
machine may have run out of swap space, disk space disk I/O problems
or all manner of other things that could cause test failures. But if
the time of the failure was recorded, then
Hello all,
My working on the big PARI-upgrade (#9343) has sprouted many ideas. One
of these (possibly crazy) ideas is the following: we might manage to
some extent to make 32-bit PARI behave like 64-bit PARI. Because right
now various doctests return different results depending on the word size
Hello sage-devel,
At present, the error catching mechanism from PARI is rather bad: you
get exceptions like
Traceback (most recent call last):
...
PariError: (15)
I would like to change this (and created ticket #9640). When looking
into this issue, I realize it would make sense to add a
Hello sage-devel,
I think we should think about NumberFieldFractionalIdeal.__repr__(),
i.e. how to print an ideal in a number field. Right now, we actually
check whether the ideal is principal (and then use a generator to print
the ideal). This is very slow, especially with proof=True. I see
On 2010-08-03 19:11, William Stein wrote:
How about if whenever somebody runs
make testlong
at the end an email is sent to saget...@gmail.com that contains some
information:
* description of platform (OS + hardware)
* list of files where tests failed
* version of sage
On 2010-08-04 09:59, Robert Bradshaw wrote:
The new version of Pari has better error messages, though it'll be a
bit of work to get at them.
It won't be that hard. PARI uses callbacks to write its error messages.
We just have to direct those callbacks to a function writing into
I have a technical question about the implementation of
NumberFieldIdeal.gens_reduced().
In sage/rings/number_field/number_field_ideal.py, there is:
def gens_reduced(self, proof=None):
[...]
except AttributeError:
K = self.number_field()
nf =
On 2010-08-15 18:59, John Cremona wrote:
My guess is that in the prime case it's easy to find the smallest
integer, and desirable that the 2 generators always have the form p,
alpha in that order with p the underlying prime. But it may well be
that PARI's idealtwoelt() function does that
On 2010-08-15 21:14, Jeroen Demeyer wrote:
On 2010-08-15 18:59, John Cremona wrote:
My guess is that in the prime case it's easy to find the smallest
integer, and desirable that the 2 generators always have the form p,
alpha in that order with p the underlying prime. But it may well
Hello all,
I noticed some classes in Sage have a _pari_ method (which seems to be
used to convert self to a PARI GEN). But there is also _pari_init_,
which seems to be more or less the same (although, through a string).
What is the point of this? If there is any documentation about this,
feel
On Thu, Aug 19, 2010 at 03:59:14PM -0700, Simon King wrote:
Hi Jeroen,
On 19 Aug., 23:54, Jeroen Demeyer jdeme...@cage.ugent.be wrote:
I noticed some classes in Sage have a _pari_ method (which seems to be
used to convert self to a PARI GEN). But there is also _pari_init_,
which seems
On 2010-08-21 07:55, Carl Witty wrote:
On Fri, Aug 20, 2010 at 9:26 PM, Dr. David Kirkby
david.kir...@onetel.net wrote:
Unless OS X rounds by default to 64-bits, I can't understand how this would
have ever worked. Why was it not necessary to change the rounding behavior
of an Intel based OS X
I created the following page which will hopefully make reviewing easier:
http://wiki.sagemath.org/NewPARI
--
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
On 2010-08-21 22:49, Dr. David Kirkby wrote:
http://boxen.math.washington.edu/home/kirkby/patches/sympow-1.018.1.p8/patches/fpu.c
Let me just mention that very new versions of gcc support setting the
FPU precision on the gcc command line with the options -mpc32, -mpc64,
-mpc80. This might be
On 2010-08-22 03:45, Dr. David Kirkby wrote:
I don't know if sage 4.6 is going to be an exclusively Pari release, but
if not, it would be really good to get #9703 and #9735 merged, as then
there are two new complete ports, where all doc tests pass
* Solaris 10 x86 (32-bit)
I thought the new
On 2010-08-22 10:38, Jeroen Demeyer wrote:
I thought the new PARI doesn't work on Solaris. In fact, you wrote on
http://trac.sagemath.org/sage_trac/ticket/9343#comment:281
I can confirm what John found on 't2.math' - this package is now
broken on Solaris 10 SPARC in at least 32-it mode.
My
On 2010-08-22 22:23, Oscar Gerardo Lazo Arjona wrote:
I'm trying to find the solutions to solve this equation
sage: a=8594.0*x^3 - 30768.0 *x^2 + 36399.0 *x -14224.0
sage: b=solve(a==0,x)
sage: for i in b:
: c=i.rhs()
: print c.n()
:
1.19783952189420 -
Hello,
It looks that #9343 is more or stable now (for a while now, the only
issues have to do with porting).
I think it's time for somebody to look at #9400. It's a patch written
by William with additions by me. It changes quite of bit of NumberField
code and also cleans up various functions
On 2011-07-08 15:09, Vincent D wrote:
{{{
sage: G1 = DiGraph(loops=True,multiedges=True)
sage: G1.add_edges([
...(0, 0, 'c'), (0, 4, 'b'), (0, 5, 'c'), (0, 5, 't'), (1, 1,
'c'),
...(1, 3,'c'), (1, 3, 't'), (1, 5, 'b'), (2, 2, 'c'), (2, 3,
'b'),
...(2, 4, 'c'),(2, 4, 't'), (3,
On 2011-07-08 15:15, Vincent D wrote:
Actually, the problem is even worst... the function relabel does not
do the right job! The graph G2 obtained as above has two loops at the
vertex 4.
Well, to what does to vertex 4 get mapped to under your permutation?
--
To post to this group, send an
This is certainly a bug. The generators (reduced or not) have nothing
to do with this and are not the solution. The HNF's are simply PARI
matrices and equal matrices should have equal hashes.
I opened http://trac.sagemath.org/sage_trac/ticket/11611
--
To post to this group, send an email to
On 2011-07-25 15:40, John Cremona wrote:
A second point Karim made is that he would like to see more more cases
(currently: 0) in which a deficiency in a part of Pari used by Sage
-- for example, some number field functionality -- was fixed by
contributions to Pari itself, rather than by
On 2011-07-25 21:57, Karim Belabas wrote:
We badly need feedback at a higher level, from developpers or would-be
developpers, regarding the features they think are lacking in Pari, and
are preventing them from developping in Pari the way they would like to.
I'm sorry to say this (I would
Sometimes, it can happen that a patch only applies with fuzz, for example:
$ hg import
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/11298/trac11298_singular_standard_options.rebase4.7.1.a1.patch
patching file doc/en/reference/misc.rst
Hunk #1 succeeded at 10 with fuzz 2 (offset 0
On 2011-07-29 22:44, kcrisman wrote:
Right, but it would also seem that it is unwise to (say) try to add
functionality on top of 4.7.1.rcx when tickets for overlapping code
say merged in 4.7.2.alphay. So, at least while Jeroen is release
manager (which very happily seems to be an ongoing
To the sysadmin of the buildbot machine cicero:
It seems that gcc and g++ have recently been upgraded to version 4.6.1
but gfortran is stuck at 4.6.0. Personally, I don't know what can go
wrong when mixing versions like this, but Sage doesn't like it:
checking if gcc accepts -dumpversion
On 2011-08-02 19:09, William Stein wrote:
Hi,
There is now a high priority wishlist of bugs/issues to work on for
Sage Days 32 (Bug Days):
http://wiki.sagemath.org/days32/wishlist
In this list, I notice two tickets on which the Sage community does
not agree whether the patch is
Also http://www.sagemath.org/ is down, there seems to be a serious
problem (again) with the Sage cluster.
--
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
So, although broken, things are broken as expected ;-)
Quote of the day :-)
--
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
This is a blocker for 4.7.1: the new docutils (#10166) installs some
files not-world-readable which causes trouble when running Sage as a
different user from the user which compiled Sage. In particular, the
help from the notebook does *not* work.
Please see #11660 and review:
On 2011-08-08 15:01, Jeroen Demeyer wrote:
This is a blocker for 4.7.1: the new docutils (#10166) installs some
files not-world-readable which causes trouble when running Sage as a
different user from the user which compiled Sage. In particular, the
help from the notebook does *not* work
On 2011-08-08 20:11, leif wrote:
We could also create some post-install script that checks (and
optionally fixes) file permissions.
-1 because there is no reason to do it *post-install*, it would add
unnecessary complications to the build process and more potential for
unportable behavious.
On 2011-08-09 02:34, kcrisman wrote:
I'd add that the Developers deny it's a bug option is at least a
little offensive, or has the potential to be so. Developers do not
view as a bug or something like that is perhaps a little more
neutral.
I actually like developers deny it's a bug because
On 2011-08-08 15:54, Jeroen Demeyer wrote:
See also analogous tickets for other packages:
#11661 (gap)
#11662 (moin)
#11663 (singular)
#11664 (polybori)
I have updated spkgs for these, they all need review. I have built Sage
with these new spkgs and now all files after the Sage build have
On 2011-08-09 16:00, Maarten Derickx wrote:
1. change: Reported upstream. Little or no feedback. to Reported
upstream. Waiting for reply
2. Add a new option: Reported upstream. Waiting for reply
I'm slightly in favour for option 1.
+1
I would also shorten Reported upstream. Developers
On 2011-08-11 12:41, John Cremona wrote:
After building Sage the amount of filespace used is (as we all know)
rather large. I was just checking a 4.7 install, which is not used
for any development pusposes, and is on a machine which I use but do
not own, and where I was just told that the
I have completed milestone sage-4.7.1 on Trac but now all existing
tickets still refer to sage-4.7.1, this should be changed to sage-4.7.2.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
Hello sage-devel,
Can somebody explain the rationale for the following lines in
$SAGE_ROOT/sage:
if [ $SAGE_ROOT = . ]; then
SAGE_ROOT=`readlink -n $0 2 /dev/null` || \
SAGE_ROOT=`realpath$0 2 /dev/null` || \
SAGE_ROOT=$0
I think the following would work equally well:
if [
On 2011-08-22 00:38, MartinX wrote:
Graphviz would not install as pkg-config was not reading the
pangocairo.pc in the grphviz configure file in the sage environment so
it was not setting the includes correctly. Cause is a duplication of
SAGE_ROOT definition in sage's local libpng12.pc. This
Hello all,
This is a remainder that all ticket authors or reviewers should add
their real name on Trac when authoring/reviewing a ticket. Most regular
Sage developers already do this (except for this guy was :-) ) but you
should also tell your students or colleagues doing an occasional Sage
On 2011-08-24 20:52, Maarten Derickx wrote:
I can't seem to find in the history of sage where it exactly comes
from, but I think the solution proposed by Jeroen is indeed better.
In any case, there is now a patch for review at #5852:
http://trac.sagemath.org/sage_trac/ticket/5852
--
To post
Since Trac is currently down, I send you an email instead:
It seems that #10795 (QR decomposition) causes failures in a
non-reproducible way. Is there some randomness in the algorithm?
For example, I just got this failure on sage.math.washington.edu (a
machine on which I remember the test
Dear all,
For reasons of holidays and a conference, I will do little or no
Sage-related work up to at least 17 september (and probably some days
after that). I should be back up to speed for Sage Days 34 (starting 26
september).
I decided to quickly release sage-4.7.2.alpha2, so it is tested
On 2011-08-25 14:40, leif wrote:
What I can definitely say is that Sage 4.7.1.rc2's hg cannot handle
Sage 4.7.2.alpha2's root repo, which *will* break upgrading...
If this is true, then #10594 needs work!
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe
Hello all,
Have finite-dimensional algebras (over QQ, say) been implemented in
Sage? I mean an implementation where you can give any multiplication
table and compute with the algebra. Or to give such an algebra as a
sub-algebra of a matrix algebra (first computing the sub-algebra
generated by
On 2011-09-19 13:23, Dima Pasechnik wrote:
There is such functionality in GAP, so potentially one can just provide
an interface.
I guess providing an interface would be as much work (maybe even more)
as doing it directly in Sage. There is a lot of basic functionality
in GAP but not many
On 2011-09-20 12:27, Dima Pasechnik wrote:
This mandates the structure for
multiplication coefficients being clever.
You mean they should be sparse?
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
On 2011-09-22 11:07, Volker Braun wrote:
On Wednesday, September 21, 2011 7:53:16 PM UTC+1, John H Palmieri wrote:
Another idea would be to not cache it at all: don't save any file,
but save the preparsed file as a string and feed that in to
sage-python. (sage -preparse would
On 2011-10-04 15:44, leif wrote:
* We get integrity checking / checksums without further changes and
without additional files. (We may have to support gzip in sage-spkg,
but the required changes are trivial.)
I really do not understand how md5sums are related to compression.
--
To post to
I have prepared some small Sage scripts at:
http://boxen.math.washington.edu/home/jdemeyer/J0_46_disc.sage
http://boxen.math.washington.edu/home/jdemeyer/crystal.sage
http://boxen.math.washington.edu/home/jdemeyer/cyclomat.sage
http://boxen.math.washington.edu/home/jdemeyer/ellbsd.sage
On 2011-10-05 15:27, Jeroen Demeyer wrote:
crystal.sage:
* sage-4.7.2.alpha0: 4s
* sage-4.7.2.alpha2: 9s
This one is probably not a true regression, in #11183 a test was added
to the testsuite making it take more time.
--
To post to this group, send an email to sage-devel@googlegroups.com
On 2011-10-05 22:01, Simon King wrote:
Hi Jeroen!
Did you open a ticket for the regression, by the way?
No, but you should do it.
--
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
On 2011-10-05 15:27, Jeroen Demeyer wrote:
I have prepared some small Sage scripts at:
http://boxen.math.washington.edu/home/jdemeyer/J0_46_disc.sage
http://boxen.math.washington.edu/home/jdemeyer/crystal.sage
http://boxen.math.washington.edu/home/jdemeyer/cyclomat.sage
http
Hello all,
there is a very easy review needed at #11870: add support for an abs()
function for the RLF and CLF (Real/Complex Lazy Field).
Please review, see
http://trac.sagemath.org/sage_trac/ticket/11870
Thanks,
Jeroen.
--
To post to this group, send an email to sage-devel@googlegroups.com
On 2011-10-08 01:36, jsymons wrote:
Maybe some of you, based on the experience of using it, could explain
better than me what are the advantages/disadvantages with respect to
Tachyon renderer.
I think it is something very different from the Tachyon renderer.
Tachyon is a ray-tracing for 3D
I would really like to finally finish the PARI upgrade in order to merge
it in sage-4.7.3.alpha0. There are still two tickets which need review
for the new PARI:
* #11130: Update PARI to version 2.5.0. Almost everything here has
positive review, only the very trivial patch
Some notes:
* #11321: Make lcalc compatible with the new PARI.
This is Michael Rubinstein's L-function calculator, upstream is at
http://oto.math.uwaterloo.ca/~mrubinst/L_function_public/L.html
Luckily, for this review it is not necessary to know anything about the
workings of the L-function
On 2011-10-24 17:19, Keshav Kini wrote:
By the way, I think trailing whitespace is often intentional. Some
people consider this a good thing:
Some text$
$
Some more text$
Personally, I do NOT consider this a problem. I would like to remove
whitespace after non-empty lines, but
On 2011-10-25 02:33, Dan Drake wrote:
It seems like no one wants to have an epic break-all-patches-in-trac
patch that removes all the trailing whitespace in the Sage library --
and, some people like some trailing whitespace, so perhaps we should
also add just a warning to the sage-merge script
On 2011-10-25 09:51, Dan Drake wrote:
I think that would be a good idea, although if you're just running that
through sed, the exact patches applied would be different from the ones
on the trac server, which would cause some confusion.
Very true, but I think that is only a minor annoyance.
On 2011-10-27 19:14, John H Palmieri wrote:
The option to build spkg's in Sage in parallel has been available for
quite a while now, but it has to be enabled by setting the shell
variable SAGE_PARALLEL_SPKG_BUILD equal to yes. Should we change the
default, building in parallel unless this
Hello sage-devel and sage-nt,
At #11321, there is a new lcalc spkg ready for review. This is a
dependency for the new PARI (#11130), so it is very important that this
gets merged, there are a lot of tickets depending on this.
In order to review this, it is not necessary to know anything about
Hello,
Could somebody please review the following patch from #11130:
http://trac.sagemath.org/sage_trac/attachment/ticket/11130/11130-4.7.2.alpha3.patch
This is in the ticket to upgrade PARI to version 2.5.0. The patch fixes
a doctest which was added in sage-4.7.2.alpha3. Everything else on
Hello,
could somebody please review a patch which fixes the conversion from QQ
and matrices over ZZ/QQ to PARI? The ticket is #11854. The main issue
is that rationals are not converted properly. This can lead to equal
PARI rational numbers or number field ideals having a different hash.
The
Hello,
Ticket #11904 deals with the conversion of polynomials over number
fields to PARI. Currently, this cannot be done in Sage. The issue is
with PARI's variable priorities. The patch fixes this by using the
variable y instead of x by default for PARI number field elements.
Then x can be
Hello,
Currently, there is no support for the conversion of Python types (int,
long, float, complex) to PARI. This means that strings are used for the
conversion. First of all, this means that conversion from complex types
is broken because PARI does not understand 2j. Second, using strings
is
Hello,
Following a question on sage-support, I created a patch to enable the
numeric evaluation of erf() at complex arguments and with arbitrary
precision. The error function is evaluated using the PARI library. The
patch itself is fairly simple and should be easy to review. However,
this
Hello,
There is a very simple patch to add a sage -sqlite3 command line
option and a test in sage/tests/cmdline.py
See http://trac.sagemath.org/sage_trac/ticket/8654
Jeroen.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email
Hello,
Currenly quotient rings of polynomial rings do not have a cardinality()
method. The patch at #11947 implements this (essentially, the
cardinality equals the cardinality of the base field to the power the
degree of the modulus).
See http://trac.sagemath.org/sage_trac/ticket/11947
Hello,
Qepcad is an experimental package dealing with quantifier elimination.
There are doctests in sage/interfaces/qepcad.py which are badly
formatted and returning wrong results. The patch fixes this. This
patch is more important than it looks because it is a dependency for
#5155 (Fix
Hello,
I have a sympow spkg at #11920 ready for review. The source code of
sympow is almost not changed, the changes are mostly in the
configuration/build/installation of sympow.
Major changes are:
* Check FPU precision and use of fused-multiply-and-add instructions in
spkg-install, apply
Hello,
There are various issues with the canonicalization (i.e. resolving
symbolic links and making the path absolute) of $SAGE_ROOT. First of
all, canonicalization is only done in $SAGE_ROOT/sage and not (properly)
in sage-env. Second, the result is highly system-dependent, depending
on the
Hello all,
Simon King has a big patch at #11900 to speed-up categories. There were
some regressions at #9138, this patch fixes all of these and moreover,
even speeds up some things. This patch is quite important, there are
various tickets depending on it.
I have already checked that the patch
Important question: If I set
MAKE=make -j6
could it be that I get 36 processes in a parallel build? 6 packages in
parallel and 6 jobs per package? Or has this been taken care of?
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an
On 2011-11-02 15:39, John H Palmieri wrote:
On Wednesday, November 2, 2011 5:33:15 AM UTC-7, Jeroen Demeyer wrote:
Important question: If I set
MAKE=make -j6
could it be that I get 36 processes in a parallel build? 6 packages in
parallel and 6 jobs per package? Or has
On 2011-10-29 00:22, Dr. David Kirkby wrote:
My Opensolaris box hawk is back up. Those who have accounts, and the
buildbot, can use it again.
Can you remind me the full hostname please?
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send
On 2011-11-03 01:38, William Stein wrote:
I have some understanding of categories in Sage. However, I gave up
in frustration trying to apply 11900 and the
required prerequisites, because I got tired of stuff like:
Which version of Sage did you start from? For #11900, if you start from
On 2011-11-03 01:38, William Stein wrote:
So, as a kindness to the reviewer (who may
be me), can somebody build (or extract) a copy of Sage-4.7.3.alpha1
(say) on sage.math, apply all relevant patches for 11900, run make
ptestlong and confirm that all tests pass, and make a bdist of the
On 2011-11-03 01:38, William Stein wrote:
On Mon, Oct 31, 2011 at 4:42 AM, Jeroen Demeyer jdeme...@cage.ugent.be
wrote:
Hello all,
Simon King has a big patch at #11900 to speed-up categories. There were
some regressions at #9138, this patch fixes all of these and moreover,
even speeds up
On 2011-11-03 09:35, Simon King wrote:
Yes, I just verified it. It contains the plural wrapper #4539 and thus
all its dependencies: #11068, #5, #11575, #11900 and #9138, even
though none of them is marked as merged.
See
On 2011-11-03 22:24, William Stein wrote:
Also, any longterm strategy for getting Sage to really
work on Windows will require getting rid of any use of pexpect
Good riddance! Why not replace pexpect by somthing much simpler? I
have never believed that we really need pseudo-terminals for what
On 2011-11-03 22:24, William Stein wrote:
Let's do Sage-5.0 !
Were you suggesting let's do sage-5.0 now, i.e. the release after
sage-4.7.2? I agree that Python-2.7 and the new Notebook would justify
sage-5.0, but neither of these sound like they are close to being
finished (of course you can
- Franco Saliola
- Frédéric Chapoton [first contribution]
- Gustavo Rama
- Harald Schilly
- Ivan Andrus
- Ivo Hedtke [first contribution]
- Jan Groenewald
- Jason Grout
- Jason Hill [first contribution]
- Jean-Pierre Flori
- Jeroen Demeyer
- Johan Bosman
- John Cremona
On 2011-11-04 08:19, Julien Puydt wrote:
but rather a more deliberately fragile one :
- check very-specific-arch1, and set magic options if so ;
...
- check very-specific-archN, and set magic options if so ;
- if we aren't on a known arch, or a fly farted too near a known one :
FAIL.
This is
On 2011-11-05 15:44, Martin Albrecht wrote:
case $SHELL_NAME in
It's not that terribly important, by this wouldn't work for my ZShell prompt
because i use more advanced features in my prompt. In particular, my prompt
displays the revision number of the hg repository I'm in and whether it's
On 2011-11-08 07:51, Paulo César Pereira de Andrade wrote:
With the sympy/mpmath patches, I can drop a hack I have been rediff'ing
for some time, but anything that uses mpmath now shows a lot of warnings
like these:
sage -t -force_lib devel/sage/sage/libs/mpmath/ext_main.pyx
*** glibc
Currently, in sage-4.7.2:
sage: integral_numerical(log(x), 0, 0)
(nan, nan)
Mathematically, the integral should certainly be zero: there is a
primitive function which is continuous and defined at 0. Symbolically,
we can compute the integral correctly:
sage: integral(log(x), (x,0,0))
0
So I
On 2011-11-08 19:35, William Stein wrote:
Right now we get a TypeError when trying to evaluate the above, which
is unfortunate too, but at least it's an error rather than a totally
wrong answer. With your patch, probably Sage would silently produce
a wrong answer.
Yes it would always produce
On 2011-11-08 19:35, William Stein wrote:
In this case, dirac_delta is actually a distribution. It
is defined as the distribution with the property that
integral(dirac_delta, a, b)
is 0 if the interval [a,b] does not contain 0, and is 1 if the
interval [a,b] does contain 0.
Not quite,
On 2011-11-09 06:58, Robert Bradshaw wrote:
Any ideas?
Did you set ulimit?
I constantly build/test sage on sage.math.washington.edu and never saw
this. So I guess it is something with your particular setup.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe
Is there a requirement that all Sage .py files should be ASCII or is
UTF8 also accepted?
It seems that Sphinx 1.1.2 (#10620) cares more about this: at #10112
there is a patch with a 0xd0 byte (which is neither ASCII neither UTF8)
which is rejected by Sphinx 1.1.2.
Jeroen.
--
To post to this
I am considering removing the doc dependency from the test targets
(like ptestlong). I am regularly annoyed by the long time it takes to
rebuild the docs when doing make ptestlong. It is true that a few
doctests would fail if no documentation has been built. But if the
documentation has been
On 2011-11-11 21:59, frosty wrote:
Secondly I have downloaded the binary for Linux and have it installed
runnimng: I want to actually compile Sage for my server which is an
AMD 6 core based server with 8Gb of ram running Debian stable. I
tried , but it errored out, error 1 showing a
Right now, there are several parts of the Sage scripts having support
for doing things in parallel:
- Building Sage itself with SAGE_PARALLEL_SPKG_BUILD (which is now the
default)
- Source files in the same spkg
- Sage library (sage -b)
- Doctesting (sage -tp, make ptestlong)
- With #6495,
1 - 100 of 3164 matches
Mail list logo
