You're right ! It doesn't work with the view() function. On the other
hand, when I select latex instead of sage and I enter the command
\sage{A()}
it displays 123 on the first line and 23 on the second line, with the
2's aligned properly, i.e. it handles the newlines and indentation as
desired. T
On it.
--
Robert L. Miller
http://www.rlmiller.org/
--
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
UR
The issue is that we have two vertex-transitive graphs on 156 vertices, coming
from two constructions of a generalized quadrangle over GF(5).
According to sage these graphs are not isomorphic, but the graphs
we obtain by deleting one vertex from each are isomorphic. One of
these claims has to be f
On 05/24/10 05:26 PM, leif wrote:
On 24 Mai, 14:45, Matthew Gwynne wrote:
When building Sage 4.4.1, I (and also my colleague) get the following
errors during the build process -
/bin/sh ./libtool --tag=CXX --mode=link g++ -fPIC -I/home/csoliver/
SAT-Algorithmen/OKplatform/ExternalSources/Inst
On 05/23/10 11:05 PM, leif wrote:
Strange anyway, what does "gcc -v -Q -march=native foo.c" report?
If you do have some ideas, perhaps you can post them on the trac ticket.
Certainly.
-Leif
Perhaps more useful would be the output of gcc when the -m64 option is added,
which is what is be
On 05/23/10 11:05 PM, leif wrote:
On 23 Mai, 22:47, "Dr. David Kirkby" wrote:
Host system
uname -a:
SunOS hawk 5.11 snv_134 i86pc i386 i86pc
uname -m == i386 is bad for a 64-bit machine...
uname -m does not give i386.
drkir...@hawk:~/sage-4.4.2$ uname -m
i86pc
drkir...@hawk:~/sage-4.4.2$
> I don't have time to fix this myself, but I am talking to a researcher
> who decided to use Magma instead of Sage because the fact that Sage
> supports multiple edges in DiGraphs was not very well advertised in
> the documentation. I think that the graph theory module should have an
> entire sect
Those of you that are enjoying zapping bugs right now at Sage Days (and
everyone else too) might enjoy watching it via gource:
It's in macports and in ubuntu lucid (might be in earlier versions of
ubuntu too):
http://code.google.com/p/gource/
See
http://manpages.ubuntu.com/manpages/lucid/ma
Hello,
I don't have time to fix this myself, but I am talking to a researcher
who decided to use Magma instead of Sage because the fact that Sage
supports multiple edges in DiGraphs was not very well advertised in
the documentation. I think that the graph theory module should have an
entire sectio
On May 24, 2:17 pm, ablondin
wrote:
> What about using the verbatim environment of Latex ?
>
> class A(SageObject):
>
> def _latex_(self):
> from sage.misc.latex import LatexExpr
> return '\\begin{verbatim}\n123\n 23\n\\end{verbatim}'
>
> sage: attach latex.sage
> sage: latex(A
Hi there,
On Fri, May 21, 2010 at 03:24:47AM -0700, Alasdair wrote:
> Since the current Sage implementation of derangements is a wrapper for
> a GAP function, and doesn't always work as you'd like, I've bunged the
> first draft of a more complete native implementation of derangements
> up as
What about using the verbatim environment of Latex ?
class A(SageObject):
def _latex_(self):
from sage.misc.latex import LatexExpr
return '\\begin{verbatim}\n123\n 23\n\\end{verbatim}'
sage: attach latex.sage
sage: latex(A())
\begin{verbatim}
123
23
\end{verbatim}
In the n
I don't think that is something we can cover on the MPIR website.
You might consider "Windows support", "FSF copyright assignment" and
other issues It should just be clear that GMP won't, by and large,
just accept our contributions. You might also consider that numerous
individuals *did* try t
Just a quick clarification. I wrote:
"As far as I know, the library itself was correctly licensed though."
Obviously, given the foregoing, that isn't what I meant to say.
This is to be taken in the context of the parenthetical remark in the
following statement from the GMP website:
"a renamed GM
On 24 Mai, 20:13, Bill Hart wrote:
> OK, I made a little bit of a change to the "about" section of the MPIR
> website. It now has:
>
> "MPIR is an open source multiprecision integer (bignum) library forked
> from the http://gmplib.org/";>GMP (GNU Multi Precision)
> project. It consists of much cod
OK, I made a little bit of a change to the "about" section of the MPIR
website. It now has:
"MPIR is an open source multiprecision integer (bignum) library forked
from the http://gmplib.org/";>GMP (GNU Multi Precision)
project. It consists of much code from past GMP releases, in
combination with m
Interesting observation. Do you think we should state the original
reasons for the fork? Bear in mind, some of these reasons are no
longer valid, e.g. GMP now has an open repository.
We also aren't releasing new versions under LGPL 2.1+ ourselves any
more. After extensive consultation we decided t
On 24 May 2010 17:05, Bill Hart wrote:
> Please note that version of flintqs if really 2007, is ancient, and
> that recent FLINT 1.5 contains a much faster, up-to-date sieve.
>
> I don't mind if the latter is used or not. Just thought it worth
> mentioning.
>
> Bill.
Thanks Bill.
I'll leave some
I just made a check of past GMP tarballs regarding this Title Page issue.
Right up to GMP 4.3.0 the document license was GFDL 1.2. By GMP 4.3.0
@author{The GMP Developers} had been added (I didn't bother checking
the precise version this got added). Nothing wrong with either no
author or lack of s
On 24 Mai, 16:27, Jan Groenewald wrote:
> Sage 4.4.2 compiles cleanly on 64bit ubuntu 9.04.
I got errors after the "real" build (documentation doesn't build
because of import errors/"NotImplemented" exceptions), see
http://groups.google.com/group/sage-release/msg/465971b29eff27c3.
After 4 fresh
On 24 Mai, 15:59, Bill Hart wrote:
> [...]
> I *apologise unreservedly* for upsetting the GMP
> developers. This flame war, whether well-intentioned or not, is much
> to be regretted. It would have been better to simply state we forked
> because we wished to support Windows development, have an op
On 24 Mai, 14:45, Matthew Gwynne wrote:
> When building Sage 4.4.1, I (and also my colleague) get the following
> errors during the build process -
>
> /bin/sh ./libtool --tag=CXX --mode=link g++ -fPIC -I/home/csoliver/
> SAT-Algorithmen/OKplatform/ExternalSources/Installations/Sage/
> sage-4.4.1
Please note that version of flintqs if really 2007, is ancient, and
that recent FLINT 1.5 contains a much faster, up-to-date sieve.
I don't mind if the latter is used or not. Just thought it worth
mentioning.
Bill.
On 24 May, 14:38, David Kirkby wrote:
> On 24 May 2010 13:09, Minh Nguyen wrote
On 24 Mai, 14:26, geep999 wrote:
> make ptestlong
> All tests passed!
> Total time for all tests: 4762.2 seconds
> (=79.37 minutes with Linux 2.6.29.6 SMP x86_64 Intel(R)
> Core(TM)2 Duo CPU E6550 @ 2.33GHz GenuineIntel GNU/Linux )
Thanks!
-Leif
--
To post to this group, send an email to sage-
Hi
Sage 4.4.2 compiles cleanly on 64bit ubuntu 9.04.
On 10.04 32bit, and only 512M RAM, an older laptop, I
get:
The following tests failed:
sage -t "devel/sage/sage/rings/polynomial/symmetric_ideal.py" # File
not found
sage -t
"devel/sage/sage/schemes/hyperelliptic_curves/
Hi All,
On the GMP website we find that MPIR "have also removed the author
name from our 140 page manual".
Roughly speaking, whilst not strictly correct as written (we haven't
"removed" anything), my reading of the license suggests there *is* an
issue that needs to be sorted out here. As of MPIR
Could you be more specific?
Otherwise, you can look at some working examples: the graph editor uses
processing for sure, and the javascript viewer for 3d plots might also
use it.
There were some messages in this list last month about a javascript
matrix editor, but I don't know if it uses processi
On 24 May 2010 13:09, Minh Nguyen wrote:
> Hi David,
>
> On Mon, May 24, 2010 at 10:06 PM, David Kirkby
> wrote:
>> Does anyone know whether the files in the 'dist' directory should be
>> checked in, removed, or whatever else from the 'flintqs-20070817.p4'
>> package?
>
> The directory dist/ of
Dear all,
currently I work on the doctest coverage of sage.categories.map and
sage.categories.morphism.
It seems to me that the class sage.categories.morphism.Morphism is
completely redundant.
In fact, the definition of a map (sage.categories.map.Map) requires
that the map belongs to a homset (t
On May 24, 9:11 am, kcrisman wrote:
> Dear Matthew,
>
> Thanks for your report. I know I can't answer your question fully :)
> but I can say that the most likely way to receive more specific info
> is to also post your OS, chip type if known, and any other info.
>
> One reason I say this might
Dear Matthew,
Thanks for your report. I know I can't answer your question fully :)
but I can say that the most likely way to receive more specific info
is to also post your OS, chip type if known, and any other info.
One reason I say this might be relevant is the following I found doing
a quick
Hi,
When building Sage 4.4.1, I (and also my colleague) get the following
errors during the build process -
/bin/sh ./libtool --tag=CXX --mode=link g++ -fPIC -I/home/csoliver/
SAT-Algorithmen/OKplatform/ExternalSources/Installations/Sage/
sage-4.4.1/local/include/ -L/home/csoliver/SAT-Algorithme
On May 23, 5:22 pm, leif wrote:
>
> If you find the time, you could try running "./sage -testall", "./sage
> -testall -long" or e.g. "make testlong"/"make ptestlong" (the latter
> runs tests in parallel).
> (The "standard" tests shouldn't take much more than an hour, with
> "long" tests enabled, p
Hi David,
On Mon, May 24, 2010 at 10:06 PM, David Kirkby wrote:
> Does anyone know whether the files in the 'dist' directory should be
> checked in, removed, or whatever else from the 'flintqs-20070817.p4'
> package?
The directory dist/ of all spkg's should be removed. Ticket #5903
http://trac.
Does anyone know whether the files in the 'dist' directory should be
checked in, removed, or whatever else from the 'flintqs-20070817.p4'
package?
drkir...@hawk:~/sage-4.4.2/spkg/standard/flintqs-20070817.p4$ hg status
? ._.hg
? ._.hgignore
? ._SPKG.txt
? ._dist
? ._patches
? ._spkg-install
? ._sr
Hello people,
I've created a new function to solve systems of ODEs, and I think it's
ready for review. I'd be grateful if somebody would take a look at it
and gave some feedback!
Here's the trac page:
http://trac.sagemath.org/sage_trac/ticket/8950
Thank you a lot!!
Uri
--
To post to this group
On Mon, May 24, 2010 at 12:12 AM, Dr. David Kirkby
wrote:
> On 05/24/10 02:45 AM, William A. Stein wrote:
>>
>> On May 23, 2010, at 6:10 PM, Dr. David Kirkby wrote:
>>
>>> Trying to build Sage on OpenSolaris in 64-bit mode I discovered two
>>> packages which look to me that they don't try to build
On 05/24/10 02:45 AM, William A. Stein wrote:
On May 23, 2010, at 6:10 PM, Dr. David Kirkby wrote:
Trying to build Sage on OpenSolaris in 64-bit mode I discovered two packages
which look to me that they don't try to build 64-bit. They don't use the SAGE64
variable at all and nothing else the
38 matches
Mail list logo
