On 1/15/11 9:45 AM, Vincent Delecroix wrote:
Due to conflict with trac_8898 the combinat queue is currently
broken... wait few minutes before pull and push.
This conflict is resolved and should work on sage-4.6.1. But
application de trac_9065-facade_parents-nt.patch
patching file
The four patches below do not apply on 4_6_1, so I decided to
temporarily to guard them with a +4_6_1
* trac_10333-lrcalc-mh.patch
* coxeter3-mh.patch
* coxeter3-iterator.patch
* trac_8360_semigroupe-interface-nt.patch
It will be push in few minutes
Vincent
--
You received this
Hi John,
Isn't a .rst file considered as a big docstring by the tester ?
No.
Before the second code block, you need a link directive to tell it
that it should be connected with the previous block. See
http://sagemath.org/doc/developer/conventions.html#testing-rest-
Hi John,
Before the second code block, you need a link directive to tell it
that it should be connected with the previous block. See
http://sagemath.org/doc/developer/conventions.html#testing-rest-
documentation
for documentation. For an example, see the file interfaces.rst in
Sage Version 4.6, Release Date: 2010-10-30
openSUSE 11.3 (x86_64)
g++ (SUSE Linux) 4.5.0 20100604 [gcc-4_5-branch revision 160292]
On Dec 8 2010, 8:55 pm, Dima Pasechnik dimp...@gmail.com wrote:
please report Sage version, OS version, compiler version...
On Dec 9, 2:48
Another remark:
Examples of code::
sage: el = 1
sage: el
1
Some explanations:
.. link
::
sage: el
1
(Note the double colon after .. link, so only a single colon after
Some explanations.)
In conventions.html#testing-rest-documentation you write
It doesn't work with sage-4.6.2.alpha0 either: gsl fails to build.
The other install.log is at
http://sage.math.washington.edu/home/SimonKing/logs/install.alpha0.log
Best regards,
Simon
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group,
On Jan 15, 11:51 pm, Emil Widmann emil.widm...@gmail.com wrote:
Stripping Sage Binaries II
--
With hardlinking multible files and stripping executables a size
reduction of 438 MB (-26%) was achieved. Further reduction involves
moving directories which breaks sage
On Jan 15, 8:34 pm, Rob Beezer goo...@beezer.cotse.net wrote:
On Jan 15, 9:23 am, Jeroen Demeyer jdeme...@cage.ugent.be wrote:
Whether every range() should be changed to xrange(): I can't comment on
that.
In Python 3, range() will return an iterator, which is the current
behavior of
(Sorry somehow I managed to send incomplete message)
I always have to laugh when I do, say or write something silly, but at
least it's a good learning experience. But at least now I beginn to
grasp what docstrings are and how they work. I also check the sage -t
command.
I used
sage -t
On Jan 16, 11:54 am, koffie m.derickx.stud...@gmail.com wrote:
To bad nobody still noticed suggestion number 2
2. Could we maybe add some sort of check for common bad practice to
the doctest or coverage framework, I think something like pylint with
some sage specific plugins could be very
It doesn't even work to build sage-4.6.1 from source!
What is going wrong? Do you have any hint for me by reading the
install.log that I posted? What can I ask the administrator to
install? Unfortunately, I am not root on that computer.
Best regards,
Simon
--
To post to this group, send an
On Sunday 16 January 2011, Simon King wrote:
It doesn't even work to build sage-4.6.1 from source!
What is going wrong? Do you have any hint for me by reading the
install.log that I posted? What can I ask the administrator to
install? Unfortunately, I am not root on that computer.
Summary:
Hi Martin!
On 16 Jan., 15:48, Martin Albrecht martinralbre...@googlemail.com
wrote:
Summary: building gsl fails because ar (which packages .o files together to
produce static libraries) cannot find lt1-init.o in the build directory. Does
this file exist in your build directory somewhere?
ar:
PS:
On 16 Jan., 16:09, Simon King simon.k...@uni-jena.de wrote:
..
It is at
./local/king/SAGE/sage-4.6.1/spkg/build/gsl-1.14/src/.libs/libgsl.lax/
lt1-init.o
And I should add: I issued the make command when I was in ./local/
king/SAGE/sage-4.6.1/
I went a few directories up before searching
On Sunday 16 January 2011, Simon King wrote:
Hi Martin!
On 16 Jan., 15:48, Martin Albrecht martinralbre...@googlemail.com
wrote:
Summary: building gsl fails because ar (which packages .o files together
to produce static libraries) cannot find lt1-init.o in the build
directory. Does
One more puzzle:
$ ls -l /mnt/local/king/SAGE/sage-4.6.1/spkg/build/gsl-1.14/src/.libs/
libgsl.lax/lt1-init.o
lrwxrwxrwx 1 king malg 36 16. Jan 16:17 /mnt/local/king/SAGE/
sage-4.6.1/spkg/build/gsl-1.14/src/.libs/libgsl.lax/lt1-init.o -
.libs/libgsl.lax/libgslcheb.a/init.o
$ less
I see: lt1-init.o is just a pointer to .libs/libgsl.lax/libgslcheb.a/
init.o
Here are all init.o that I found:
./spkg/build/gsl-1.14/src/block/init.o
./spkg/build/gsl-1.14/src/block/.libs/init.o
./spkg/build/gsl-1.14/src/permutation/init.o
./spkg/build/gsl-1.14/src/permutation/.libs/init.o
Hi Martin,
On 16 Jan., 16:18, Martin Albrecht martinralbre...@googlemail.com
wrote:
What happens if you type 'make' in
/local/king/SAGE/sage-4.6.1/spkg/build/gsl-1.14/src
king@mpc622:/mnt/local/king/SAGE/sage-4.6.1/spkg/build/gsl-1.14$ make
make: *** Keine Targets angegeben und keine
On Jan 16, 1:14 am, Florent Hivert florent.hiv...@univ-rouen.fr
wrote:
Hi John,
It seems that doesn't work inside a note environement:
I guess it doesn't interact well with other environments? As far as I
know, the .. link directive is a Sage add-on, dealt with in
Ticket #1975 (see http://trac.sagemath.org/sage_trac/ticket/1975) is
related: you can at least construct a curve over Z/NZ and do
arithmetic with points on it. But the point-counting routines only
work for curves defined over finite fields.
So, it would be useful to do computations on an
Automated testing aside, I wholeheartedly support the idea of
cleaning up our code so that when we inevitably move to Python 3.x
the transition will be as painless as possible. In some cases these
changes may even have performance benefits, like converting range() to
xrange() in loops. By the way,
On Jan 14, 7:07 pm, rjf fate...@gmail.com wrote:
For a discussion of practical fast polynomial multiplication,
seehttp://www.eecs.berkeley.edu/~fateman/papers/dumbisfast.pdf
and also the first reference in that paper.
(As well as other references).
The code in GMP is likely to be well
I get the following messages while trying to access tickets...
Notification codes: (1, INTERNAL_ERROR,
http://trac.sagemath.org/sage_trac/ticket/6391)
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
thanks for your help. I see that arithmetic is possible with a
composite N on an elliptic curve.
My inital question focused on the ECPP (Goldwasser-Kilian) algorithm
which uses the cardinality() command. In case of ECPP/GoldwasserKilian
(but not in the case of ECM...), any code in sage that uses
Hi!
My frustration grows: The same problem occurs even with sage-4.6
sources. Since previously a sage upgrade failed, the computer in my
office is now sageless.
To summarize it:
* When make fails, it is in SAGE_ROOT/spkg/build/gsl-1.14/src
* It complains the .libs/libgsl.lax/lt1-init.o does
On Sun, Jan 16, 2011 at 01:33:43PM -0800, Simon King wrote:
Hi!
My frustration grows: The same problem occurs even with sage-4.6
sources. Since previously a sage upgrade failed, the computer in my
office is now sageless.
To summarize it:
* When make fails, it is in
Hello All,
Given two number fields, say L and K, I would like to be able to
define the field $L \cap K$, i.e. the intersection of L and K.
There currently does not appear to be any way of doing this in Sage
(though if there is I would love to hear about it).
Thanks,
Ben Linowitz
--
To post to
[I am cc-ing sage-nt.]
Without extra infromation, such as an embedding of each field into C,
surely the intersection is not well-defined?
John
On 16 January 2011 22:49, Ben Linowitz benjamin.linow...@gmail.com wrote:
Hello All,
Given two number fields, say L and K, I would like to be able to
Sorry about that. I was thinking of the number fields as being
subfields of C by definition. What if each of the number fields came
with a specified embedding into C?
Ben
On Jan 16, 5:55 pm, John Cremona john.crem...@gmail.com wrote:
[I am cc-ing sage-nt.]
Without extra infromation, such as
Hi Willem Jan,
On 16 Jan., 23:05, Willem Jan Palenstijn w...@usecode.org wrote:
* When make fails, it is in SAGE_ROOT/spkg/build/gsl-1.14/src
* It complains the .libs/libgsl.lax/lt1-init.o does not exist.
* spkg/build/gsl-1.14/src *does* exist, namely it is a link to .libs/
On Jan 17, 12:16 am, Ben Linowitz benjamin.linow...@gmail.com wrote:
Sorry about that. I was thinking of the number fields as being
subfields of C by definition. What if each of the number fields came
with a specified embedding into C?
Ben
I am not sure for the case of embeddings into C, I
Announcement:
--
The FLINT development team is pleased to announce the release of
FLINT 2.0. (see http://www.flintlib.org/ )
FLINT 2 is a complete rewrite of FLINT (Fast Library for Number
Theory) from scratch! The main benefits of the rewrite are:
* Much tidier code
*
On Sun, Jan 16, 2011 at 12:15 PM, Dima Pasechnik dimp...@gmail.com wrote:
I get the following messages while trying to access tickets..
Notification codes: (1, INTERNAL_ERROR,
http://trac.sagemath.org/sage_trac/ticket/6391)
It works fine for me now. Apache seemed generally funny earlier
ok, it works now for me.
On Jan 17, 11:42 am, William Stein wst...@gmail.com wrote:
On Sun, Jan 16, 2011 at 12:15 PM, Dima Pasechnik dimp...@gmail.com wrote:
I get the following messages while trying to access tickets..
Notification codes: (1,
while attempting to upload a patch on #6391, I get
(http://trac.sagemath.org/sage_trac/attachment/ticket/6391/?
action=newattachfilebutton=Attach+file)
(using Safari on OSX 10.6.6)
Traceback (most recent call last):
File /usr/lib/python2.5/site-packages/Trac-0.11.5-py2.5.egg/trac/
web/api.py,
Hi Willem Jan,
On 17 Jan., 00:48, Simon King simon.k...@uni-jena.de wrote:
Hi Willem Jan,
On 16 Jan., 23:05, Willem Jan Palenstijn w...@usecode.org wrote:
The syntax for making hardlinks in subdirs is different than that for
making symlinks in subdirs. Do you maybe have 'ln' aliased to 'ln
Congratulations, this looks really good.
--
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
URL:
38 matches
Mail list logo