On Wed, Jan 20, 2010 at 5:44 PM, François Bissey
wrote:
> I don't remember what the equivalent is for solaris and so on.
See
http://trac.sagemath.org/sage_trac/ticket/7818
http://trac.sagemath.org/sage_trac/attachment/ticket/7818/sage-env
--
Regards
Minh Van Nguyen
--
To post to this group, s
On Wed, 20 Jan 2010 16:21:55 Jonathan Bober wrote:
> The Sage README.txt contains the text:
>
> "On Linux, if you get this error message:
>
> " restore segment prot after reloc: Permission denied "
>
> the problem is probably related to SELinux."
>
> I got this error on a machine on which I
Hi Dmitrii,
On Wed, Jan 20, 2010 at 8:35 AM, Minh Nguyen wrote:
> I have written up some instructions on how to patch an spkg. The
> instructions are provided as an answer to the question, "How do I
> patch an spkg?" in the Development FAQ:
>
> http://wiki.sagemath.org/devel/DevelFAQ
Due to s
On Tue, Jan 19, 2010 at 07:29:33AM -0800, slabbe wrote:
> > Can you try "sage -t -verbose"?
>
> Great. It worked. It was a syntax error in a doctest : a line "...:"
> after a one-liner while.
I've just submitted patches to tickets #7995 and #7993 that (among other
things) change the error given i
On Jan 19, 7:21 pm, Jonathan Bober wrote:
> Should PARI always be compiled with -fPIC? (Should I really be asking
> this question to PARI developers who decided not to use PIC?) I don't
> know much about this, but apparently -fPIC might cause some slowdown on
> some systems. It seems that just abo
Hi,
Somehow all the virtual machines were corrupted due to a surprising
bug in VirtualBox. Fortunately, I made some sort of backup of them
all about 1 week ago.
1. I've restored sagemath from this backup. Unfortunately, there are
problems with some of the other virtual machines in the build far
First - thanks, Jason, for taking this on.
I think the rref approach makes a lot of sense for a change this big,
and will be really useful for educational settings moving away from
calculators (like me this term!). If we then want to replace
instances of echelon_form, it can happen at its own pac
On Tue, 19 Jan 2010 13:54:57 -0800, Robert Miller wrote:
>
> And here are the eight longest -long doctests:
>
> devel/sage-main/sage/rings/arith.py
> 506.284008026
Where was this run? I find it very strange, because #7678 recently
arranged things so that arith.py runs quite a bit faster than i
The Sage README.txt contains the text:
"On Linux, if you get this error message:
" restore segment prot after reloc: Permission denied "
the problem is probably related to SELinux."
I got this error on a machine on which I don't have root access, so I
couldn't try the suggested workarounds.
This is dredging up from the past an issue that will hopefully soon be
resolved. Ticket #3211 recounts the issue. In summary, if M is an
integer matrix, M.echelon_form() (and M.echelonize()) returns the
echelon form over ZZ (i.e., the Hermite form). This is modeled after
Magma, I believe. A
Hi,
There will be at least 4 hours or more of downtime for the wiki's,
sagemath site, etc.
This is because somebody decided to start the sagemath virtualmachine
at the same time as it was already started, thus mounting the disk
twice. Not good.
-- William
--
William Stein
Associate Professor
On Tue, Jan 19, 2010 at 11:53 AM, Robert Miller wrote:
> On Tue, Jan 19, 2010 at 12:28 AM, Robert Miller wrote:
>> Sage-4.3.1.rc1 has been released.
>
> Note on the binaries! The binary posted yesterday was for sage.math
> only! The other three machines have a different version of ubuntu on
> the
On Tue, Jan 19, 2010 at 7:48 AM, Dag Sverre Seljebotn
wrote:
> Dima Pasechnik wrote:
>>
>> is it possible to make patches, instead/as well as posting full source
>> releases?
>> It took 4+ hours here to download rc0...
>>
>
> One thing one could try out is to play with rsync over SSH to an account
Hi all,
attached are the instructions and code to build a
Sage LiveDVD based on Xubuntu 9.10.
Once you uncompress the file you will find a folder with
two files: "README" and "codeToBuildIso" which are
plain text ones.
Follow the instructions and you're done.
Enjoy!
--
To post to this group, s
I am one of them, sorry!
I'll try to look at this went I get some time. I'm teaching a new
course this semester which is taking a lot of prep...
http://www.usna.edu/Users/math/wdj/teach/sm450.html
On Tue, Jan 19, 2010 at 4:54 PM, Robert Miller wrote:
> It's time to point our fingers at long doct
PS - sorry for shouting in the subject :)
On Jan 19, 1:54 pm, Robert Miller wrote:
> It's time to point our fingers at long doctests again.
--
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
It's time to point our fingers at long doctests again. (I won't name
names, but there are a few people who are mostly responsible for
several of these files) Here are the eight files whose doctests
(without -long) take the longest:
devel/sage-main/sage/rings/polynomial/multi_polynomial_ideal.py
35
Hi Dmitrii,
On Wed, Jan 20, 2010 at 1:53 AM, Dima Pasechnik wrote:
> Hi Minh,
> first I need instructions on how to patch a standard package (i.e.
> gap-4.4.10).
I have written up some instructions on how to patch an spkg. The
instructions are provided as an answer to the question, "How do I
pat
2010/1/19 Minh Nguyen :
> Hi John,
>
> On Wed, Jan 20, 2010 at 4:42 AM, John Cremona wrote:
>
>
>
>> And on another 64-bit ubuntu machine, built fine and two failures --
>> the one above and also this:
>>
>> j...@host-57-44%./sage -t devel/sage/sage/interfaces/sage0.py
>
> This failure might be
On Tue, Jan 19, 2010 at 12:28 AM, Robert Miller wrote:
> Sage-4.3.1.rc1 has been released.
I have fixed the tarball so you don't need to change permissions to build:
http://boxen.math.washington.edu/home/rlmill/sage-4.3.1.rc1.tar
You will likely need to apply the patch at #7999 in order for sag
On Jan 19, 7:02 am, John Cremona wrote:
> 4.3.1.rc1 built fine (64-bit ubuntu), one test failure:
>
> sage -t devel/sage/sage/misc/sagedoc.py
> **
> File "/home/jec/sage-4.3.1.rc1/devel/sage-main/sage/misc/sagedoc.py", line
> 36
Dear all,
Both these lists will be interested in the upcoming online Sage PREP
(Professional Enhancement Program), funded by the MAA via NSF
DUE-0817071. See http://www.maa.org/prep/2010/sage.html for more
information; please advertise it to those you might think are
interested.
Our hope is to
2010/1/16 Minh Nguyen :
> Hi folks,
>
> A spammer using the wiki username KristyMontero recently deleted
> everything on the development wiki page [1]. In its place, the spammer
> placed a link to an external site. To see the effect of the spammer's
> work, go to the development wiki page and click
On Tue, 19 Jan 2010 15:02:55 +, John Cremona wrote:
> 4.3.1.rc1 built fine (64-bit ubuntu), one test failure:
>
> sage -t devel/sage/sage/misc/sagedoc.py
> **
> File "/home/jec/sage-4.3.1.rc1/devel/sage-main/sage/misc/sagedo
Hi John,
On Wed, Jan 20, 2010 at 4:42 AM, John Cremona wrote:
> And on another 64-bit ubuntu machine, built fine and two failures --
> the one above and also this:
>
> j...@host-57-44%./sage -t devel/sage/sage/interfaces/sage0.py
This failure might be related to the DOT_SAGE directory. By de
2010/1/19 John Cremona :
> 4.3.1.rc1 built fine (64-bit ubuntu), one test failure:
>
> sage -t devel/sage/sage/misc/sagedoc.py
> **
> File "/home/jec/sage-4.3.1.rc1/devel/sage-main/sage/misc/sagedoc.py", line
> 365:
> sage: 'a
> I'm not a lawyer, nor do I live in the USA,
I'm not a lawyer either, and don't live in the US. I do know a little
bit about copyright, though.
> but at least in the UK, if you
> write something you automatically get copyright, though it does no harm to
> make a specific statement.
Copyright ex
Hi John,
On Wed, Jan 20, 2010 at 3:25 AM, John Cremona wrote:
> 2010/1/19 John Cremona :
>> That's funny, I can run my 4.3.1.rc1 built from source with no problem.
> Someone else had better review this since I don't get the error
On first loading the pre-compiled binary for Sage 4.3.1.rc1
Hi David,
On Sun, Jan 17, 2010 at 12:24 AM, Dr. David Kirkby
wrote:
> Is this really necessary?
I don't know.
> Is it updated because you believe it is legally necessary to do so, or
> because it looks better?
I think it looks better. I'm following what the Python folks do with
their stand
2010/1/19 John Cremona :
> That's funny, I can run my 4.3.1.rc1 built from source with no problem.
>
> On that accent, I would have just deleted the accent. There are two
> other reference to that journal:
>
> sage: search_src("Ast")
> schemes/elliptic_curves/ell_rational_field.py:5447:
That's funny, I can run my 4.3.1.rc1 built from source with no problem.
On that accent, I would have just deleted the accent. There are two
other reference to that journal:
sage: search_src("Ast")
schemes/elliptic_curves/ell_rational_field.py:5447: modular
forms. Astérisque, (295):ix,
Hi folks,
I built Sage 4.3.1.rc1 from source and then produced a sage.math
binary (you can find it at [1]). Loading the binary resulted in the
following SyntaxError:
SyntaxError: Non-ASCII character '\xc3' in file
/dev/shm/mvngu/sage-4.3.1.rc1-dev/local/lib/python2.6/site-packages/sage/schemes/el
> Can you try "sage -t -verbose"?
Great. It worked. It was a syntax error in a doctest : a line "...:"
after a one-liner while.
Thanks to both of you for the quick answer.
Sébastien
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send a
4.3.1.rc1 built fine (64-bit ubuntu), one test failure:
sage -t devel/sage/sage/misc/sagedoc.py
**
File "/home/jec/sage-4.3.1.rc1/devel/sage-main/sage/misc/sagedoc.py", line 365:
sage: 'abvar/homology' in _search_src_or_doc('
Hi Minh,
first I need instructions on how to patch a standard package (i.e.
gap-4.4.10).
Say, I have made gap-blah.spkg and I want to replace the standard
package with it.
When I read the development guide I only see that I should post by gap-
blah.spkg somewhere
and let people test it. That's not
Dear all,
The latex representation of variables is great, thanks to those that
implemented it. I just noted one point that I think could be made more
consistent. If a greek letter name is followed by a number, the greek
letter is detected and the number is automatically typeset as a
subscript (gre
Dr David Kirkby wrote:
From what I have read of the GNU linker documentation on the linker
'ld'
http://sourceware.org/binutils/docs-2.20/ld/Options.html#Options
there is no such flag as -m64. So I can't understand how it works.
(There is an opton -64 on the Sun linker, but it rarely needed).
On Tue, Jan 19, 2010 at 05:41:18AM -0800, slabbe wrote:
> Dear sage-devel,
>
> Sometimes, I get the following :
>
> $ sage -t myfile.py
> A mysterious error (perhaps a memory error?) occurred, which may have
> crashed doctest.
>[1.7 s]
> exit code: 768
>
> How should I debug this? Should
Hi Sébastien,
On Wed, Jan 20, 2010 at 12:41 AM, slabbe wrote:
> How should I debug this? Should I use valgrind?
If you're going the Valgrind route, note that the optional Valgrind
spkg was recently upgraded to version 3.5.0. See ticket #7440 [1]. You
can grab the updated Valgrind spkg [2] fro
Dear sage-devel,
Sometimes, I get the following :
$ sage -t myfile.py
A mysterious error (perhaps a memory error?) occurred, which may have
crashed doctest.
[1.7 s]
exit code: 768
How should I debug this? Should I use valgrind? Would it be possible
for "sage -t" to give more information
On Tue, Jan 19, 2010 at 4:29 AM, Robert Miller wrote:
> On Tue, Jan 19, 2010 at 2:49 AM, William Stein wrote:
>> We have a standard system for doing upgrades from say rc0 to rc1, etc,
>> which we usually use in such cases.
>> However, Robert Miller was *super tired* and didn't have time to set
>>
On Tue, Jan 19, 2010 at 2:49 AM, William Stein wrote:
> We have a standard system for doing upgrades from say rc0 to rc1, etc,
> which we usually use in such cases.
> However, Robert Miller was *super tired* and didn't have time to set
> that up in this case and post a link.
The main reason was t
On Jan 19, 8:51 am, Dr David Kirkby wrote:
> With the exception of a bug in the Solaris implementation of 'memset'
> on 't2', which has now been patched with a patch from Sun, I've never
> observed any differece between the behavious on 't2' and my own
> machine.
Other than my own SPARC (Sun B
On Jan 19, 1:50 am, William Stein wrote:
> On Mon, Jan 18, 2010 at 4:15 PM, Dr. David Kirkby
> > I should have made it clearer, that it will need to be:
>
> > CFLAGS=$SAGE_COMMON_CFLAGS
> > CXXFLAGS=$SAGE_COMMON_CXXFLAGS
> > FCFLAGS=$SAGE_COMMON_FCFLAGS
>
> > since the options may be different fo
On Tue, Jan 19, 2010 at 2:59 AM, Dima Pasechnik wrote:
> hmm, is running
> diff -r DIR1 DIR2 >patch1
> and putting patch1 up for download so hard to do?
>
> Surely, a better way might be having the whole thing under a revision
> control system allowing
> (semi)anonymous pulls, than pulling an up
hmm, is running
diff -r DIR1 DIR2 >patch1
and putting patch1 up for download so hard to do?
Surely, a better way might be having the whole thing under a revision
control system allowing
(semi)anonymous pulls, than pulling an upgrade is trivial...
(well, I would be mighty surpised learning Sage
On Tue, Jan 19, 2010 at 12:05 AM, Fernando Perez
wrote:
> Hi William,
>
> On Mon, Jan 18, 2010 at 11:52 PM, William Stein wrote:
>>
>> SO, now I think this is a bug in *IPython*, not the sage notebook.
>> What do you think?
>
> It's by design: one of the few places where early on, I explicitly an
On Tue, Jan 19, 2010 at 1:48 AM, Dag Sverre Seljebotn
wrote:
> Dima Pasechnik wrote:
>>
>> is it possible to make patches, instead/as well as posting full source
>> releases?
>> It took 4+ hours here to download rc0...
>>
We have a standard system for doing upgrades from say rc0 to rc1, etc,
whic
2010/1/19 William Stein :
> On Tue, Jan 19, 2010 at 1:16 AM, John Cremona wrote:
>> If someone is looking into that please say so on the ticket, otherwise
>> I'll look at it today (GMT).
>
> John -- go for it; none of us are doing it!
OK. I just did #7992 too.
John
>
>>
>> John
>>
>> 2010/1/19
Dima Pasechnik wrote:
is it possible to make patches, instead/as well as posting full source
releases?
It took 4+ hours here to download rc0...
One thing one could try out is to play with rsync over SSH to an account
on boxen.math. rsync the rc1 file with a local copy of the rc0 tarball,
and
On Tue, Jan 19, 2010 at 1:16 AM, John Cremona wrote:
> If someone is looking into that please say so on the ticket, otherwise
> I'll look at it today (GMT).
John -- go for it; none of us are doing it!
>
> John
>
> 2010/1/19 William Stein :
>> On Mon, Jan 18, 2010 at 4:59 PM, John H Palmieri
>>
If someone is looking into that please say so on the ticket, otherwise
I'll look at it today (GMT).
John
2010/1/19 William Stein :
> On Mon, Jan 18, 2010 at 4:59 PM, John H Palmieri
> wrote:
>> Ticket #7532 deals with this issue: in ring.pyx, code says "return
>> NotImplementedError" where it s
is it possible to make patches, instead/as well as posting full source
releases?
It took 4+ hours here to download rc0...
On Jan 19, 4:29 pm, Robert Miller wrote:
> >http://boxen.math.washington.edu/home/rlmill/sage-4.3.1.rc1.tar
>
> Oops:http://boxen.math.washington.edu/home/rlmill/release/sage-
On Jan 19, 5:39 am, Craig Citro wrote:
> So the error seems to be coming from this command:
>
> > building 'sage.schemes.elliptic_curves.descent_two_isogeny' extension
> > /usr/local/gcc-4.4.1-sun-linker/bin/gcc -fno-strict-aliasing -DNDEBUG -g -O3
> > -Wall -Wstrict-prototypes -fPIC
> > -I/expo
On Tue, Jan 19, 2010 at 12:29 AM, Robert Miller wrote:
>> http://boxen.math.washington.edu/home/rlmill/sage-4.3.1.rc1.tar
>
> Oops: http://boxen.math.washington.edu/home/rlmill/release/sage-4.3.1.rc1.tar
>
Also, note that you *must* do
chmod +x spkg/install
make test
because we forgot t
> http://boxen.math.washington.edu/home/rlmill/sage-4.3.1.rc1.tar
Oops: http://boxen.math.washington.edu/home/rlmill/release/sage-4.3.1.rc1.tar
--
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...@googlegr
Hello all,
Sage-4.3.1.rc1 has been released (buyer beware! *). The source is here:
http://boxen.math.washington.edu/home/rlmill/sage-4.3.1.rc1.tar
Due to hardware issues, this is a source only release (at least for tonight).
After an intensive day of merging, Sage now has:
- OS X 10.6 support
On Jan 18, 11:27 pm, Burcin Erocal wrote:
> I'm not familiar with the maxima interface, but the comment by Robert
> Dodier reproduced here
>
> http://trac.sagemath.org/sage_trac/ticket/7507
>
> seems to suggest we need to call remove() in some cases.
Thanks! very relevant indeed. That just means
58 matches
Mail list logo
