[sage-devel] Re: How to build patch for documentation
ancienthart writes:
> Hi guys, wanted to have a crack at the following trac ticket.
> http://trac.sagemath.org/sage_trac/ticket/9824
> Basically the documentation at http://www.sagemath.org/doc/reference/sage/
> calculus/desolvers.html#sage.calculus.desolvers.desolve_system
> needs to be changed so that it's clear what form ics needs to be entered in.
>
> So what I'm asking, is there a clear tutorial or list of instructions on how
> to
> create a patch for the official documentation?
You need to edit $SAGE_ROOT/devel/sage/sage/calculus/desolvers.py around
line 679, where there is a documentation string ("docstring") associated
to the function desolve_system(). After you have done so, you need to
create a patch (preferably using Mercurial) and upload it to the trac
ticket. The developer guide should tell you how to do that.
-Keshav
Join us in #sagemath on irc.freenode.net !
--
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] weird version issue
On Thu, 12 Apr 2012 at 09:06PM +0100, John Cremona wrote: > Looking at the install log I first saw the message "Installing GCC > because your 'gcc' is not so recent." The same message is used when you have gcc 4.6.1, which is quite recent. The message also appears when building the documentation, when of course it is not installing gcc at all. Ticket #12825 is relevant here. I'm not sure about your LD_LIBRARY_PATH issues, though. Dan -- --- Dan Drake - http://mathsci.kaist.ac.kr/~drake --- signature.asc Description: Digital signature
[sage-devel] Attn: Confidential
Hello, How are you doing today? I know this might be a surprise to you but am sorry to reach out to you in this manner. I apologize for not informing you about my travel to Scotland for a workshop on financial optimization. Everything is going fine but there's a little problem, I misplaced my wallet on my way back to the hotel and right now all my credit cards and money are gone. Am sending you this message to inform you that am stranded at the moment and need your help financially. Am not sure if you have that much but will you be able to help me with a loan of $1,450 dollars to sort-out my hotel bills and get myself back home. I promise to pay you back as soon as i return. I'm am sorry for the inconvenience this message might cause you but please understand that am in a very bad situation right now. I will appreciate whatever you can assist me with. Please let me know if i should e-mail my details and location for the money. Best regards Joachim Dahl -- 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: Julia
Hi! On 12 Apr., 16:41, rjf wrote: > OMG I put in an extra space and my indentation is wrong. Somewhere. I > wonder where? +1. One of my first Sage patches was about fixing a wrong indentation that resulted in some line of code not being executed. Cheers, Simon -- 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] weird version issue
I may be going mad but: I just built sage-5.0.beta13 on a machine where I had not built sage since 4.7. It went fine, apparently. Without changing directories after the build finished I typed ./sage and was surprised to see the banner for 4.7 appeared. Looking at the install log I first saw the message "Installing GCC because your 'gcc' is not so recent." which is a little surprising (the machine has gcc-4.3.4 and is Suse linux; it's the front-end to a big cluster). I also saw that LD_LIBRARY_PATH was set (by me in a startup script) to include $HOME/sage-4.7/local/lib . But the paths in the install log have sage-5.0.beta13. I guess I should unset that LD_LIBRARY_PATH and build it again? But is this an indication of some issue which needs to be looked at? John -- 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: Julia
On Apr 12, 2:47 am, Volker Braun wrote: > In other words, the reason why many programmers don't like lisp is > * OMG I forgot a closing parenthesis, where is it actually, a proper editor for lisp keeps the parentheses well in hand. Personally I find it quite convenient to see the automatically computed and displayed reinforcement of both parentheses and pretty-printed indentation that one gets automatically by using emacs or one of the lisp IDEs. I could say, of python programmers .. OMG I put in an extra space and my indentation is wrong. Somewhere. I wonder where? > * my parentheses keys have worn off Hardly an issue, though you could perhaps make a case that parentheses on a keyboard are in an inconvenient place. This used to be an issue when the IBM-selectric standard and the Teletype standard put parentheses in different locations relative to the "home row". But now the locations are pretty much standard in the keyboards I see. (Not sure about non-Western keyboards though.) Apologies for giving you a longer response than you warrant, straight-faced... > * can't time with sub-millisecond accuracy OK, I ran the program 100 times to get something detectable. 0.0014 sec, Faster than Julia or Cython, ignoring differences in computer speed etc. > * uncaught exceptions > Huh? Why can't lisp catch exceptions? Read about the error handler, as well as catch and throw. Programming language designers and implementors tend to screw up on things like exception handling, setting traps, and other flags. I don't know if Python allows you to, for example, set floating-point inexact to cause an exception, or to set rounding modes. It's not part of the ANSI lisp standard, but I can't speak for all the implementations. RJF -- 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: How to build patch for documentation
On Apr 12, 9:57 am, ancienthart wrote: > Hi guys, wanted to have a crack at the following trac > ticket.http://trac.sagemath.org/sage_trac/ticket/9824 > Basically the documentation > athttp://www.sagemath.org/doc/reference/sage/calculus/desolvers.html#sa... > needs to be changed so that it's clear what form ics needs to be entered in. > > So what I'm asking, is there a clear tutorial or list of instructions on > how to create a patch for the official documentation? Same as any other patch, because they come from the code. Does http://www.sagemath.org/doc/developer/walk_through.html help? -- 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: OS X 10.7 testing again
> I will try again after installing the latest version: > XCode 4.3.2 and ctools_late_march12 Update. Same problem make[1]: *** [installed/ecm-6.3.p4] Error 1 -Bruce On Apr 11, 6:11 pm, Bruce Cohen wrote: > I've borrowed a new Mac Air from and installed the following > MacOS 10.7.3, XCode 4.2, ctools_february12 > > I get the same result: > CC=clang > > make[1]: *** [installed/ecm-6.3.p4] Error 1 > > real 94m44.538s > user 82m42.887s > sys 10m53.847s > Error building Sage. > make: *** [build] Error 1 > $ clang --version > Apple clang version 3.1 (tags/Apple/clang-318.0.45) (based on LLVM > 3.1svn) > Target: x86_64-apple-darwin11.3.0 > Thread model: posix > > I will try again after installing the latest version: > XCode 4.3.2 and ctools_late_march12 > > I'm interested in knowing exactly which versions of Xcode and command > line tools actually produce a clean compile. > > I'll report back. > > Thanks. > > -Bruce > > On Apr 11, 6:21 am, Simon Wyatt wrote: > > > > > > > > > I have the exactly the same error as Bruce on a brand new MacBook Pro > > that came out of the box last Friday and has a fresh install of the > > newest XCode, without having migrated any remnants of old XCodes from > > any other computer. > > > MacOS 10.7.3, XCode 4.3.2 > > > $ clang --version > > Apple clang version 3.1 (tags/Apple/clang-318.0.58) (based on LLVM > > 3.1svn) > > Target: x86_64-apple-darwin11.3.0 > > Thread model: posix > > > My ecm-6.3.p4.log is practically identical to his. > > > On Apr 11, 8:28 am, Bruce Cohen wrote: > > > > On Apr 10, 11:36 pm, Jeroen Demeyer wrote: > > > > > On 2012-04-11 05:33, Bruce Cohen wrote:> I believe that I am running > > > > the latest Xcode 4.3.2 > > > > > Are you sure? I have only seen this error with *older* XCode versions. > > > > I ran the make again last night using clang, get the same error, and > > > the clang version is newer than David's. That said, this machine > > > probably has remnants of Xcode's from earlier versions of OSX. Any > > > ideas on how to clean my machine? > > > > Thanks. > > > > -Bruce > > > > bash-3.2$ export CC=clang > > > > > > > make[1]: *** [installed/ecm-6.3.p4] Error 1 > > > > real 98m29.674s > > > user 82m6.097s > > > sys 11m35.524s > > > Error building Sage. > > > make: *** [build] Error 1 > > > bash-3.2$ clang --version > > > Apple clang version 3.1 (tags/Apple/clang-318.0.58) (based on LLVM > > > 3.1svn) > > > Target: x86_64-apple-darwin11.3.0 > > > Thread model: posix -- 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: Julia
Julia is, at the moment, my favourite programming language. It uses LLVM as the back end for speed. It is a dynamic language like Python, but to make it really fast they use dynamic type inference behind the scenes. The compiler is insanely clever. Moreover, unlike Cython, Julia has an interactive prompt. Yes, it is as fast as C, but dynamic and interactive! It is trivial to call compiled C code from Julia too. It also has a very active community and has generated a lot of interest recently. If Julia had existed back when Sage started, I would contend that it would have been a reasonable choice for language to use for Sage. I can't think of any other language I would say that about. Bill. On Apr 11, 4:15 pm, kcrisman wrote: > Apparently a new scientific computing language... > > http://www.r-bloggers.com/julia-i-love-you/ -- 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] How to build patch for documentation
Hi guys, wanted to have a crack at the following trac ticket. http://trac.sagemath.org/sage_trac/ticket/9824 Basically the documentation at http://www.sagemath.org/doc/reference/sage/calculus/desolvers.html#sage.calculus.desolvers.desolve_system needs to be changed so that it's clear what form ics needs to be entered in. So what I'm asking, is there a clear tutorial or list of instructions on how to create a patch for the official documentation? Joal Heagney -- 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: OS X 10.7 testing again
I don't really know what's going on, I was hoping it would be as simple as "make", but it failed for me too. Error installing package ecm-6.3.p4 Please email sage-devel (http://groups.google.com/group/sage-devel) explaining the problem and including the relevant part of the log file /Users/pdehaye/Software/sage-5.0.beta13-lion/spkg/logs/ecm-6.3.p4.log Describe your computer, operating system, etc. If you want to try to fix the problem yourself, *don't* just cd to /Users/pdehaye/Software/sage-5.0.beta13-lion/spkg/build/ecm-6.3.p4 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 '/Users/pdehaye/Software/sage-5.0.beta13-lion/spkg/build/ecm-6.3.p4' && '/Users/pdehaye/Software/sage-5.0.beta13-lion/sage' -sh) When you are done debugging, you can type "exit" to leave the subshell. make[1]: *** [installed/ecm-6.3.p4] Error 1 I am running XCode 4.3.2, and my clang --version returns Apple clang version 3.1 (tags/Apple/clang-318.0.45) (based on LLVM 3.1svn) Target: x86_64-apple-darwin11.3.0 Thread model: posix I have put the logs at http://www.math.ethz.ch/~pdehaye/logs/ Thanks for your work so far! Paul On Thursday, April 12, 2012 3:54:15 AM UTC+2, John H Palmieri wrote: > > > > On Tuesday, April 10, 2012 2:11:13 AM UTC-7, Jeroen Demeyer wrote: >> >> Please build the following source tarball from source on OS X 10.7: >> >> http://boxen.math.washington.edu/home/jdemeyer/release/sage-5.0.beta13-lion/sage-5.0.beta13-lion.tar >> >> I have included a few fixes, now *hopefully* it should work for everybody. >> >> Report success and failure, include the output of >> $ clang --version >> > > Works for me (with SAGE_CHECK=yes) on two different machines: > > $ clang --version > Apple clang version 3.1 (tags/Apple/clang-318.0.45) (based on LLVM 3.1svn) > Target: x86_64-apple-darwin11.3.0 > Thread model: posix > > $ clang --version > Apple clang version 3.1 (tags/Apple/clang-318.0.58) (based on LLVM 3.1svn) > Target: x86_64-apple-darwin11.3.0 > Thread model: posix > > Both are with the most recent Xcode. > > -- > John > > On Thursday, April 12, 2012 3:54:15 AM UTC+2, John H Palmieri wrote: > > > > On Tuesday, April 10, 2012 2:11:13 AM UTC-7, Jeroen Demeyer wrote: >> >> Please build the following source tarball from source on OS X 10.7: >> >> http://boxen.math.washington.edu/home/jdemeyer/release/sage-5.0.beta13-lion/sage-5.0.beta13-lion.tar >> >> I have included a few fixes, now *hopefully* it should work for everybody. >> >> Report success and failure, include the output of >> $ clang --version >> > > Works for me (with SAGE_CHECK=yes) on two different machines: > > $ clang --version > Apple clang version 3.1 (tags/Apple/clang-318.0.45) (based on LLVM 3.1svn) > Target: x86_64-apple-darwin11.3.0 > Thread model: posix > > $ clang --version > Apple clang version 3.1 (tags/Apple/clang-318.0.58) (based on LLVM 3.1svn) > Target: x86_64-apple-darwin11.3.0 > Thread model: posix > > Both are with the most recent Xcode. > > -- > John > > On Thursday, April 12, 2012 3:54:15 AM UTC+2, John H Palmieri wrote: > > > > On Tuesday, April 10, 2012 2:11:13 AM UTC-7, Jeroen Demeyer wrote: >> >> Please build the following source tarball from source on OS X 10.7: >> >> http://boxen.math.washington.edu/home/jdemeyer/release/sage-5.0.beta13-lion/sage-5.0.beta13-lion.tar >> >> I have included a few fixes, now *hopefully* it should work for everybody. >> >> Report success and failure, include the output of >> $ clang --version >> > > Works for me (with SAGE_CHECK=yes) on two different machines: > > $ clang --version > Apple clang version 3.1 (tags/Apple/clang-318.0.45) (based on LLVM 3.1svn) > Target: x86_64-apple-darwin11.3.0 > Thread model: posix > > $ clang --version > Apple clang version 3.1 (tags/Apple/clang-318.0.58) (based on LLVM 3.1svn) > Target: x86_64-apple-darwin11.3.0 > Thread model: posix > > Both are with the most recent Xcode. > > -- > John > > On Thursday, April 12, 2012 3:54:15 AM UTC+2, John H Palmieri wrote: > > > > On Tuesday, April 10, 2012 2:11:13 AM UTC-7, Jeroen Demeyer wrote: >> >> Please build the following source tarball from source on OS X 10.7: >> >> http://boxen.math.washington.edu/home/jdemeyer/release/sage-5.0.beta13-lion/sage-5.0.beta13-lion.tar >> >> I have included a few fixes, now *hopefully* it should work for everybody. >> >> Report success and failure, include the output of >> $ clang --version >> > > Works for me (with SAGE_CHECK=yes) on two different machines: > > $ clang --version > Apple clang version 3.1 (tags/Apple/clang-318.0.45) (based on LLVM 3.1svn) > Target: x86_64-apple-darwin11.3.0 > Thread model: posix > > $ clang --version > Apple clang version 3.1
Re: [sage-devel] Re: inferior sage in emacs, bug?
On Apr 11, 2012, at 4:32 PM, Benjamin Jones wrote: > On Wed, Apr 11, 2012 at 4:16 AM, Ivan Andrus wrote: >> On Apr 11, 2012, at 10:34 AM, Ivan Andrus wrote: >> >>> FWIW, I've been meaning to make an spkg with my changes (adding AUCTeX >>> support for SageTeX). It would also include customization of the preamble >>> and possibly a fix for this problem. >> >> I made spkg that you can try [1]. >> >> I can confirm the Unknown button type `help-xref' error if I revert Nick's >> fix [2], but not otherwise. The new spkg contains the latest from my >> repository [3] including this fix. If desired I can open a trac ticket and >> get this to be the new official spkg, though I would like to add a make-spkg >> script first so that it's easier (create sage-load.el and rename directory) >> in the future. >> >> -Ivan >> >> [1] http://boxen.math.washington.edu/home/iandrus/sage_mode-0.8.spkg >> [2] https://bitbucket.org/ncalexan/sage-mode/changeset/4e9e72fc639f >> [3] https://bitbucket.org/gvol/sage-mode/overview >> > > Thanks Ivan, your sage_mode-0.8.0.spkg works for me! Excellent. > By the way, > should it be "sage_mode" or "sage-mode"? It looks like the 0.7 spkg > was called "sage-mode". I'm a bit torn on that. The problem with sage-mode is that Sage uses a dash to separate the package name from the version, so it complained that it didn't understand the version. It's not the only spkg with this problem, but I thought maybe I should fix it. > If you make a ticket, please CC me on it and I'll help review. Will do. Thanks. -Ivan -- 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: inferior sage in emacs, bug?
On Apr 11, 2012, at 3:52 PM, Florent Hivert wrote: > Hi, > >> Perhaps we should make my fork the "official" sage-mode repository so that >> Nick no longer has to be involved. > > I've write (maybe even admin) access on Nick's repo I'm pretty sure he will > agree to give your the same right. So I don't really see the point of having a > new fork. It will just add some confusion, or am I missing something ? Oh, okay. I didn't know that was possible. The only confusion of still using his repo will be that his name is on it but he (presumably) won't have anything to do with it. FWIW, I've been meaning to make an spkg with my changes (adding AUCTeX support for SageTeX). It would also include customization of the preamble and possibly a fix for this problem. >>> >>> I'm not sure what you mean by "include customization of the preamble" but >>> the >>> patch I submitted was exactly for that purpose. So the LaTeX preamble should >>> now be fully customizable in emacs customization menus. What I would like to >>> have is to include Sage's "latex.extra_preamble()" to emacs >>> preamble. Unfortunately I don't know how to get this from emacs. >> >> Sorry, I meant that it includes your changes in this area. > > When did you made your "fork" ? Isn't your patch already there ? I forked, made the change, and then submitted a pull request. So my fork isn't very old. -Ivan -- 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: Julia
In other words, the reason why many programmers don't like lisp is * OMG I forgot a closing parenthesis, where is it * my parentheses keys have worn off * can't time with sub-millisecond accuracy * uncaught exceptions ;-) On Thursday, April 12, 2012 2:41:30 AM UTC+1, rjf wrote: > > I would tell you how much faster (fib 25) is in lisp but I got a > division by 0. > It seems to be 0.00 seconds. > > (defun fib(n) > (if (< n 2) > n > (+ (fib (- n 1))(fib(- n 2))) > > > The reason people compare speed is that it is quantitatively easy. > > However, people value expressiveness in a programming language. > > Otherwise we would all be programming in assembler. > > > RJF > -- 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
