[sage-devel] Gamma(N)
The following contradicts the specification of reduce_cusp for Gamma(7). https://doc.sagemath.org/html/en/reference/arithgroup/sage/modular/arithgroup/congroup_gamma.html sage: Gamma(7).are_equivalent(Cusp(6,7),Cusp(1,0)) True sage: Gamma(7).reduce_cusp(Cusp(1,0)) Infinity sage: Gamma(7).reduce_cusp(Cusp(6,7)) 6/7 Ralf -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/ebffabc9-b0c8-656e-aab5-e769057dfe18%40gmail.com.
[sage-devel] modular form basis
Hello, is there any particular reason why the term 12/5*q is not subtracted away by the first basis element? Ralf ┌┐ │ SageMath version 9.6, Release Date: 2022-05-15 │ │ Using Python 3.10.6. Type "help()" for help. │ └┘ sage: ModularForms(Gamma0(11), 2, prec=20).basis() [ q - 2*q^2 - q^3 + 2*q^4 + q^5 + 2*q^6 - 2*q^7 - 2*q^9 - 2*q^10 + q^11 - 2*q^12 + 4*q^13 + 4*q^14 - q^15 - 4*q^16 - 2*q^17 + 4*q^18 + O(q^20), 1 + 12/5*q + 36/5*q^2 + 48/5*q^3 + 84/5*q^4 + 72/5*q^5 + 144/5*q^6 + 96/5*q^7 + 36*q^8 + 156/5*q^9 + 216/5*q^10 + 12/5*q^11 + 336/5*q^12 + 168/5*q^13 + 288/5*q^14 + 288/5*q^15 + 372/5*q^16 + 216/5*q^17 + 468/5*q^18 + 48*q^19 + O(q^20) ] -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/64337a19-6c75-a78d-2579-1c06c771754b%40hemmecke.org.
[sage-devel] boolean value of inequality
Am I doing something wrong? I would have expected the last line to return False. ┌┐ │ SageMath version 9.6, Release Date: 2022-05-15 │ │ Using Python 3.10.4. Type "help()" for help. │ └┘ sage: hr=(x^2+2*x+1) sage: hl=(x+1)^2 sage: bool(hl==hr) True sage: bool(hl!=hr) True -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/c785ac0f-a58b-305e-136d-e592a7f3a298%40gmail.com.
[sage-devel] problem with paralell build
I seem to have a problem with building sage 9.4 via. MAKE='make -j12' make -j12 It stops during the build of dochtml. Obviously because of too many open files. I'm now trying without "-j12" and it seems to be building nicely. Anyhow... any suggestion what to change to prevent my problem and still be able to build in parallel? Thanks Ralf [dochtml] File "", line 987, in get_code [dochtml] OSError: [Errno 24] Too many open files: '/zvol/sage/sage-9.4/x86_64/local/lib/python3.9/site-packages/sage/doctest/__init__.py' [dochtml] File "", line 1044, in get_data [dochtml] OSError: [Errno 24] Too many open files: '/zvol/sage/sage-9.4/x86_64/local/lib/python3.9/site-packages/sage/rings/finite_rings/all.py' [dochtml] make[5]: *** [Makefile:20: doc-inventory--reference-algebras] Error 1 [dochtml] make[5]: *** Waiting for unfinished jobs [dochtml] make[5]: *** [Makefile:20: doc-inventory--reference-polynomial_rings] Error 1 >ulimit -a real-time non-blocking time (microseconds, -R) unlimited core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 31256 max locked memory (kbytes, -l) 1009691 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 31256 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/14616aec-24cd-3411-a18c-c30a2c8fce1f%40gmail.com.
Re: [sage-devel] sage -i fricas broken ?
https://sourceforge.net/projects/fricas/files/fricas/1.3.6/ On 10/1/20 9:28 PM, Frédéric Chapoton wrote: > Hello, > it seems that "sage -i fricas" is currently not working. > Maybe the tarball is missing on the mirrors, > or maybe the tarball name is wrong ? > Frédéric > > [fricas-1.3.6] FileNotMirroredError: tarball does not exist on mirror > network > [fricas-1.3.6] > > [fricas-1.3.6] > > [fricas-1.3.6] Error downloading fricas-1.3.6-full.tar.bz2 > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/23e12641-86f3-2692-7d6c-7eee4c559dfa%40gmail.com.
[sage-devel] groebner walk
Hello,
on
http://doc.sagemath.org/html/en/reference/polynomial_rings/sage/rings/polynomial/multi_polynomial_ideal.html
is an examle, how to use Gröbner walk.
sage: R.=PolynomialRing(GF(32003),3,order='lex')
sage: I=Ideal([y^3+x*y*z+y^2*z+x*z^3,3+x*y+x^2*y+y^2*z])
sage: I.transformed_basis('gwalk')
However, it says that the other_ring argument is only valid for fglm.
Thus, gwalk will always return a lex GB. :-(
That's not something I need. Can I call gwalk with another target
ordering than lex? How?
Why is there such a restriction built into the singular wrapper in the
first place? According to the Singular documentation, gwalk allows
different target term orders.
Thank you
Ralf
--
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 group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: SAGE_PATH and PYTHONPATH
On 09/09/2017 05:05 PM, Maarten Derickx wrote: > In case people start setting pythonpath after reading this thread: > you will actually get some silly doctest failures if python path is > set. I don't need to set SAGE_PATH (or PYTHONPATH) for testing Sage. All I want is to tell Sage about a locally installed package that does not come from "sage -i". As I understand what Nils was saying is that instead of SAGE_PATH I should simply switch to PYTHONPATH directly. That would be OK for me. However, it's quite bad that the commit that removed SAGE_PATH did not also consider to change the documentation for Sage 8.0. It still says that SAGE_PATH is in use. http://doc.sagemath.org/html/en/reference/repl/environ.html But it should actually explain what to do when a user wants to tell Sage about some additional code. Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] SAGE_PATH and PYTHONPATH
Since my settings using SAGE_PATH do seemingly not work anymore, I looked for the use of SAGE_PATH in the sources. I found in 7.6 some code if [ -n "$SAGE_PATH" ]; then PYTHONPATH="$SAGE_PATH:$PYTHONPATH" fi but that was removed in commit 22e470c2d6941875908f35ff3657843f1fe83f21 So it looks like SAGE_PATH is not used in 8.0 anymore although the documentation still suggests its use. http://doc.sagemath.org/html/en/reference/repl/environ.html What exactly is the situation? And how should I set a path for additional packages? Thank you Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] NotImplemented?
Isn't it a bit strange if in the documentation it says "NotImplementedError"? http://doc.sagemath.org/html/en/reference/arithgroup/sage/modular/arithgroup/arithgroup_generic.html#sage.modular.arithgroup.arithgroup_generic.ArithmeticSubgroup.coset_reps Is it true that Sage cannot compute the representatives of Gamma(4) in Gamma(2)? Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Question on git merge
If it is only a small difference to just one file on another (diverged) branch, then why not simply create a patch and apply it to the right branch. Something like this. git checkout mybranch git format-patch -k1 # if it is just on commit # This gives a file 0001-... git checkout master git am 0001-... I thought that cherry-pick does exactly that, but I've had more success with the above sequence. Especially if previous commits on "mybranch" conflicted with the diverging master, but the commit on top of mybranch applied cleanly. Ralf On 07/11/2017 03:32 PM, Simon King wrote: > On 2017-07-11, Daniel Krenn wrote: >> On 2017-07-11 14:39, Simon King wrote: >>> Being on a different git branch, I tried >>>git cherry-pick xyz >> >> Why cherry-pick and not simply >> git merge xyz >> ? This could git help finding a proper merge base. > > Because I didn't want to merge the whole branch. It was only > about the single commit. Moreover, I just tried "git merge" in a toy > example, and it was not better than "git cherry-pick". > > I believe it is obvious that the branch which the xyz's changeset is > being applied to (by cherry-pick or by merge) *always* is a better > merge base than the branch that xyz comes from. > > Best regards, > Simon > -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] convert .sws to .ipynb
> Also, sagews != sws, i.e., that script won't help you. > > If I were you, I would start with this script that I wrote: >https://github.com/sagemathinc/smc/blob/master/salvus/scripts/sws2sagews.py > > since it parses sws files at least. Thank you. Worked like a charm. Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] convert .sws to .ipynb
Hello, I'd like to convert some simple .sws file into Ipython notebooks (.ipynb). Searching for a converter led me to https://github.com/anteprandium/sagews2ipynb but unfortunately the README.md says nothing about how to actually call the script. Any suggestions? Thank you Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] 404 Error: page not found
Click Changelog on http://www.sagemath.org/ Or README.txt on http://www.sagemath.org/download-source.html http://www.sagemath.org/mirror/src/README.txt Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] missing changelog
There is currently a 404 for http://sagemath.org/mirror/src/changelogs/sage-6.5.txt which is linked from http://sagemath.org/ Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: [fricas-devel] fricas pkg in Sage
On 12/06/2014 06:23 PM, 20100.delecr...@gmail.com wrote: > I have a very naive question: the version of lisp we have in Sage is ecl, > does it make a huge difference with sbcl ? I'd say yes. But it's probably Waldek who has more knowledge of ecl vs. sbcl. I only remember that compilation (at least some years ago) with ecl took quite a bit longer than with sbcl. In fact, I don't see any "embeddable" advantage of ecl for Sage. It's usually the computation that costs time (since I only expect heavier or complicated computations exported to FriCAS) not the conversion from one Sage to FriCAS and back. Especially the translation of FriCAS types into Sage types is nearly impossible. FriCAS has quite a sophisticated type hierarchy. I would expect that there isn't even always a corresponding Sage type that one could convert the FriCAS result to in order to have those values natively available for further computations in Sage. Anyway, being able to call FriCAS from within Sage and thus giving Sage users access to the power of FriCAS, is certainly a good step. Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] git config --global push.default matching/simple ?
http://www.lmgtfy.com/?q=git+config+global+push.default+simple&l=1 On 11/20/2014 09:04 PM, John Cremona wrote: > On 20 November 2014 17:24, Dima Pasechnik wrote: >> with new git, one has new default behavour of git push. Namely, you can >> choose >> git config --global push.default matching >> or >> git config --global push.default simple >> >> Which one should one choose for Sage workflow? >> (sorry for possibly dumb question). > > An even dumber question: what is the difference? > > John -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Docs, "return" vs. "returns" etc.
On 08/22/2014 10:14 PM, Volker Braun wrote: > On Friday, August 22, 2014 9:11:08 PM UTC+1, Ralf Hemmecke wrote: >> >> Well, of course, a name is just a name. So call the function 'foo' >> instead of 'nonzero'. Would you still be happy with the specification? >> > > I wouldn't be happy with the method name to start with. No amount of > documentation can save a badly-chosen UI. The aim should always be to be so > clear that the use doesn't have to look it up in the docs. Maybe I should say that I'm on your side when it comes to name methods by full name and in such a way that they basically describe what they do. Nevertheless, the function name is not the specification. The point I want to make is that some programmer might have chosen a name that does not exactly describe what the function does, i.e. in some cases the reader of the API would believe something from the name that is actually wrong. Now suppose that in such a case the docstring is vague and somehow relies on the programmers (false) belief that he chose the name right. I guess you probably agree with me that this calls for bugs later. There should be no need to look at the source code in order to know the input/output behaviour of a function. The documentation should suffice. If the function is named well, that's certainly a plus, but the specification is what is really important, not the name of the function. For example, take "mod" and suppose the documentation says. For two integers a and b (b nonzero), a mod b computes the remainder of the division of a by b. Unless the programmer has specified somewhere what he means by "remainder", I wouldn't exactly know what this function does. Or would you know what mod(6,7) would return with the above specification? Does the name "mod" help you? Maybe you say, that name is bad. OK. Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Docs, "return" vs. "returns" etc.
> Suppose you have: >> "nonzero(x) tests whether x is zero or not" > Your example is confusing because the method name is not expressive enough. > Call it is_nonzero() and it is much clearer. Or maybe ensure_nonzero(x) if > you want to return x if x!=0 and something else if x==0. Well, of course, a name is just a name. So call the function 'foo' instead of 'nonzero'. Would you still be happy with the specification? Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Docs, "return" vs. "returns" etc.
> Shorter is generally better for headlines, so I'd prefer "Test whether f is > foo" over "Return whether f is foo" over "Return ``True`` if f is foo, and > ``False`` otherwise". I hate it when someone documents 'test whether this and that holds'. Or is there some convention that a test returns true if something holds and false otherwise? Suppose you have: "nonzero(x) tests whether x is zero or not" What does nonzero return? You have at least 5 possible return values. True False 0 1 x Would everyone interpret in the same way as the documenter actually wanted it to be interpreted? Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] backups of the git tree ?
> what if the russians suddendly attack the US When does it stop that everyone fears the other for no good reason. I guess if you ask an ordinary russian person, he fears being invaded by the US. Are we still in the cold war? > reach our server and achieve to erase our data ? (or what if our hard > drive burns ?) Tell your friends about the repository and let it be cloned to several distant physical places in the world. Then sit back and relax (or rather trust that sha-1 is still somewhat safe to ensure that you have the right history up to a certain point. As Robert said, cloned repositories are more or less backups of each other. Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] (c) Copyright 2005--2011, The Sage Development Team
Perhaps here? http://git.sagemath.org/sage.git/tree/src/doc/common/conf.py#n40 Ralf On 06/26/2014 09:52 AM, Nathann Cohen wrote: > That's what you can read at the bottom of the doc pages : > > http://www.sagemath.org/doc/index.html > > Does anybody know how to change that ? > > Nathann > -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: hash for algebraic field
>>> I'll second this. Are there *any* computer algebra systems (or >>> programming languages for that matter) out there such that 4/2 != 2 != >>> 2.0? Code would simply be too hard to write. >> >> Ada, I guess. It should give error if you try to compare integer with float. > > Ah, no wonder it's so widely used :). Right. ;-) In FriCAS you get (1=1.0)@Boolean if you type that in a session, but ... (200) -> )compile foo.spad Compiling FriCAS source code from file /home/hemmecke/foo.spad using old system compiler. FOO abbreviates package Foo initializing NRLIB FOO for Foo compiling into NRLIB FOO compiling exported foo : () -> Boolean ** comp fails at level 3 with expression: ** error in function foo (= (|Sel| (|Integer|) 1) (|Sel| (|Float|) 1)) ** level 3 ** $x:= (Sel (Float) (One)) $m:= (Integer) $f:= |$Information| #) (|foo| #) (|$DomainsInScope| # # #) ($ # #) ...))) >> Apparent user error: Cannot coerce (call (XLAM ignore 1)) of mode (Integer) to mode (Float) for the source code: )abbrev package FOO Foo Foo: with foo: () -> Boolean == add foo(): Boolean == (1$Integer = 1$Float) In other words. For the compilation, there will be no automatic coercion, but in a interactive session, FriCAS will try to find respective types so that the function (here it is =: (%, %)-> % ) is available. I.e. in the above case it finds coerce: Integer -> Float and thus uses =: (Float, Float)-> Float in a session. Maybe that is not what you want or even can do in Sage, but I find this programming vs. interactive session distinction rather good. I don't like if my program suddenly behaves differently only because someone has slightly changed the coercion system. As a programmer I would like to have control on whether I consider the integer 1 equal to the 2 by 2 unit matrix. We do the same in mathematics. Rational numbers are pair of integers modulo ... so how can they be equal to an integer? Yes, we have an embedding. The question is simply whether one wants a system that hides that embedding (coercion) or a sytem that makes that coercion explicit. I think FriCAS makes a good compromise with this. Just my 2 cents. Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: free private github repos
On 05/15/2014 10:55 AM, Volker Braun wrote: > Of course I'm not going to say no to free stuff, but hosting your own > unlimited number of private repos (and/or a gitolite installation, as we do > for Sage) is pretty simple ;-) Bsst! Not so loud! ;-) If people knew how easy it is to share git repos privately, nobody would pay for bitbucket or github anymore and we would lose all the free services they offer. ;-) Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Viewing "real" merge commit
I have not personally used it (so I might be wrong), but I somehow feel that git-rerere might be of some help. As I understand, you basically want to see exactly what your merge resolution was. http://git-scm.com/blog/2010/03/08/rerere.html Ralf On 03/27/2014 12:31 AM, Andrey Novoseltsev wrote: > Hello, > > I have just merged current "develop" into a branch abandoned half a year > ago (http://trac.sagemath.org/ticket/15240). I think I've resolved > conflicts correctly, but once everything is committed - how can I review > what exactly have I done during the merge? I.e. how can see just the hunks > that I had to edit/approve manually during the merge? Clicking on the > branch on trac seems to show the difference between the current state and > the branch, which looks OK, but since there are many changes it is hard to > say anything about the merge. Clicking on the last merge commit, on the > other hand, shows changes to the whole library and is useless. > > Thank you! > Andrey > -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] system-wide sage installation with option to add spkgs locally
> i'd be happy to see (something like) SAGE_PREFIX (maybe just PREFIX?) in > future versions. i'm sorry i currently don't have a lot of (read: "no") > time to work on this. Sounds like: "No Ralf's use case is not yet possible with Sage 6.1.1." :-( Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] system-wide sage installation with option to add spkgs locally
I don't know whether this is the right place to ask, but how can meet Sage the following use case? - system-wide installation of sage in /opt/sage/$SAGEVERSION - /opt/sage is not writable by an ordinary user - "sage -i PACKAGE" exacuted as an ordinary user should install an additional spkg into $HOME/.sage-local/$SAGEVERSION. Is that currently possible? Can such behaviour be easily achieved? Of course, I don't want to copy the full installation of Sage, but rather only the files that "sage -i" needs to modify are copied over to $HOME. And I would expect that Sage first looks into $HOME/.sage-local/$SAGEVERSION before it tries /opt/sage/$SAGEVERSION. Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] review and rebase workflow with git
>> 6. And then create a new branch, say "my_branch", to work (do the review) >> on, if I choose not to work "detached": >> >> git checkout -b my_branch FETCH_HEAD Right. And I don't know why one ever seriously wants to work detached. Detached work is always in danger of being garbage collected via git gc. It's simply too easy to create and remove branches. git branch my_branch git branch -D my_branch Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Volunteer for changelog?
On 12/17/2013 04:14 PM, Volker Braun wrote:
> Jeroen has been doing very nice release announcements summarizing the
> changes and people involved. For an example, see
>
> https://groups.google.com/d/msg/sage-release/V5RVnB2sH88/zs8hXmUlkq8J
>
> It would be nice to keep that tradition, but also divide up the
> responsibilities to make the release process more sustainable. Maybe
> somebody wants to volunteer (*hint* *hint*) to write the release notes? The
> information is contained in the git commit history, it just needs to be
> presented in a concise way:
I guess authors can easily be listed via
git log --format=" - %an" 6.0.rc0..6.0.rc1|sort -u|grep -v 'Release
Manager'
And for the other log information take something like this...
git log --grep '^Trac #[0-9]*:' --format="%B" 6.0.rc0..6.0.rc1|perl
-e 'while (<>){chomp;if(s/^Trac #//){if($l){print
"$l\n"}$l=$_}if(s|^Reviewer\(s\): ||){$l.=" [Reviewed by
$_]"}}if($l){print "$l\n"}'
Ralf
--
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 group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [fricas-devel] Re: [sage-devel] Ubuntu/Debian packages
> https://cloud.sagemath.com/projects/87b42925-de3b-482c-99b2-edf1e1ba8bfb/files/fricas/rhx-instructions Updated. That compiles Aldor and FriCAS and seems to work. Unfortunately, FriCAS will show Version: FriCAS 2013-09-27 which isn't quite correct. Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [fricas-devel] Re: [sage-devel] Ubuntu/Debian packages
> Could you re-send me the link to the instructions? Thanks!
I would have done that before but I didn't know whether a link like this
https://cloud.sagemath.com/projects/87b42925-de3b-482c-99b2-edf1e1ba8bfb/files/fricas.term
does help you. Anyway, under
https://cloud.sagemath.com/projects
I see "Test Aldor in Sage Cloud". In there I have a fricas.term.
How would one actually provide an appropriate link?
The instructions are in $HOME/fricas/rhx-instructions.
I wanted also to add instructions to compile aldor from Pippijn's github
repo. But unfortunately libtool is not installed and thus I cannot
successfully run ./autogen.sh.
Ralf
===
~/fricas$ cat rhx-instructions
#!/usr/bin/env bash
set -e
#apt-get install sbcl emacs libgmp3-dev git build-essential gawk noweb
# Unless the "datadir=" line is already in the aldor wrapper script.
# By now you probably have a newer version of Aldor.
## mkdir -p $HOME/local/bin
## sed 's,EXEEXT=,datadir=${prefix}/share\nEXEEXT=,' /usr/bin/aldor >
$HOME/local/bin/aldor
export PATH=$HOME/local/bin:$PATH
# The following branch fricas-aldor-local works with the installed
debian version.
# It should also work with newer versions, but one never knows.
# It's a patch series that is not yet in the official FriCAS SVN repo.
git clone https://github.com/hemmecke/fricas.git fricas
cd fricas
# No longer needed since FriCAS now include the .as files.
git checkout -b fricas-aldor-local origin/fricas-aldor-local
# We build FriCAS inside it's source tree and install into $HOME/local.
./configure --enable-aldor --with-lisp=sbcl --enable-gmp
--prefix=$HOME/local
time make -j10 > make.log 2>&1
--
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 group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [fricas-devel] Re: [sage-devel] Ubuntu/Debian packages
Hi William, I've updated rhx-instructions for the installation of FriCAS that should work in connection with Aldor. You'd need the latest github versions of both. Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [fricas-devel] Re: [sage-devel] Ubuntu/Debian packages
Hi William, hi Pippijn, As of today, we can also provide packages for Debian and Ubuntu at https://launchpad.net/~pippijn/+archive/ppa I haven't checked exactly what sha1 from his aldor git repo actually corresponds to this ppa. But that would be important. Since only recently FriCAS added a patch of Peter Broeadbery that synchronizes some hash function computation with Aldor. (Marked below with <<<.) git log --oneline bb49660 Add 'qsetfirst!' and 'qsetrest!' 2004dff Implement missing functions in Dequeue. f23ecc5 remove SPAD variable d7606b3 find aldor at startup f906854 remove trailing whitespace, trailing empty lines, expand tabs 20c6779 Fix ArrayStack. 69dd1f8 Aldor: Use newer hash function. << 3966c94 Aldor: Don't try to evaluate conditions on categories where the category 096d0f8 Use different symbols for labels and values. f4e21a1 make clean now does not remove cliques.as 8a66a07 Evaluate the lambertW function for the special value at -1/e. 8cd3e73 Update INSTALL, INSTALL.aldor and release notes. I.e. using the latest FriCAS from https://github.com/hemmecke/fricas-svn/commits/master would require a corresponding version of Aldor. (The most rrecent from Pippijn's github repo should work.) Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] compile sage from github
On 11/12/2013 07:00 PM, Michael Orlitzky wrote: > Yes, yes, and yes. But there's more: Oh... I only wondered why Sage from github wants to install its own git. But this thread seems to develop into a discussion of some people that like a monolithic we-redo-all-ourselves sage and some that like more if sage builds on underlying software that comes with the distribution. That nearly sounds like a good reason to fork. ;-) Ralf PS: Maybe I shouldn't have started typing make on a system without gettext. :-( -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] compile sage from github
On 11/11/2013 07:22 PM, William Stein wrote: >> check "git --version" and then don't start trying to build git at all, > If this (and any other similar) change is made, it needs to be made in > a way that doesn't mess up the binaries we build. The binaries that > are built for generic redistribution should have everything built by > default. I guess, it should be standard that a "make" started from a github checkout tests the system and builds git (or anything else that is already available in a reasonable version on the system) only if its non-existing or existing in an incompatible form. I would assume that for creating the source release one would (instead) have to type "make dist" [1] and for a binary distribution perhaps "make bindist". The *result* would then contain/build everything as required. It's perhaps also reasonable that the Makefile that is produced for the distribution is slightly different than the one on github or that one simply adds an additional file to the distribution tarball that enables "make" to distinguish between github checkout and source/binary distribution. Given the many software packages on which Sage builds, I wouldn't expect that I get exactly the same sage (as in the official release) when I type "make" from a github checkout. The only thing I would expect is that I am *able* to build exactly the same distribution files and thus can do everything localy a release manager usually does. For that, it is, of course, necessary, to list somewhere the *exact* versions of all the subpackages that go into a sage release (i.e. to make it reproducible). I think sage already does the latter with the spkgs, but why not also have another list for *minimal version requirements* of other software like git, maxima, ecl, etc.? Just an idea. Ralf [1] http://www.gnu.org/software/make/manual/make.html#Standard-Targets -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] compile sage from github
>> check "git --version" and then don't start trying to build git at all, > That is really a feature request, not a bug. Of course it would be nice. If > you want to work on a configure-style script that queries the system for > build- and runtime dependencies then please do! Interesting! You can check the archive that I tried to do this some years ago and nobody was interested, quite the contrary. Time seemed to have changed that, but my coding time now mainly goes to other projects. Sorry. Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] compile sage from github
> It would be nice if you could answer Vincent's question about the > full build log so it can be fixed. As promised... Oh, interesting, I just looked through it. One can find there something like /bin/sh: 1: curl-config: not found /bin/sh: 4: autoconf: not found /bin/sh: 1: msgfmt: not found but only the last one seems to matter. Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out. Found local metadata for git-1.7.12.2.p0 Attempting to download package git-1.7.12.2.p0 >>> Trying to download http://www.sagemath.org/packages/upstream//git/git-1.7.12.2.tar.bz2 [] Checksum: 8cce24a390595d6e62c3aa66bef332ab95900173 vs 8cce24a390595d6e62c3aa66bef332ab95900173 git-1.7.12.2.p0 Setting up build directory for git-1.7.12.2.p0 Finished set up Host system: Linux fricas 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux C compiler: gcc C compiler version: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.7/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 4.7.2-5' --with-bugurl=file:///usr/share/doc/gcc-4.7/README.Bugs --enable-languages=c,c++,go,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.7 --enable-shared --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.7 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin --enable-objc-gc --with-arch-32=i586 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.7.2 (Debian 4.7.2-5) Using install program /usr/bin/install /bin/sh: 1: curl-config: not found make[3]: Entering directory `/home/me/v/git/sage/local/var/tmp/sage/build/git-1.7.12.2.p0/src' GIT_VERSION = 1.7.12.2 make[3]: Leaving directory `/home/me/v/git/sage/local/var/tmp/sage/build/git-1.7.12.2.p0/src' /bin/sh: 1: curl-config: not found make[3]: Entering directory `/home/me/v/git/sage/local/var/tmp/sage/build/git-1.7.12.2.p0/src' make[3]: `GIT-VERSION-FILE' is up to date. make[3]: Leaving directory `/home/me/v/git/sage/local/var/tmp/sage/build/git-1.7.12.2.p0/src' configure: Setting SANE_TOOL_PATH to '' configure: Setting lib to 'lib' (the default) configure: Will try -pthread then -lpthread to enable POSIX Threads. configure: CHECKS for site configuration configure: Setting PYTHON_PATH to /home/me/v/git/sage/local/bin/python configure: CHECKS for programs checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for inline... inline checking if linker supports -R... no checking if linker supports -Wl,-rpath,... yes checking for gtar... no checking for tar... tar checking for gnudiff... no checking for gdiff... no checking for diff... diff checking for asciidoc... no configure: CHECKS for libraries checking for SHA1_Init in -lcrypto... yes checking for curl_global_init in -lcurl... no checking for XML_ParserCreate in -lexpat... no checking for iconv in -lc... yes checking for deflateBound in -lz... yes checking for socket in -lc... yes checking for inet_ntop... yes checking for inet_pton... yes checking for hstrerror... yes checking for basename in -lc... yes checking for gettext in -lc... yes checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes configure: CHECKS for header files checking sys/select.h usability... yes checking sys/select.h presence
Re: [sage-devel] compile sage from github
>> My initial question was "What requirement for git does Sage have?" > It should have none, you found a bug. It would be nice if you could answer > Vincent's question about the full build log so it can be fixed. OK. I can only dig that out later. But I think even if I send that log, the bug is rather that Sage should check "git --version" and then don't start trying to build git at all, no? My log wouldn't help for that, since all the information about git versions was already in my initial mai. Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] compile sage from github
>> mean that a sage installation should never install anything that is >> already available in a standard distribution. > Even if that means that the Sage testsuite fails because distribution > packages have a bug that isn't fixed upstream yet? Thats an important > policy question and we never had that discussion Come on, it's clear that a decent system that wants to build on existing software has to specify the least requirement for that existing software. If the underlying distribution does not fulfil that requirement, something else has to be done. My initial question was "What requirement for git does Sage have?" Where can I find a list of version number for all the packages that are available in some distribution and *could* be used by Sage. In other words why did my sage build want to install git on Debian 7 although I already have it installed. Does that mean the git that comes with Debian 7 has a bug that sage cannot live with? I guess not. > can you summarize what the problems > Build it on all supported platforms and then report back. This ought to be > the most important output of the project but I never saw it. I don't have the feeling that this answers my question. :-( Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] compile sage from github
On 11/11/2013 06:29 PM, Volker Braun wrote: > Its not a technical problem - I think Felix is technically very competent. > But he didn't listen to our concerns nor did he engage in discussions. He > continues to be focused on Debian whereas Sage has a much larger target. In > the end, a Debian fork was created which does absolutely nothing for other > platforms. Since I did not follow the GSOC discussion, can you point me (or better summarize) what the better alternative would be to install sage on default packages that are available a given distribution? Of course, I mean that a sage installation should never install anything that is already available in a standard distribution. Obviously your (and probably others) opinion is that a sage installation as approached by Felix for Debian cannot easily be lifted to other non-debian distributions. I haven't actually looked at any code (so I'm rather uninformed). Still, can you summarize what the problems with Felix' approach is? Thank you Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] compile sage from github
> The part of the log you paste is not long enough. I guess you need to > install msgfmt which is not part of standard debain. The name of the > package is gettext. Thanks. I'd probably found that myself. But of course, that was not my point. > Does anybody know why git is a standard spkg ? It is likely that > anybody has his/her own git... That comes closer. Wouldn't it make sense to let (sage-)configure test whether the features of an installed git are already sufficient? I personally would get confused if sage used its own git. Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] compile sage from github
Hello! I've cloned from git://github.com/sagemath/sage.git (094712a Merge in bug fixes for the dev scripts) and typed "make" on a (relatively minimal) Debian 7 Installation. I didn't know whether such a step would actually succeed, since I haven't yet been able to find a description that such a simple "make" would work. So I didn't expect success. But I am somewhat surprised that the build fails at building git (see below). :-( My Debian system says: git version 1.7.10.4 and Sage wants to build 1.7.12.2. Is there really any reason why Sage wouldn't be satisfied with a smaller version number. What super features are used when building/developing sage that justify the need for 1.7.12.2? What actually surprises me is that Sage must build git at all. Wouldn't it make sense to restrict build and development scripts to use features of a git version number that is usually satisfied by current major stable distributions and build git only when this is not fuflilled for some very old distribution. Note that git must have been installed, since I have (successfully) cloned sage from github. Ralf = Manifying blib/man3/Git.3pm make[5]: Leaving directory `/home/me/v/git/sage/local/var/tmp/sage/build/git-1.7.12.2.p0/src/perl' make[4]: Leaving directory `/home/me/v/git/sage/local/var/tmp/sage/build/git-1.7.12.2.p0/src/perl' make[4]: Entering directory `/home/me/v/git/sage/local/var/tmp/sage/build/git-1.7.12.2.p0/src/git_remote_helpers' make[4]: Leaving directory `/home/me/v/git/sage/local/var/tmp/sage/build/git-1.7.12.2.p0/src/git_remote_helpers' make[4]: Entering directory `/home/me/v/git/sage/local/var/tmp/sage/build/git-1.7.12.2.p0/src/templates' make[4]: Leaving directory `/home/me/v/git/sage/local/var/tmp/sage/build/git-1.7.12.2.p0/src/templates' MSGFMT po/build/locale/da/LC_MESSAGES/git.mo /bin/sh: 1: msgfmt: not found make[3]: *** [po/build/locale/da/LC_MESSAGES/git.mo] Error 127 make[3]: Leaving directory `/home/me/v/git/sage/local/var/tmp/sage/build/git-1.7.12.2.p0/src' Error building git. real1m20.508s user1m2.884s sys 0m7.028s Error installing package git-1.7.12.2.p0 Please email sage-devel (http://groups.google.com/group/sage-devel) explaining the problem and including the relevant part of the log file /home/me/v/git/sage/logs/pkgs/git-1.7.12.2.p0.log Describe your computer, operating system, etc. If you want to try to fix the problem yourself, *don't* just cd to /home/me/v/git/sage/local/var/tmp/sage/build/git-1.7.12.2.p0 and type 'make' or whatever is appropriate. Instead, the following commands setup all environment variables correctly and load a subshell for you to debug the error: (cd '/home/me/v/git/sage/local/var/tmp/sage/build/git-1.7.12.2.p0' && '/home/me/v/git/sage/sage' --sh) When you are done debugging, you can type "exit" to leave the subshell. make[2]: *** [/home/me/v/git/sage/local/var/lib/sage/installed/git-1.7.12.2.p0] Error 1 make[2]: Leaving directory `/home/me/v/git/sage/build' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/me/v/git/sage/build' real159m35.587s user120m8.078s sys 8m16.735s *** Error building Sage. The following package(s) may have failed to build: package: git-1.7.12.2.p0 log file: /home/me/v/git/sage/logs/pkgs/git-1.7.12.2.p0.log build directory: /home/me/v/git/sage/local/var/tmp/sage/build/git-1.7.12.2.p0 The build directory may contain configuration files and other potentially helpful information. WARNING: if you now run 'make' again, the build directory will, by default, be deleted. Set the environment variable SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this. make: *** [build] Error 1 -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: Changing branch on a trac ticket
On 11/05/2013 12:02 PM, Simon King wrote: > Good. So, would you (and other people) agree that the effort needed to > rebase X on top of A-C' is always (i.e., also in the case of conflicts) > the same as the effort needed to rebase X on top of A-B-C-D (where D > reverts B)? In terms of code the situation at D (in A-B-C-D) agrees with that at C' (in A-C'). I don't see any reason why rebasing X on top of D is in any way different from rebasing it on top of C'. > If you agree, then let me repeat my question: Why do some people believe > that changing A-B-C into A-B-C-D is better than changing it into A-C'? > Because in this case I really don't get the argument. Some people believe that changing history is bad and some don't. I would put it that way: it's a convention. If a developer works on a branch and clearly states that this branch is "work in progress" (In other words he says, nobody should rely on that code.), then I even think it is *good* to publish such work and let other people comment on it. If however wrong code ever gets committed into the "official master branch", then it's "official" and commits that are not wanted should be reverted (i.e. a new commit added) instead of history is rewritten. Well, the question now is whether the Sage convention sees submissions to TRAC more like the first view or more like "official" proposals whose history should be kept. In fact, all Sage developers simply have to agree on one convention. I don't think that one is particularly better than the other. Personally, I somehow tend more to a convention which would forbid history rewriting only for the master branch. And to all branches that got a "positive review". All other stuff is work in progress and thus people know that commits can be reordered or squashed together or even disappear. Work in progress that is publicly seen isn't that bad. How else would one like to collaborate in small groups that work on a restricted field of interest? Code must be shown to collaborators, but whether this code exchange is just via github or via the "official" sage-trac machinery is yet another question. Just my 2 cents Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] git workflow with trac?
Bold question... does Sage still need Trac? Has someone already compared all options for a workflow with git? Sage-Trac vs. Github pull-requests with comments vs. Gerrit vs. ... https://help.github.com/articles/using-pull-requests http://alblue.bandlem.com/2011/02/gerrit-git-review-with-jenkins-ci.html Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: Changing branch on a trac ticket
On 11/05/2013 10:09 AM, Simon King wrote: >> To achieve this from the above situation, you do >> >> git rebase --onto ticket/123 master ticket/456 > > Good to know! I did not test yet. Is there any manual intervention > needed, if X is disjoint from the changes introduced in B? No. A merge conflict can only happen, if X builds (depends) on changes that are introduced in B, since these changes would not be there in the A-C branch. Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: Changing branch on a trac ticket
> So, what simple and easy-to-use command does git offer to create a > "negative commit"? That's to say, if I have commits A-B-C and want to > "remove" B, how can I make git create a commit D for me such that > A-B-C-D results in the same code as A-C? https://www.kernel.org/pub/software/scm/git/docs/git-revert.html > Anyway, I think it is a good idea to have a concrete > example. I created a test repository, created ticket/123, > ticket/456 and an identical copy ticket/456new of ticke/456. > > The commits are > - A: Introduces file bla > - B: Introduces file blaB > - C: Changes file bla > - X: Changes file bla on top of commit C > Branches master and ticket/123 is A-B-C, branches ticket/456 and > ticket/456new are A-B-C-X > > Result on ticket/123 = master > git log --oneline > 202a495 Commit C > c7edaa0 Commit B > 3c00aaf Commit A > ls > bla blaB > > Then, I changed ticket/123 by > git reset --hard HEAD~2 > followed by > git cherry-pick master > > The result was > git log --oneline > e7d13cf Commit C > 3c00aaf Commit A > ls > bla OK, now we have A B C = masterX = ticket/456 o --> o --> o ---> o --> o | | +--> o C' = ticket/123 I must say, I don't quite understand what it means that ticket/456 and ticket/456new are identical? Do they correspond to the same (git-)sha1? > Question to the git experts: > - Is there an easy git command that creates a new commit reverting the > effects of a specified old commit (or series of old commits)? I assume what you want as a result is this: A B C = master o --> o --> o ---> o | | +--> o ---> o C' = ticket/123X = ticket/456 To achieve this from the above situation, you do git rebase --onto ticket/123 master ticket/456 You can find some more information about "git rebase --onto" here. (General rebasing starts at slide 148.) http://www.slideshare.net/railsconf/smacking-git-around-advanced-git-tricks?src=related_normal&rel=2731503 Of course, instead of just X you could have several commits on top of C(=master) leading to X. The command would be the same. I hope, that is what you wanted. Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [fricas-devel] Re: [sage-devel] Ubuntu/Debian packages
> Bill Page made a project on cloud called "Test Aldor in Sage Cloud",
> added me to it, and I've now added you to it.
> I "apt-get install"'ed the packages you mentioned above. There's a
> directory in the project called "fricas" and a terminal "fricas.term"
> opened there. I tried running your instructions and it didn't work.
> Any chance you can take a look and fix things to at least build
> locally in that project? Once I have a script to automate the build,
> then this new fricas will be a standard part of cloud.sagemath
> henceforth.
Hi Bill, hello William,
take a look into $HOME/fricas/rhx-instructions. Using
bash rhx-instructions
cd fricas && make install
will install fricas locally into $HOME/local. I'm sure you find the
--prefix if you want to install it globally.
I've tested with the myfib.as, but I don't pretend that everything is
working fine.
Anyway, it's a good opportunity to get more feedback wrt the
FriCAS-Aldor connection.
And indeed, there seem to be issues with the fricas-aldor interface (see
below).
Waldek, do you have any idea where this error might come from. Looking
at the very bottom seems to suggest that it's something connected to the
exponent in the series.
I don't quite understand the problem since it works with L, but not with
S, although S (FunnySeries) is, in fact, only calling the respective
operations from L.
Ralf
=== funny.as
#include "axiom"
L ==> UnivariateLaurentSeries(F, v, c);
FunnySeries(F: Field, v: Symbol, c: F): Field with {
coerce: L -> %;
coerce: % -> L;
} == add {
Rep == L;
import from L;
coerce(l: L): % == per l;
coerce(x: %): L == rep x;
(x: %) + (y: %): % == per (rep x * rep y);
(x: %) * (y: %): % == per (rep x + rep y);
(x: %) = (y: %): Boolean == rep x = rep y;
coerce(x: %): OutputForm == {
OF ==> OutputForm;
import from List OF;
hconcat ["funny(" :: OF, rep(x) :: OF, ")" :: OF];
}
hashUpdate!(h: HashState, x: %): HashState == hashUpdate!(h, rep x);
0: % == per(0$Rep);
1: % == per(1$Rep);
_-(x: %): % == per(-rep x);
characteristic(): NonNegativeInteger == characteristic()$Rep;
}
(1) -> )co funny.as
Compiling FriCAS source code from file
/home/hemmecke/scratch/funny.as using AXIOM-XL compiler and
options
-O -Fasy -Fao -Flsp -laxiom -Mno-ALDOR_W_WillObsolete -DAxiom -Y
$AXIOM/algebra -I $AXIOM/algebra
Use the system command )set compiler args to change these
options.
Internal warning: Use Env called outside gl0Prog (glvLexFormats is NULL)
Compiling Lisp source code from file ./funny.lsp
Issuing )library command for funny
Reading /home/hemmecke/scratch/funny.asy
FunnySeries is now explicitly exposed in frame frame1
FunnySeries will be automatically loaded when needed from
/home/hemmecke/scratch/funny
(1) -> I ==> Integer
Type:
Void
(2) -> Q ==> Fraction I
Type:
Void
(3) -> L ==> UnivariateLaurentSeries(Q, v, c)
Type:
Void
(4) -> S ==> FunnySeries(Q, v, c)
Type:
Void
(5) -> c: Q := 0
(5) 0
Type:
Fraction(Integer)
(6) -> v: Symbol := "z" :: Symbol
(6) z
Type:
Symbol
(7) -> l1: L := 1$L
(7) 1
Type:
UnivariateLaurentSeries(Fraction(Integer),z,0)
(8) -> lx := integrate(l1)
(8) z
Type:
UnivariateLaurentSeries(Fraction(Integer),z,0)
(9) -> s1: S := l1 :: S
(9) funny(1)
Type:
FunnySeries(Fraction(Integer),z,0)
(10) -> sx := lx :: S
(10) funny(z)
Type:
FunnySeries(Fraction(Integer),z,0)
(11) -> s2 := s1 * s1
(11) funny(2)
Type:
FunnySeries(Fraction(Integer),z,0)
(12) -> l2 := s2 :: L
(12) 2
Type:
UnivariateLaurentSeries(Fraction(Integer),z,0)
(13) -> integrate l2
(13) 2z
Type:
UnivariateLaurentSeries(Fraction(Integer),z,0)
(14) -> s2x := integrate(l2)::S
(14) funny(2z)
Type:
FunnySeries(Fraction(Integer),z,0)
(15) -> s2x * sx
(15) funny(3z)
Type:
FunnySeries(Fraction(Integer),z,0)
(16) -> lx * lx
2
(16) z
Type:
UnivariateLaurentSeries(Fraction(Integer),z,0)
(17) -> sx2:=(lx * lx) :: S
2
(17) funny(z )
Type:
FunnySeries(Fraction(Integer),z,0)
(18)
Re: [fricas-devel] Re: [sage-devel] Ubuntu/Debian packages
> I tried with Aldor build form Aldor-2013.tar.gz. I had to > copy lang.as by hand to 'src/aldor' subdirectory of FriCAS > build tree, but otherwise things went smoothly. Yes, copying the respective files directly into the right place should also work, but I'm about to prepare a little temporary patch just for cloud.sagemath.com. > Note that building Aldor interface requires a lot of disc > space. True. Quite a lot of that could probably be removed already during the build. I didn't bother to do that, because when I figured out how the build actually succeeds, it was quite helpful to have all that garbage around. Waldek, would you mind if I prepare a patch that includes these few Apache-licensed files directly into the Fricas sourcetree? Then it would suffice to build the fricas-aldor interface with only having the aldor binary distribution around, not further trouble of hand-copying files or cloning the aldor repo or fetching in any other way from the Internet. Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [fricas-devel] Re: [sage-devel] Ubuntu/Debian packages
> Tell me exactly how to do that, and I would be happy to. apt-get install sbcl emacs libgmp3-dev apt-get install git build-essential gawk noweb # The following is probably not needed since I don't think that from within a browser you can start X applications like hyperdoc. # Since graphics in FriCAS also goes via a separate window, # it's questionable whether to build it or not. # But if you start configure in an environment that ha no X, # then then these component will be disabled anyway. apt-get install xvfb libxt-dev libxpm-dev git clone https://github.com/hemmecke/fricas-svn.git fricas or get the *source* tarball from http://fricas.sourceforge.net/download.html # You need the aldor sources just for a few files that are not yet # included in the fricas distribution. git clone https://github.com/pippijn/aldor.git # Since someone changed the relevant aldor tree we have to do a few # extra steps. Basically copying the files back. cp aldor/aldor/lib/libax0/src/*.as aldor/aldor/lib/libax0 # out-of-sourc-build mkdir build cd build ../fricas/configure --enable-aldor=../aldor --with-lisp=sbcl --enable-gmp --prefix=/path/to/install/location make -j10 make install That's should do it. Sorry, if the above contains an error, I've just written that up without testing. Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Ubuntu/Debian packages
> http://codemirror.net/mode/clike/index.html Ah, on can enter code there! I hadn't realized that at first. But no. None of the modes look in any way reasonable for aldor. Looks like JS-expert has to do something new. :-( Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Ubuntu/Debian packages
> Which of the modes at > >http://codemirror.net/ > > seems to best work with .as files? Since Aldor looks in some sense pretty much like C, I guess that should be fine. But in contrast to C one doesn't have TYPE FUNCTIONNAME(...) but rather FUNCTIONNAME(...): TYPE so that wouldn't fit. I haven't yet found a website where I can experiment with all the styles that codemirror offers. Any suggestion? Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Ubuntu/Debian packages
>>> [1] https://github.com/haraldschilly/sage-cloud-templates >> >> Well, I'm pretty new here and Harald's page doesn't really explain what >> I'd have to do to create such a template. > this is an example of how you can publish data from inside a project. Well, I begin to understand. https://cloud.sagemath.com/ gives me a terminal (worksheet is not (yet) appropriate for aldor). And I simply provide example aldor files with a description of how to compile them. Put that all into a public place (like a github repo). And then allow people to clone this repo from within the cloud.sagemath.com terminal. So practically cloud.sagemath.com just give me access to an external computer which already has a few software packages installed (and all of that inside a browser). Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Ubuntu/Debian packages
Hi William, On 07/23/2013 09:32 PM, William Stein wrote: > Nice. Your Aldor ubuntu package (with the updated fix so setting > ALDORROOT=/usr is not necessary) is now available in ther Terminal of > https://cloud.sagemath.com, in case anybody wants to easily try it > out. Just create an account, click "New Project", then in the project > "+New --> Terminal", and in the terminal type "aldor -gloop" as you do > above, and it works. Thanks William, for providing such a service. That's quite nice for someone just trying out Aldor without bothering to install Aldor locally. Can I make my program files that I put onto the cloud publicly available? What would be the URL? Or can I only make it available to collaborators who have a login at cloud.sagemath.org? > If somebody ends up making a cloud project with a few examples that > work, it would be a good example for our "project templates" library > [1]. > [1] https://github.com/haraldschilly/sage-cloud-templates Well, I'm pretty new here and Harald's page doesn't really explain what I'd have to do to create such a template. From that git repo I cannot even figure out what to do with such a template. Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [fricas-devel] Re: [sage-devel] Ubuntu/Debian packages
> I tried putting the program sieve.as from > http://www.aldor.org/docs/HTML/chap1.html into a file and typing > >aldor -Fx sieve.as > > as they do there, but it fails with many errors, starting as follows. > I don't know anything about Aldor really, so I'm probably doing > something wrong. The html documentation at aldor.org is outdated. Compile the aldor user guide (.pdf file) yourself or just use http://www.aldor.org/docs/aldorug.pdf. > ~$ aldor -Fx sieve.as > "sieve.as", line 6: import from Boolean, SingleInteger; > .^ > [L6 C22] #1 (Error) No meaning for identifier `SingleInteger'. You're not doing anything wrong, it's just that there are too many libraries and in Axiom, FriCAS, OpenAxiom, Axllib it's SingleInteger, but in LibAldor it's called MachineInteger. Use the pdf-Form of the Aldor User Guide. That's closer to the actual sources. > If somebody ends up making a cloud project with a few examples that > work, it would be a good example for our "project templates" library > [1]. Maybe later. But for a start, you can look into https://github.com/hemmecke/aldor-texts or https://github.com/pippijn/aldor/tree/master/aldor/lib/aldor/tutorial Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: SymbolicData
On 07/11/2013 01:04 PM, Martin Albrecht wrote: > I have to admit that I haven't touched that package in years, but I agree > that > we should use your database properly (my code is a bit of a hack). Martin, it would be interesting if you can list some use cases for the data and how you could imagine all the data is used (testsuites, benchmark tests, etc.). How this is translated into an API and who is going to implement that is another question, but getting people to know about SD and what they might want from SymbolicData would be quite useful already. Producing something with no user base is not very promising. Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: SQRT of negative number is negative? Or positive? Or what?
> does Axiom have Coercion? You surely have never looked into AXIOM. http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.132.4943&rep=rep1&type=pdf > How does it handle this? > http://www.sagemath.org/doc/reference/coercion/sage/structure/coerce.html It depends on how much automatic coercions you want to allow. For library programming I personally don't like automatic coercions, since they might hide a bug in the code. But working in an interactive session, AXIOM has some smartness in the interpreter that allows "coerce" (and sometimes also "convert" and "retract" functions) to be applied. Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] symbolic copy of installed sage into HOME
On 04/08/2013 02:26 PM, Julien Puydt wrote:
> Or instead of a real local copy, only have the same directory structure
> and symlinks for the files.
Suppose that $S is a shell variable that points to the installed Sage.
What do the people say who have more knowledge of the Sage-internals.
A) Is the following giving me a full functional Sage version in my HOME
(with only about 300 MB)? Or did I mis anything in my commands below?
B) Is "sage -i some-package" supposed to work in this local copy?
(It might be necessary to remove some links, I guess.)
Ralf
S=/opt/sage
T=$HOME/mysage
mkdir -p $T
cd $S
find . -type d -exec mkdir -p $T/{} \;# directories
find . -type f -exec ln -s $S/{} $T/{} \; # files
find . -type l -exec cp -d $S/{} $T/{} \; # links
cd $T
find . -name '*.pyc' -delete
find . -name '*.la' -delete
find . -name '*.pc' -delete
/bin/rm $T/local/default.qepcadrc
/bin/rm $T/local/lib/sage-current-location.txt
cp $S/local/lib/sage-current-location.txt
$T/local/lib/sage-current-location.txt
/bin/rm $T/spkg/bin/sage
cp $S/spkg/bin/sage $T/spkg/bin/sage
# Set SAGE_ROOT to point to $T
emacs $T/spkg/bin/sage
# do the relocation
./sage
--
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 group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] deinstallation of spkg
On 04/08/2013 01:39 PM, David Roe wrote: > There are various people working on making this possible, but it requires a > lot of changes to Sage's packaging system. As Jeroen says, this is not > currently possible. Thanks, but then another question. We have Sage installed centrally and would like to give people a chance to say something like "sage -i some-spkg". Does Sage allow to install packages locally in $HOME while a (read-only) vanilla Sage is in /opt/sage? Has such a scenario already be considered? Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] deinstallation of spkg
Is there a way to undo "sage -i somepackage", i.e. deinstall a package? Ralf -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] ImportError: libffi.so.6: cannot open shared object file
>> In particular, I ran into the problem (see below): >> >> ERROR:root:code for hash md5 was not found. > Well, I did "sage -i openssl" and then at least I could start sage. But then, I ran into the thing below and gave up. I used ftp://ftp.fu-berlin.de/unix/misc/sage/linux/32bit/sage-5.8-linux-32bit-ubuntu_12.04.2_lts-i686-Linux.tar.lzma Ralf sage: integrate(x,x) --- ImportError Traceback (most recent call last) in () > 1 integrate(x,x) /zvol/sage/sage-5.8/i686/local/lib/python2.7/site-packages/sage/misc/functional.pyc in integral(x, *args, **kwds) 738 """ 739 if hasattr(x, 'integral'): --> 740 return x.integral(*args, **kwds) 741 else: 742 from sage.symbolic.ring import SR /zvol/sage/sage-5.8/i686/local/lib/python2.7/site-packages/sage/symbolic/expression.so in sage.symbolic.expression.Expression.integral (sage/symbolic/expression.cpp:38413)() /zvol/sage/sage-5.8/i686/local/lib/python2.7/site-packages/sage/symbolic/integration/integral.pyc in integrate(expression, v, a, b, algorithm) 684 return integrator(expression, v, a, b) 685 if a is None: --> 686 return indefinite_integral(expression, v) 687 else: 688 return definite_integral(expression, v, a, b) /zvol/sage/sage-5.8/i686/local/lib/python2.7/site-packages/sage/symbolic/function.so in sage.symbolic.function.Function.__call__ (sage/symbolic/function.cpp:5125)() /zvol/sage/sage-5.8/i686/local/lib/python2.7/site-packages/sage/symbolic/integration/integral.pyc in _eval_(self, f, x) 82 # we try all listed integration algorithms 83 for integrator in self.integrators: ---> 84 res = integrator(f, x) 85 try: 86 return integrator(f, x) /zvol/sage/sage-5.8/i686/local/lib/python2.7/site-packages/sage/symbolic/integration/external.pyc in maxima_integrator(expression, v, a, b) 17 expression = SR(expression) 18 if a is None: ---> 19 result = maxima.sr_integral(expression,v) 20 else: 21 result = maxima.sr_integral(expression, v, a, b) /zvol/sage/sage-5.8/i686/local/lib/python2.7/site-packages/sage/misc/lazy_import.so in sage.misc.lazy_import.LazyImport.__getattr__ (sage/misc/lazy_import.c:1865)() /zvol/sage/sage-5.8/i686/local/lib/python2.7/site-packages/sage/misc/lazy_import.so in sage.misc.lazy_import.LazyImport._get_object (sage/misc/lazy_import.c:1268)() /zvol/sage/sage-5.8/i686/local/lib/python2.7/site-packages/sage/interfaces/maxima_lib.py in () 69 from sage.symbolic.ring import SR, var 70 ---> 71 from sage.libs.ecl import * 72 73 from maxima_abstract import (MaximaAbstract, MaximaAbstractFunction, ImportError: libffi.so.6: cannot open shared object file: No such file or directory -- 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 group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] md5 missing
Hello,
I want to install sage on a system that share the sage installation
directory and are all Debian6 machines, but they might have different
packages installed.
In particular, I ran into the problem (see below):
ERROR:root:code for hash md5 was not found.
Unfortunately, I haven't found a page that talks about prerequisites.
Any quick help available of what debian package I have to install to
make sage working?
Ralf
$ sage
--
| Sage Version 5.8, Release Date: 2013-03-15 |
| Type "notebook()" for the browser-based notebook interface.|
| Type "help()" for help.|
--
The Sage installation tree has moved
from /var/lib/buildbot/build/sage/arando-1/arando_binary/build/sage-5.8
to /zvol/sage/sage-5.8/i686
Updating various hardcoded paths...
(Please wait at most a few minutes.)
DO NOT INTERRUPT THIS.
Done updating paths.
ERROR:root:code for hash md5 was not found.
Traceback (most recent call last):
File "/zvol/sage/sage-5.8/i686/local/lib/python/hashlib.py", line 139,
in
globals()[__func_name] = __get_hash(__func_name)
File "/zvol/sage/sage-5.8/i686/local/lib/python/hashlib.py", line 91,
in __get_builtin_constructor
raise ValueError('unsupported hash type %s' % name)
ValueError: unsupported hash type md5
ERROR:root:code for hash sha1 was not found.
Traceback (most recent call last):
File "/zvol/sage/sage-5.8/i686/local/lib/python/hashlib.py", line 139,
in
globals()[__func_name] = __get_hash(__func_name)
File "/zvol/sage/sage-5.8/i686/local/lib/python/hashlib.py", line 91,
in __get_builtin_constructor
raise ValueError('unsupported hash type %s' % name)
ValueError: unsupported hash type sha1
ERROR:root:code for hash sha224 was not found.
Traceback (most recent call last):
File "/zvol/sage/sage-5.8/i686/local/lib/python/hashlib.py", line 139,
in
globals()[__func_name] = __get_hash(__func_name)
File "/zvol/sage/sage-5.8/i686/local/lib/python/hashlib.py", line 91,
in __get_builtin_constructor
raise ValueError('unsupported hash type %s' % name)
ValueError: unsupported hash type sha224
ERROR:root:code for hash sha256 was not found.
Traceback (most recent call last):
File "/zvol/sage/sage-5.8/i686/local/lib/python/hashlib.py", line 139,
in
globals()[__func_name] = __get_hash(__func_name)
File "/zvol/sage/sage-5.8/i686/local/lib/python/hashlib.py", line 91,
in __get_builtin_constructor
raise ValueError('unsupported hash type %s' % name)
ValueError: unsupported hash type sha256
ERROR:root:code for hash sha384 was not found.
Traceback (most recent call last):
File "/zvol/sage/sage-5.8/i686/local/lib/python/hashlib.py", line 139,
in
globals()[__func_name] = __get_hash(__func_name)
File "/zvol/sage/sage-5.8/i686/local/lib/python/hashlib.py", line 91,
in __get_builtin_constructor
raise ValueError('unsupported hash type %s' % name)
ValueError: unsupported hash type sha384
ERROR:root:code for hash sha512 was not found.
Traceback (most recent call last):
File "/zvol/sage/sage-5.8/i686/local/lib/python/hashlib.py", line 139,
in
globals()[__func_name] = __get_hash(__func_name)
File "/zvol/sage/sage-5.8/i686/local/lib/python/hashlib.py", line 91,
in __get_builtin_constructor
raise ValueError('unsupported hash type %s' % name)
ValueError: unsupported hash type sha512
Traceback (most recent call last):
File "/zvol/sage/sage-5.8/i686/local/bin/sage-ipython", line 6, in
from sage.misc.interpreter import SageTerminalApp
File
"/zvol/sage/sage-5.8/i686/local/lib/python2.7/site-packages/sage/misc/interpreter.py",
line 68, in
from IPython.utils.py3compat import cast_unicode
File
"/zvol/sage/sage-5.8/i686/local/lib/python2.7/site-packages/IPython/__init__.py",
line 43, in
from .config.loader import Config
File
"/zvol/sage/sage-5.8/i686/local/lib/python2.7/site-packages/IPython/config/__init__.py",
line 16, in
from .application import *
File
"/zvol/sage/sage-5.8/i686/local/lib/python2.7/site-packages/IPython/config/application.py",
line 31, in
from IPython.config.configurable import SingletonConfigurable
File
"/zvol/sage/sage-5.8/i686/local/lib/python2.7/site-packages/IPython/config/configurable.py",
line 26, in
from loader import Config
File
"/zvol/sage/sage-5.8/i686/local/lib/python2.7/site-packages/IPython/config/loader.py",
line 27, in
from IPython.utils.path import filefind, get_ipython_dir
File
"/zvol/sage/sage-5.8/i686/local/lib/python2.7/site-packages/IPython/utils/path.py",
line 21, in
from hashlib import md5
--
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..
Re: [sage-devel] Re: Patches overwriting patches in singular
So if we added GNU patch, and removed two of the many excess files from Python alone, we would save a few disk space. Is it actually an issue, how long sage builds? Why build gpatch if mercurial is built by default and would do the job? I don't understand you guys. Ralf -- 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: http://www.sagemath.org
Re: [sage-devel] Re: Patches overwriting patches in singular
Why would one need an extra 'patch' program? mercurial is a python program - python needs some patches, see a problem with using mercurial on its own? ??? Sage uses a patched python? And the python people don't want to fix these issues? OK, life is tough. Anyway, then restrict this copy mechanism to just python and perhaps mercurial if you also must patch mercurial. But all the other packages should just be using mercurial. Why spread this copy disease all over the place? And as for python, I would have the sources living in a hg repo with the patches directly living in a branch. When distributing the spkg, you simply distribute the sources of the modified branch. If ever somebody wants to have python without the patches (who would want that in the context of sage anyway?--one would probably clone the original python.org) that would be a simple branch switch, no? So not even here is patch or cp really necessary. Ralf -- 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: http://www.sagemath.org
Re: [sage-devel] Re: Patches overwriting patches in singular
On 06/30/2010 02:05 AM, Dr. David Kirkby wrote: On 06/30/10 12:54 AM, Tim Daly wrote: I'm surprised you don't use patch. Mercurial can generate patches. That would only be ok at the point Mercurial is built, so might be tricky. $SAGE_ROOT/sage/spkg/standard/deps says... all: $(INST)/$(SAGE_SCRIPTS) $(INST)/$(SAGE) \ $(INST)/$(EXAMPLES) $(INST)/$(GAP) $(INST)/$(SINGULAR) ^^^ $(INST)/$(MAXIMA) \ $(INST)/$(G2RED) $(INST)/$(LCALC) $(INST)/$(SYMPOW) $(INST)/$(MATPLOTLIB) \ $(INST)/$(GFAN) $(INST)/$(ECM) $(INST)/$(TACHYON) \ $(INST)/$(GIVARO) $(INST)/$(LINBOX) $(INST)/$(IML) \ $(INST)/$(SYMMETRICA) $(INST)/$(POLYBORI) \ $(INST)/$(GSL) $(INST)/$(GD) $(INST)/$(GDMODULE) \ $(INST)/$(MERCURIAL) $(INST)/$(TWISTED) $(INST)/$(TWISTEDWEB2) \ What about moving Mercurial some lines up? Then for the spkg, the src subdirectory would only contain a subdir .hg and nothing else. This would contain all the sources of the respective spkg which can then simply be extracted via 'hg update -C'. Building this src subdir just means to say hg init; hg add .; hg commit -m'singular-7.42.1' and remove everything except .hg. Now one could, of course use a branch and put the patches already into this .hg repo, but if you like to have them separate, put it into a patches directory and then use 'hg import'. Why would one need an extra 'patch' program? Ralf -- 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: http://www.sagemath.org
[sage-devel] maxima
I've just run a sage -upgrade which complained that some .fas file was not existing or too old. ;;; Internal error: Unable to find include directory ; - Binary file binary-ecl/maxima-package.fas is old or does not exist. ;Compile (and load) source file /home/hemmecke/software/sage-source/spkg/build/maxima-5.20.1.p0/src/src/maxima-package.lisp instead? y ; - Should I bother you if this happens again? So I thought maybe installing maxima as an spkg should work. But 'sage -i maxima' first extracts maxima and then downloads it again. Why? Can this be considered a bug? maxima-5.20.1.p0/src/src/trigo.lisp maxima-5.20.1.p0/src/src/comm.lisp maxima-5.20.1.p0/src/AUTHORS Finished extraction sage: After decompressing the directory maxima does not exist This means that the corresponding .spkg needs to be downloaded again. Searching for latest version of maxima Found package maxima-5.20.1.p0 http://www.sagemath.org//packages/optional/maxima-5.20.1.p0.spkg --> maxima-5.20.1.p0.spkg Finally gives the same error as above. Any hints how to continue? Ralf -- 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: http://www.sagemath.org
Re: [sage-devel] Re: shell commands in the notebook
>> 3. If you do not want to use virtual machine, at least do not run sage >> notebook under you account! > If you somewhat trust the 20 or so users, you can set accounts=True, > make their accounts, then set account=False before publishing so random > people won't be able to join. If you trust these people enough to given > them an user login to your machine, the extra complexity of a virtual > machine shouldn't be needed (just make a sageuser account with limited > permissions). I am currently thinking of letting those users call "sage -notebook" themselves. Interestingly, the notebook looks for a free portnumber. So that shouldn't be a problem. I just hope that portnumber thing also works for 30 users. Do you see any problem here. Everyone would work just on his account. Maybe I should forbid to set the "interface" option so that nobody opens a notebook to the world. Well, but sage is python, so there is always a way around for people with command line access. Ralf -- 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: http://www.sagemath.org
[sage-devel] %directive in sage-notebook
Sorry for crossposting, but I guess that topic should get a wider audience. Obviously that notebook has been very much tailored for having Sage as the standard session/system type. However, the notebook also allows to set the standard system type to some other system, for example to "axiom (optional)". Unfortunately, the input of the cells are then still parsed with having Sage syntax in mind, i.e. writing %sage 1+1 in a cell will evaluate it using sage. While the idea is OK, the syntax is not. PanAxiom, for example uses % and %%(n) to refer to previous input. Furthermore %pi and %i are the standard notations for pi and the imaginary unit. Obviously, I cannot enter things that start with %, if my session type is Axiom. Locally, I've modified cell.py so that the directives have to start with %%% instead of just one %. That would cure the problem, but is obviously not backward compatible and some (yet unknown) system might have a special meaning for %%% (for example Maple). A backward compatible change would allow the session type, i.e. in my case devel/sage/sage/interfaces/axiom.py to choose an appropriate prefix. Any suggestions how to fix that? Ralf -- 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: http://www.sagemath.org
Re: [sage-devel] shell commands in the notebook
Thanks. Looks like I rather want to use localhost. But I need it for about 20 users. What options do I have to give to "sage -notebook"? Ralf On 06/22/2010 01:58 AM, Robert Bradshaw wrote: > On Jun 21, 2010, at 4:47 PM, Ralf Hemmecke wrote: > >> What exactly has been done to prevent users of http://sagenb.org to do >> mischief on that server. >> >> It's easy to set the session type to "sh" and find out about the system. > > All worksheet processes run as (several) limited-privilege users within > a virtual machine. Of course more could be done, but that's at least > something. Also, Yoav Aner did a thesis on the securing of the Sage > notebook (available at http://sagemath.org/library-publications.html ). > > - Robert > > -- 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: http://www.sagemath.org
[sage-devel] shell commands in the notebook
What exactly has been done to prevent users of http://sagenb.org to do mischief on that server. It's easy to set the session type to "sh" and find out about the system. Ralf -- 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: http://www.sagemath.org
Re: [sage-devel] sagenotebook vs codenode
>> What is the relation between sagenotebook and codenode.org? > My understanding is that Codenode was supposed to be a generalized > Sage Notebook. OK, but that doesn't fully answer my question. From appearance they look similar. Do they have the same codebase? Was sagenotebook developed from codenode or vice versa? > The project is inactive. :-( > It does not support interacts Can you explain what you mean by "interacts"? > and can not be used within Sage like Sage Notebook. ??? I thought the sagenotebook is an interface to sage (unfortunately needs quite some part of sage to run). From what you say it sounds as if Sage is used to program the notebook. True? Shouldn't there be a clean API? Why does Alex say in http://groups.google.com/group/codenode-devel/browse_thread/thread/9541cfc34db09a61 "My recommendation is to focus on the Sage notebook right now, it is the most usable." ? It obviously means that the sage notebook is more powerful. But what are the better features? Why cannot they easily be ported to codenode? Could someone also comment on another passage from the above thread: "The aim of Codenode is to make a "generalized notebook" that could be used by all these projects, but in practice it turns out that is an *extremely* large amount of work." What exactly is this large amount of work? There is certainly some part of sage that works on the input that comes from the notebook. But shouldn't all that count as "backend" for the notebook? Ralf -- 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: http://www.sagemath.org
[sage-devel] sagenotebook vs codenode
What is the relation between sagenotebook and codenode.org? Ralf -- 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: http://www.sagemath.org
[sage-devel] axiom.py
The last few lines in the _eval_line function of
devel/sage/sage/interfaces/axiom.py look like
outs = out.split("\n")
i = 0
outline = ''
for line in outs:
line = line.rstrip()
# print "'%s'"%line
if line[:4] == ' (':
i = line.find('(')
i += line[i:].find(')')
if line[i+1:] == "":
i = 0
outs = outs[1:]
break;
out = "\n".join(line[i+1:] for line in outs[1:])
return out
That's obviously buggy as can be seen at the output of )version at
http://sagenb.org/home/pub/2158/.
The first "i = 0" should become "i = -1"
The second thing I don't understand is:
(*)
if line[i+1:] == "":
i = 0
outs = outs[1:]
That sounds like... If the line only contains the axiom prompt "(123)"
and nothing else then the first line is removed. If a string like
" (1)" by accident appears in the middle of an axiom output the first
line is removed?
Actually it is already enought that " (" starts a line in the output
stream. The for loop will be aborted. What is the rationale here?
Even worse. I don't think that changing the value of the list one
iterates over, is a good idea. Checkout...
r = range(5)
r.reverse()
for i in r:
print i,r
if i == 2:
r.remove(3)
Can somebody tell me, why (*) is there at all?
Ralf
--
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: http://www.sagemath.org
Re: [sage-devel] Re: Sage-Notebook file format
On 06/18/2010 01:55 PM, ma...@mendelu.cz wrote: > Hi, sws it is gzipped (or bzipped) tar fille. Unzip, untar and bzipped and tarred... ;-) OK that helps. Thanks. > you should see text version and directories, one subdirectory for each > output cell. Yes. But the output cell directories are empty. Why? All data seems to be in worksheet.txt and worksheet.html, though. Now, the .txt and .html file are different only in the first two lines. Since the .txt file contains more information, I guess, that is the master file. Now if I edit the .txt file (and leave the .html file as is) then tar and bzip again, what should I get? Or am I simply not supposed to fiddle with that textfile? (Suppose I only want to change the order of two cells.) What's the way to go? Ralf -- 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: http://www.sagemath.org
[sage-devel] Sage-Notebook file format
Hello, I realized that the .sws File of a notebook is not a text file. Would it be hard to also provide a text format that one could edit with any editor? What I see, when I press the "Edit" button already doesn't look too bad. Also when pressing the "Text" button, the notebook shows nice txt. (Although it shows "sage: " in front of a command even if the session type is gap or maxima.) Ralf -- 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: http://www.sagemath.org
Re: [sage-devel] moving Sage directories
On 06/10/2010 04:49 PM, Jason Grout wrote: > There seem to be a lot of loose ends left hanging when a sage directory > is moved. For example, I usually compile Sage on a ramdisk, and then > move it to my home directory. [snip] > It seems common knowledge in Sage that you can compile Sage and move the > directory around to your heart's content. Maybe we should put a warning > somewhere cautioning people that there are lot of packages included in > Sage, and Sage might not automatically change the right directory > information for every package? > This seems like a goldmine for possible subtle bugs... :-) Ralf -- 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: http://www.sagemath.org
[sage-devel] Standalone SageNotebook
Hello, The for the source code repository on http://nb.sagemath.org/ points to sage -hg pull http://boxen.math.washington.edu:8100 sage -hg update ../sage -python setup.py install But running hg clone http://boxen.math.washington.edu:8100 results in abort: error: Connection refused 1) Is there an "official" sagenb repository that is used to produce the corresponding .spkg for sage? 2) How standalone is the sage notebook? What else do I need to run the notebook? From what I read in "sagenb-0.7.5.3/spkg-install", it gives the impression as if Sage is not really needed. Is that true? 3) Where do I find the corresponding code documentation? I am interested in particular in an overview of the code. Ralf -- 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: http://www.sagemath.org
Re: [sage-devel] SEP
> For the reasons Robert Bradshaw mentioned, I don't think the AutoTools > SEP makes a lot of sense for Sage. Robert also added "Automake would add another level of complexity to the build process, in particular one which is not understood by many in the community." to http://wiki.sagemath.org/AutoToolsSEP. How many people understand Sage's build process? Would be interesting to have a poll on that. An ordinary developer would never have to deal with automake/autoconf. He/she would not even have the need to install autotools on their computer. (Although it is not a big deal to install them with newer linux distributions.) >> http://wiki.sagemath.org/UnifiedCommandLineSEP > > Perhaps this has already been adequately addressed by recent work of > John Palmieri: > > http://trac.sagemath.org/sage_trac/ticket/21 Why do you think have I cited exactly that link at http://wiki.sagemath.org/UnifiedCommandLineSEP ? Ralf -- 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: http://www.sagemath.org
Re: [sage-devel] SEP
>> http://wiki.sagemath.org/AutoToolsSEP > My primary concern with both of these proposals is that they seek to > widen the gap between developers and users, Huh? > and I think a huge part of Sage's success in attracting contributors > is erasing that gap. Sage is not a sucess for me as I stumple from bug to bug. > Want to fix a bug? Just edit the source, type "sage -br", and you're > good to go. Want to fix a bug? Just edit the source, type "make && make install" and restart sage. > A little bit more about revision control, and you've got > a patch up on trac. Oh, you've forgotten to create an account and login, reading the trac guidelines and figuring out what trac is all about. ;-) > All of this (fortunately) requires no knowledge > of autoconf/make/setup.py/environment variables/paths/etc. Ehm, does calling "make && make install" or even "./configure && make && make install" require you to know about the existence of autotools/automake? Do you know that the standard packages mpir and gnutls use automake+autoconf. http://git.savannah.gnu.org/cgit/gnutls.git/tree/Makefile.am http://boxen.math.washington.edu/svn/mpir/mpir/trunk/Makefile.am There are probably more of this sort. Still, someone that installs mpir doesn't need to have autoconf or automake installed on his/her computer. Why? Read the documentation of autoconf. Cannot just everyone from sage-devel think about requirements for the build process and write that down at http://wiki.sagemath.org/AutoToolsSEP or http://wiki.sagemath.org/UnifiedCommandLineSEP ? Having proper requirements would already be a step forward of cleaning up, right? I actually don't understand why there is so much opposition against autotools. Three people replied so far, three times it's against. Is it because the build-system of sage is already perfect and I just cannot see it? Then it's just me and I must live with the fact that sage doesn't work as expected for me. Ralf -- 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: http://www.sagemath.org
Re: [sage-devel] SEP
>> http://wiki.sagemath.org/AutoToolsSEP > > One problem with that is that too many packages in Sage do not honor > things like CC, MAKE, CXX. Cython misbehaves if CFLAGS set. What does that have to do with autotools? If the subpackages misbehave then one has to provide proper fixes with or without autotools, right? > So any hope of using autoconf/automate and thinss working as those > packages intend will fail. So you will never get a conventional > autoconf/automake build process. Right! Computers will *never* be able to deal with anything but numbers. Of course sage might never have autotools. Not because it doesn't work, but rather because some people hear autotools and are already against. Sage builds gnutls and mpir as standard spkgs. Both of them use autotools. Why haven't you realized it? And why will no user ever realize it? > It would probably be even more confusing, as people would expect Sage > to build like other packages. Exactly, I expect, "./configure && make && make install". Who wouldn't? Ralf -- 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: http://www.sagemath.org
Re: [sage-devel] sage path bug
>> today, running "./sage -t filename" did not succeed on my system. After >> a while, I could figure out with some help of Burcin that my setup of >> sage was too much using symbolic links. In fact, after I removed "sage" >> from being available via PATH, the above command succeeded. > Could you elaborate? Can you tell me what you need? If I invest any time in figuring out a proper bug description, I'll probably find and fix the bug myself. The problem is that with every call of sage (and sub-scripts) sage tries to figure out what SAGE_ROOT is. I haven't set SAGE_ROOT. (Why should I clutter up my environment? I expect sage to work properly without setting SAGE_ROOT.) I consider this behaviour of sage wrong by design, so I wrote a SEP. But that's just me and so I'll shut up. Ralf -- 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: http://www.sagemath.org
[sage-devel] SEP
Hello, today, running "./sage -t filename" did not succeed on my system. After a while, I could figure out with some help of Burcin that my setup of sage was too much using symbolic links. In fact, after I removed "sage" from being available via PATH, the above command succeeded. Since that is not the first time I run into that problem, I started to write two SEPs. http://wiki.sagemath.org/AutoToolsSEP http://wiki.sagemath.org/UnifiedCommandLineSEP I'd be happy if some of you could comment on it and improve that pages. Before any implementation starts, there should be a clearer specification. --Ralf -- 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: http://www.sagemath.org
Re: [sage-devel] Re: sage -advanced
Hi John, > See trac ticket #21. Your help looks great. Why isn't it the sage default? What's the procedure to get it into a new release? Ralf -- 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: http://www.sagemath.org
Re: [sage-devel] Re: sage -advanced
BTW, is there some reason why the -advanced output doesn't use an 80 character line length. It's really hard to read if the lines wrap. > > Even dumb (serial) terminals have 132 column mode ;-) > And screens tend to get bigger and wider, so I consider 80 cols a bit > obsolete. I don't belong to the category of people who prefer books in landscape mode. ;-) > (Mails and newsgroup posts are a bit different.) You contradict yourself. Ralf -- 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: http://www.sagemath.org
Re: [sage-devel] sage -advanced
Thanks Minh, for your suggestions. In fact, I wouldn't have expected that simply typing "sage -docbuild" gives a nice help. In fact, sage is not quite consistent here. "sage -b" does actually do something. Would be nice if there were a system so that, for example, "sage -h -some-option" would give a longer explanation of how to use that option. In some sense it should be like "hg help", "hg help update". Just a suggestion... First, of course, sage should have long options only with double dash. The usual convention would be --docbuild, no? >> In fact, to me it's a bit unclear what I can actually put as >> "lang" and . > > A better help message would also include how to get help on all > options for docbuild. Yes, good suggestion. >> BTW, is there some reason why the -advanced output doesn't use an >> 80 character line length. It's really hard to read if the lines >> wrap. > That is an issue that a lot of files in the Sage library (and > elsewhere) don't attend to. I personally like to have no more than 80 > characters per line. But in some cases, I would make an exception. > But that's my personal preference. Then maybe all developer should re-read what http://www.sagemath.org/doc/developer/conventions.html#python-coding-conventions says quite at the beginning... http://www.python.org/dev/peps/pep-0008/ == Maximum Line Length Limit all lines to a maximum of 79 characters. == Maybe patches on trac should not be approved, if the guidelines are not followed. ;-) (Oh, yes, I know that sage-sage is a bash-script.) Ralf -- 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: http://www.sagemath.org
[sage-devel] sage -advanced
Hello, Looking at the output of "sage -advanced", I couldn't see an explanation of "-docbuild". Unfortunately, I cannot provide a better patch than the one below. In fact, to me it's a bit unclear what I can actually put as "lang" and . If there were some more explanation of every option, I'd highly appreciate it. Or is there somewhere (maybe on the web) a description of *all* the options and additional switches to "-docbuild"? BTW, is there some reason why the -advanced output doesn't use an 80 character line length. It's really hard to read if the lines wrap. Ralf >hg diff sage-sage diff -r f0a419b928ec sage-sage --- a/sage-sage Fri Mar 19 20:28:19 2010 -0700 +++ b/sage-sage Thu May 27 16:49:25 2010 +0200 @@ -47,6 +47,7 @@ echo " -coverage -- give info about doctest coverage of files" echo " -coverageall -- give summary info about doctest coverage of all files in the Sage library" echo " -crap sage-x.y.z.tar -- detect suspicious garbage in sage source distro" +echo " -docbuild [lang/] html|pdf|... -- Builds the Sage documentation" echo " -ecl [...]-- run Common Lisp" echo " -experimental -- list all experimental packages that can be downloaded" echo " -gap <..> -- run Sage's Gap with given arguments" -- 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: http://www.sagemath.org
Re: [sage-devel] Re: numerically stable fast univariate polynomial multiplication over RR[x]
On 05/04/2010 12:16 AM, Bill Hart wrote: [snip] > But I was surprised at how much difference it made to the debugging > time. I made the same experience. Literate programming is not only beneficial for the people who read the literate program, but if the matter is complex enough, it's also good for the original programmer. (But I shut up now. Some things one must discover by oneself. Unfortunately there is always this hurdle to actually start trying something out.) Ralf > On May 3, 10:04 pm, Tim Daly wrote: >> Bill Hart wrote: [snip] >>> Another thing I've been enjoying lately is literate programming. >>> Amazingly it turns out to be faster to write a literate program than >>> an ordinary program because debugging takes almost no time. -- 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: http://www.sagemath.org
[sage-devel] FriCAS in Sage
Does somebody know whether (and how) I can convince Sage to work with an existing FriCAS (compiled with sbcl) instead of compiling+installing the fricas.spkg? Ralf -- 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: http://www.sagemath.org To unsubscribe from this group, send email to sage-devel+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
Re: [sage-devel] Re: Randomised testing against Mathematica
If this is a call for a vote ;-), let me tell that I completely agree with the point of view that in an ideal world, tests should be written *before* the code and by a *different* person (extreme/peer programming). In an ideal world test would be extracted from theorems of theoretical papers. Automatically! And before coding starts. Code would be generated from the mathematical theory at least semi-automatically. Florent, I have the feeling that your ideal world is not ideal enough for me. ;-) Ideally, even routine theory is generated by a computer. We should strive for a world where mathematicians just can concentrate on the creative part of mathematics. Computers are our slaves (until they become so intelligent to take over ;-) ...) But I am not sure I understand the importance of this thread. If someone writes some code that tests Sage functions against equivalent routines of commercial software, then why not just run these tests and instead (or even additionally) include the hard-coded results of the respective system into a Sage-testsuite? Thus the dependency on the commercial system is not there and Sage profits from having more tests. I'm however not sure about the quality of such tests. If they are just random, they will most probably only rarely find corner cases in contrast to well designed testsuites. Yes, yes, I know, nobody has time to write tests Just my 0.7 cents. Ralf -- 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: http://www.sagemath.org
Re: [sage-devel] Optional packages online
On 12/17/2009 07:56 PM, mhampton wrote: > I just noticed that the optional package repository on > > http://www.sagemath.org/packages/optional/ > > has at least on error - the biopython package is quite out of date, it Same for FriCAS. It should be fricas-1.0.8. http://trac.sagemath.org/sage_trac/ticket/6517 Who is going to upload the package to "optional"? Ralf -- 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: http://www.sagemath.org
[sage-devel] Re: testing all optional spkg's
>> Since you are *not* distributing the programs together, I don't see how >> the GPL applies. The *user* is the one that is running the command to >> download the non-gpl program, and all linking or other dependencies are >> happening on the user's machine, at their request. The result is not >> being distributed. > > *Technically* this may be legal because currently I'm not distributing > the binary with both spkg's prebuilt. > However, I still do not at all feel comfortable with such > distribution. In fact, I generally would like to very strongly > discourage anybody from creating any so-called GPL'd spkg (or other > programs) that cannot be built without linking in a GPL-incompatible > non-system library during **compile time**. Though perhaps > technically legal, this is against my understanding of the spirit of > the GPL and certainly not good for the free software ecosystem. Are you suggesting, that such a program should best not be written at all? No matter how useful it might be for a bunch of people? I understand your position, though. The problem actually is the non-free program not the GPL code. ;-) Ralf --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: testing all optional spkg's
> Regarding: "I was told that a GPL package must not install a non-GPL package."
>
> The above can never legally come up, right? If a program Foo is "GPL"
> and fundamentally depends on a program Bar that is licensed
> GPL-incompatible, then distributing Foo at all violates the GPL right?
No. Can you prove that by specifically pointing to the sections of the GPL?
Let's say I write a program A and just distribute that as binary for any
platform you like. (It's propriety... I'll never show you the source,
but you can have free binaries. == Hypothetical license.)
Let's say I write a program B which heavily depends on/links to A. I
distribute the source code of B on my website under the terms of the GPL.
Tell me the section of the GPL that would force me to give you the
sources of A! Note: I don't distribute B as a binary. (Of course, if I
do that, it includes A and thus A would fall under the GPL.)
You just get sources from me. I don't even claim that B is a "program".
I just distribute a collection of source files. So what?
> Regarding: "so I attempt to install them with "sage -i" in the
> spkg-install script. The bad thing is I hard-code the package
> numbers, so that will break if they are updated."
>
> Don't do that. Instead do this:
>
> sage -c "install_package('package_name')"
>
> without the version number. The "install_package" command in the Sage
> library automatically determined the most recent version of a package.
Everyone knows that this is dangerous, too. It might be that a package
needs a certain version of its dependency and does not work properly
with the newest version.
Look at zc.buildout for package management.
Ralf
--~--~-~--~~~---~--~~
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: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: testing all optional spkg's
> There is work being done on FriCAS at > http://trac.sagemath.org/sage_trac/ticket/6517. > The work on FriCAS-1.0.8 is a bit delayed due to troubles with the > aldor interface. I don't know what the status is but the intent is to > make two packages. Ehm... I can't remember why it shouldn't work to compile the fricas-1.0.8.spkg _now_ using http://boxen.math.washington.edu:29792 (look at the above ticket for clearer instructions). The real showstopper is the aldor interface. But as far as I remember, compiling fricas-1.0.8.spkg and fricasaldor-1.0.8.spkg should work. One need not upload fricasaldor to http://sagemath.org/packages/optional/ if it doesn't work. (And it doesn't work. In particular not on sage.math.) For the moment fricas-1.0.8.spkg should do. Just svn co https://fricas.svn.sourceforge.net/svnroot/fricas/releases/1.0.8 fricas-src and use that directory as FRICAS_SRC=... for http://boxen.math.washington.edu:29792 . If anything goes wrong, I'm happy to help, but I did not plan to devote time to it this or next weekend. Ralf --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: sqrt(2) is real or not
> Should I expect > > sage: SR(1) + SR(2) > 1 + 2 > > just because > > sage: SR(x) + SR(2) > x + 2 And why would "1 + 2" be wrong/bad or whatever? Can you give a suggestion what I must input to sage to exacly get an expression 1+2 in sage, i.e. an expression tree + / \ 1 2 ? It all depends on what the specification of "Symbolic Ring" is. If one defines it as a term algebra, then no simplification is even possible. Most people wouldn't like that, but shouldn't a system give predictable results? One should be able from the specification of "Symbolic Ring" to figure out what the result of SR(1) + SR(2) or sqrt(2) > 1 is without touching a computer. Would someone disagree? Don't come with the argument that one cannot predict the result of random()... True, but one can probably give a specification of the properties of such a random() function. I agree that giving proper specifications is a lot of work, but how else could one prove that an arbitrary test is giving the right result? Just because one has already given finitely many test? BTW, the docstring for symbolic ring is: Symbolic Ring, parent object for all symbolic expressions. Isn't the expression tree above a "symbolic expresssion? What is a "symbolic expression"? Ralf --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: sqrt(2) is real or not
> Symbolic Ring > sage: SR(1) > SR(2) > 1 > 2 > because it returns: > sage: x > 2 > x > 2 > if x is symbolic. Right. And of course it doesn't say whether that is true or false. That's just an expression. Only when one asks to transform that into a boolean value, computation is started. Challenge: What truth value would one expect for sqrt(-1) > 1? It all depends on where one lives. No? Ralf --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: deprecation policy
> How does WRI "support deprecated code"? And for how long? One difference between a company like WRI and the Sage project is that WRI charges for its product to get money to do (among other things) maintenance of old versions or caring about upgrade procedures. A pragmatic approach for Sage is: If there are enough resources then old code can be supported, if not then not. Even though I am very much for free an open software, if there are no resources then the project cannot care too much about legacy code. Sage is mostly done by volunteers. Nobody (except the people paid for working on Sage) can be forced to care about things that he/she is not interested in. BTW, free (in the sense of the GPL) does not mean gratis. Of course, it would be good to help users to make a smooth transition from one version to another, but caring too much about 10-year-old versions removes resources from progressing Sage. Just my two cents. (Maybe it was just one.) Ralf --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage registered trademark
> We will not be changing the name to MathTor. > > -- William Has someone already bothered to ask the people at one of the following sites whether they intend to sue Sage (at sagemath.org) or rather its leader in the future? http://sage.com/ http://www.sagefinancial.co.uk/ http://www.sagetrust.com/ http://www.fdsystems.co.uk/sage-software ... Ralf --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: deprecation policy
What about deprecation warning and moving the deprecated functionality to an optional package in the next version of Sage with a clear notice that there is no official support for this optional package. Ralf --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage env -- RM="rm"?
Though pretty much unix-related, I find this a good rule of thumb. http://www.gnu.org/software/make/manual/make.html#Utilities-in-Makefiles But otherwise there should be "configure" to figure out the machine differences. Ralf On 10/20/2009 12:04 PM, David Kirkby wrote: > Only a few days ago you agreed we would not have RM, CP and other very > basic commands set as environment variables. > > IMHO, if someone wants 'rm -f' they should type it. Looking in the > packages now, 95+% of people use 'rm' or 'rm -f' rather than '$(RM)" > so I think it would be better to drop the use of such an environment > variable. > > Dave --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] [sage-combinat-devel] Re: Categories review: algebra_ideals.py and algebra_modules.py
> Is there any real reason to use "Modules(R)" as "Bimodules(R,R)" > beyond the comfort of not changing the names? If not, I'd strongly > suggest forgetting the name "Modules" for noncommutative rings or > default it to left modules. Oh, interesting that you say that. That is exactly what PanAxiom is doing: Module(R:CommutativeRing): Category == BiModule(R,R) add if not(R is %) then x:%*r:R == r*x Module(R) can only be instatiated if R is a commutative ring. To make it more clear: (1) -> S2:=SquareMatrix(2, Integer) (1) SquareMatrix(2,Integer) Type: Domain (2) -> SparseUnivariatePolynomial(S2) has Module(S2) Module(S2) is not a valid type. Isn't that what you want? Maybe you should use FriCAS. ;-) Ralf --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: [sage-combinat-devel] Re: Categories review: algebra_ideals.py and algebra_modules.py
Could you elaborate. I would like to understand why the statement that "every module is a bimodule" is not acceptable. In PanAxiom we have BiModule(R:Ring,S:Ring):Category == Join(LeftModule(R), RightModule(S)) Module(R:CommutativeRing): Category == BiModule(R,R) add if not(R is %) then x:%*r:R == r*x What does that have to do with ideal=twosided ideal vs. submodule!=twosided submodule (or whatever the problem is)? Ralf On 10/15/2009 03:16 PM, Nicolas M. Thiery wrote: > On Wed, Oct 14, 2009 at 08:34:46AM -0700, javier wrote: >> Positive review for algebra_ideals. > > Thanks. > >> With respect to algebra_modules, we have again the problem of >> commutativity. Whilst it makes sense to simply say "ideals" for two- >> sided ideals, this is not the case for modules: I don't know of >> anybody using "modules" to refer to "bimodules". >> >> Any other opinions here? > > No opinion myself except lazyness to change without good reason :-) > In MuPAD/Axiom, Modules(R) was a subcategory of BiModules(R). > See e.g. http://daly.axiom-developer.org/dotabb.html --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] fricas-aldor-spkg
I've just added http://trac.sagemath.org/sage_trac/ticket/6517#comment:17 (and 18) Could someone please test this? Thank Ralf --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
