[sage-combinat-devel] Re: Sage Days in Bobo-Dioulasso debriefing; Sage in developping countries
On Sunday, November 11, 2012 10:00:42 AM UTC+1, Nicolas M. Thiéry wrote: - Having more Sage mirrors in Africa (although the network issues were more in the last kilometer). Hi, thank's for this detailed report and the discussion. I'm somewhat responsible for the mirror network, and I have heard reports about those bad network conditions from several places for some time now. I've tried to find more mirrors, but it's usually hard to get in contact with the right persons or even find a suitable institution. For example, to day I've added a second mirror for south america, which is probably an equally important continent. Does anyone have contacts to some suitable institutions in, let's say, Argentina, Uruguay, Ecuador, Ghana, ... ? Also, I try to make downloads work better by essentially to techniques: * torrent/metalink files. they basically tell a download-helper or web-browser to check for all sources in parallel and they also allow to resume partially downloaded files and checking them when they have finished. E.g. transmission is pre-installed on ubuntu and should be the #1 option for downloading sage tarballs or disk images. * compressing with lzma for those linux distributions where lzma/7z is installed by default. In the beginning, I got some reports that it is confusing, but for one reason or another this stopped. Probably, because right-click extract just works. Also, it would be possible - on more modern distributions - to squeeze out even more bytes by using lrztar + lzma/zpaq. Has anyone objections or some experience with that? H -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/LThu8KrPLoQJ. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
[sage-combinat-devel] Sage-combinat repo down
Hey, Sorry to sound like a broken record, but I believe the sage-combinat server is down again. What's the status on getting it back up? Thanks, Travis -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/-oTs4VAzqAwJ. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
Re: [sage-combinat-devel] Sage-combinat repo down
Hi, I power cycled the machine. It stated clearly on the display that a memory cheap *must* be re-seated. I hope I can do this tomorrow morning, which will of course mean downtime. I don't know how hard it will be to figure out which chip DIMM C3 actually is. The machine has a *lot* of memory chips in it. In the meantime, I suggest moving the combinat repo to another machine. -- William On Thu, Nov 15, 2012 at 12:27 PM, William Stein wst...@gmail.com wrote: There may be a memory issue. I'm going to the server room to physically reboot it again right now. On Thu, Nov 15, 2012 at 9:27 AM, Travis Scrimshaw tsc...@ucdavis.edu wrote: Hey, Sorry to sound like a broken record, but I believe the sage-combinat server is down again. What's the status on getting it back up? Thanks, Travis -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/-oTs4VAzqAwJ. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. -- William Stein Professor of Mathematics University of Washington http://wstein.org -- William Stein Professor of Mathematics University of Washington http://wstein.org -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
Re: [sage-devel] Sage Days in Bobo-Dioulasso debriefing; Sage in developping countries
Hi, Le lundi 12 novembre 2012 10:31:52 UTC+1, Jeroen Demeyer a écrit : On 2012-11-11 10:00, Nicolas M. Thiery wrote: - Precompiled binary for Linux: besides the usual distro-specific binaries, it would be very helpful to have two (32bit / 64bit) fat Sage binaries that would work without dependencies on as many distros and processors as possible. The pre-compiled binaries *should* work on old processors. If not, that's a bug which should be reported. Supporting more distros is possible if and only if somebody contributes a buildbot slave machine for building the binaries. One possible reason (maybe not the only one) for the binary build to need recent (sse2) set of instructions may be this bug on atlas package: http://trac.sagemath.org/sage_trac/ticket/13706 It has the effect of chosing HAMMER architecture (btw, where is this default choice coming from ?) when SAGE_FAT_BINARY is set to 'yes', no matter the value of SAGE_ATLAS_ARCH (which could be older than Hammer). After aplying the basic patch (which should be checked/improved by specialists), sse2 does not appear anymore on sage-flags.txt and the build works on Pentium 3. The request about distros is not to have many distro-specific builds that cost a lot but one autonomous robust non-distro-specific build. You ask for contributing a buildbot slave machine for building the binaries, is this about buying a machine or about spending time in maintaining a buildbot on an existing machine ? Ciao, Thierry -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
[sage-devel] Re: Sage Days in Bobo-Dioulasso debriefing; Sage in developping countries
On Sunday, November 11, 2012 10:00:42 AM UTC+1, Nicolas M. Thiéry wrote: - Having more Sage mirrors in Africa (although the network issues were more in the last kilometer). Hi, thank's for this detailed report and the discussion. I'm somewhat responsible for the mirror network, and I have heard reports about those bad network conditions from several places for some time now. I've tried to find more mirrors, but it's usually hard to get in contact with the right persons or even find a suitable institution. For example, to day I've added a second mirror for south america, which is probably an equally important continent. Does anyone have contacts to some suitable institutions in, let's say, Argentina, Uruguay, Ecuador, Ghana, ... ? Also, I try to make downloads work better by essentially to techniques: * torrent/metalink files. they basically tell a download-helper or web-browser to check for all sources in parallel and they also allow to resume partially downloaded files and checking them when they have finished. E.g. transmission is pre-installed on ubuntu and should be the #1 option for downloading sage tarballs or disk images. * compressing with lzma for those linux distributions where lzma/7z is installed by default. In the beginning, I got some reports that it is confusing, but for one reason or another this stopped. Probably, because right-click extract just works. Also, it would be possible - on more modern distributions - to squeeze out even more bytes by using lrztar + lzma/zpaq. Has anyone objections or some experience with that? H -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
[sage-devel] Re: Sage Days in Bobo-Dioulasso debriefing; Sage in developping countries
Le dimanche 11 novembre 2012 10:00:42 UTC+1, Nicolas M. Thiéry a écrit : That was a good occasion for a real-life evaluation of a claim I have been desiring to make for a long time: �Sage, being open-source, is well adapted for universities in developing countries�. http://Nicolas.Thiery.name/ Very interesting report. I'm however a little bit worried that your audience could have the feeling that math open-source software requires installing linux or/and recent hardware, while this is not mandatory at all outside of a few research fields. But perhaps I'm wrong and you also spread the word that some good open-source math softwares run on say Windows XP (or even Windows 98). -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
[sage-devel] Re: Access to SPARC 64
On 2012-11-14, Ondřej Čertík ondrej.cer...@gmail.com wrote: Hi, I am a release manager for the next NumPy release (1.7) and we have one bug that only shows on SPARC 64, see below for details. There are such machines on skynet, e.g. mark. -bash-3.00$ uname -a SunOS mark 5.10 Generic_127111-01 sun4u sparc SUNW,Sun-Blade-2500 -bash-3.00$ isainfo -b 64 I suppose William can get you access to it, if you don't have it already. HTH, Dima Is there anyone who would be willing and able to give me an access to such a machine so that I can debug it? Jason recommended to ask on the Sage list. I am BCCing the NumPy list. Any help would be greatly appreciated. Thanks, Ondrej On Thu, Aug 30, 2012 at 8:21 PM, Jason Grout jason-s...@creativetrax.com wrote: On 8/30/12 10:10 PM, Ondřej Čertík wrote: Hi, Does anyone have a SPARC 64 machine that I could have an access to, so that I can try to reproduce and fix the following issue? http://projects.scipy.org/numpy/ticket/2076 That would be greatly appreciated, as it is currently marked as a blocker for 1.7.0. You might ask on sage-devel. They were just talking about SPARC machines the other day on sage-devel. Thanks, Jason ___ NumPy-Discussion mailing list numpy-discuss...@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
Re: [sage-devel] Sage Days in Bobo-Dioulasso debriefing; Sage in developping countries
The new ATLAS http://trac.sagemath.org/10508 has additional generic archdefs and these are used with SAGE_FAT_BINARY now. Also, SAGE_FAT_BINARY essentially means pick reasonable defaults on non-museum hardware for the sage binary tarball. The only bug is that the variable has a strange name for historical reasons. On Thursday, November 15, 2012 8:07:12 AM UTC-5, Thierry (sage-googlesucks@xxx) wrote: Hi, Le lundi 12 novembre 2012 10:31:52 UTC+1, Jeroen Demeyer a écrit : On 2012-11-11 10:00, Nicolas M. Thiery wrote: - Precompiled binary for Linux: besides the usual distro-specific binaries, it would be very helpful to have two (32bit / 64bit) fat Sage binaries that would work without dependencies on as many distros and processors as possible. The pre-compiled binaries *should* work on old processors. If not, that's a bug which should be reported. Supporting more distros is possible if and only if somebody contributes a buildbot slave machine for building the binaries. One possible reason (maybe not the only one) for the binary build to need recent (sse2) set of instructions may be this bug on atlas package: http://trac.sagemath.org/sage_trac/ticket/13706 It has the effect of chosing HAMMER architecture (btw, where is this default choice coming from ?) when SAGE_FAT_BINARY is set to 'yes', no matter the value of SAGE_ATLAS_ARCH (which could be older than Hammer). After aplying the basic patch (which should be checked/improved by specialists), sse2 does not appear anymore on sage-flags.txt and the build works on Pentium 3. The request about distros is not to have many distro-specific builds that cost a lot but one autonomous robust non-distro-specific build. You ask for contributing a buildbot slave machine for building the binaries, is this about buying a machine or about spending time in maintaining a buildbot on an existing machine ? Ciao, Thierry -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
[sage-devel] Re: analytic_rank() discussed on mathoverflow
On Nov 13, 1:26 am, John Cremona john.crem...@gmail.com wrote: No, you do not miss anything. As someone has already reminded us (and I say clearly in the talk for which those are the slides), there is no known way of proving that the 3rd (or higher) derivative of an elliptic curve L-function is 0. Any computations of higher derivative are always based on an assumption that some lower derivatives which have been computed to some approximation and which look as if they are zero, really are zero. OK, just for posterity (the MathOverflow question points to this discussion), let's make clear here that to provide an *upper bound* on the order of vanishing (say, r), one needs to prove that *one* of L^(0)(1), L^(1)(1), ..., L^(r)(1) is nonzero, not any particular one. With proper error bounds that's doable in principle: as John points out, the error bounds used to prove that L^(r)(1) is non-zero assume that L^(0)(1)=...=L^(r-1)(1)=0, but if that assumption isn't valid then r is still a valid upper bound on the order of vanishing of L at 1, just not a sharp one. Every time that sage underreports the order of vanishing rather than not finish, run out of memory, or throw an error too much work for me, I think we can consider it a bug. Of course *proving* that sage is underreporting the order of vanishing is hard :-). -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
[sage-devel] Conventions for writing documentation
Hi, Skimming over the reference manual, it seems that there is no clear standard regarding how to write some things. For instance, sometimes self is double-quoted (``self``), sometimes it isn't. Sometimes True and False are double-quoted, sometimes not. Sometimes the name of arguments (say, x) is single-quoted (when they are mathematical variables), sometimes they are double-quoted, and sometimes they are not quoted at all, etc. etc. etc. What is the preferred way to go? Also, to describe what a function does, is it better to write maths in latex (i.e., if `x = 0`) or in sage code (i.e., if ``x == 0``) ? Thanks, --- Charles Bouillaguet http://www.lifl.fr/~bouillaguet/ -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
Re: [sage-devel] Conventions for writing documentation
Charles, Skimming over the reference manual, it seems that there is no clear standard regarding how to write some things. For instance, sometimes self is double-quoted (``self``), sometimes it isn't. Sometimes True and False are double-quoted, sometimes not. Sometimes the name of arguments (say, x) is single-quoted (when they are mathematical variables), sometimes they are double-quoted, and sometimes they are not quoted at all, etc. etc. etc. What is the preferred way to go? For name of variables, functions, ..., you must use two backquotes because this is the standard in Shinpx (http://sphinx-doc.org/rest.html) and Docutils (http://docutils.sourceforge.net/docs/ref/rst/roles.html#literal). The single backqoute must be used only for math elements that will be rendering using LaTeX (http://docutils.sourceforge.net/docs/ref/rst/roles.html#math). Also, to describe what a function does, is it better to write maths in latex (i.e., if `x = 0`) or in sage code (i.e., if ``x == 0``) ? It will depend if you use the sign symbol (=) to mean attribution or not when describe what the algorithm does. Once in sage code (and python) the sign symbol mean attribution I prefer to use the two sign symbol to mean comparison (``x == 0``). Raniere -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
Re: [sage-devel] Sage Days in Bobo-Dioulasso debriefing; Sage in developping countries
On Thu, Nov 15, 2012 at 09:42:04AM -0800, Volker Braun wrote: The new ATLAS http://trac.sagemath.org/10508 has additional generic archdefs and these are used with SAGE_FAT_BINARY now. Also, SAGE_FAT_BINARY essentially means pick reasonable defaults on non-museum hardware for the sage binary tarball. The only bug is that the variable has a strange name for historical reasons. As of today, this seems not to be fixed in the spkg proposed in #10508 : SAGE_FAT_BINARY default still overwrites SAGE_ATLAS_ARCH when it is set. SAGE_FAT_BINARY is not only used for atlas, but also for (according to grep in the sage-5.4 sources) : ecm-6.3.p8 libm4ri-20120613 mpir-2.4.0.p6 polybori-0.8.2 r-2.14.0.p6 hence one may want to take advantage of it and be more precise by setting the SAGE_ATLAS_ARCH variable. By the way, it is interesting to see that, when SAGE_FAT_BINARY=='yes' in sage-5.4, libm4ri-20120613 explicitely disables SSE2 set of instructions and atlas-3.8.4.p1 explicitely enables it. Also, in the #10508 package, configure_base() method adds 3DNow set of instructions to some Intel architecture, which seems not to know it: https://en.wikipedia.org/wiki/3DNow! Ciao, Thierry -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
[sage-devel] Re: Conventions for writing documentation
Hey, From my understanding there is a lot of documentation put in before the current standards were set (for example, look at how many functions do not have any documentation). My personal belief is that it should always be ``self``, ``True``, and ``False`` when they are consider as code (ex. Return ``False`` if...). Variables are somewhat more tricky, in particular if it is also an argument for the function. There it depends on context and how the documentation is written (same for your second question). I also believe in cross-referencing whenever possible. My 2 cents, Travis On Thursday, November 15, 2012 11:09:58 AM UTC-8, Charles Bouillaguet wrote: Hi, Skimming over the reference manual, it seems that there is no clear standard regarding how to write some things. For instance, sometimes self is double-quoted (``self``), sometimes it isn't. Sometimes True and False are double-quoted, sometimes not. Sometimes the name of arguments (say, x) is single-quoted (when they are mathematical variables), sometimes they are double-quoted, and sometimes they are not quoted at all, etc. etc. etc. What is the preferred way to go? Also, to describe what a function does, is it better to write maths in latex (i.e., if `x = 0`) or in sage code (i.e., if ``x == 0``) ? Thanks, --- Charles Bouillaguet http://www.lifl.fr/~bouillaguet/ -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
Re: [sage-devel] Re: Sage Days in Bobo-Dioulasso debriefing; Sage in developping countries
2012/11/15 parisse bernard.pari...@ujf-grenoble.fr But perhaps I'm wrong and you also spread the word that some good open-source math softwares run on say Windows XP (or even Windows 98). But then why should developing countries use an old, buggy and proprietary software when they can get for free modern, top class open source operating systems? :) -- *Andrea Lazzarotto* - http://andrealazzarotto.com* * -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
Re: [sage-devel] Re: Sage Days in Bobo-Dioulasso debriefing; Sage in developping countries
2012/11/14 Jason Grout jason-s...@creativetrax.com I'm curious: how does the software selection compare to, for example, mathbuntu (http://www.mathbuntu.org/), particularly the math packages? I just tried, that distro does NOT contain Sage, just a link to the Sage Notebook. -- *Andrea Lazzarotto* - http://andrealazzarotto.com* * -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
Re: [sage-devel] Re: Sage Days in Bobo-Dioulasso debriefing; Sage in developping countries
But then why should developing countries use an old, buggy and proprietary software when they can get for free modern, top class open source operating systems? :) Because they are used to work with windows, they don't know linux and they don't know someone who can explain how to use it. And their PC works well with windows : think of the nightmare it can be sometimes to make your hardware work with linux, some popular linux distros have dropped support for old hardware: I'm writing on a PC with 442Mo of RAM where I could install xubuntu LTS 12.04 but I keep running on an older version because it swaps too much, on a more recent Acer this same xubuntu does not recognize the 3-d opengl card acceleration while older xubuntu did. And I'm afraid there are a lot of mathematicians who don't use linux, even in the open-source software developers community in OCDE countries, think of Mac users for example :-) -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
[sage-devel] Re: Sage Days in Bobo-Dioulasso debriefing; Sage in developping countries
On 11/15/12 3:22 PM, Andrea Lazzarotto wrote: 2012/11/14 Jason Grout jason-s...@creativetrax.com mailto:jason-s...@creativetrax.com I'm curious: how does the software selection compare to, for example, mathbuntu (http://www.mathbuntu.org/ http://www.mathbuntu.org/), particularly the math packages? I just tried, that distro does NOT contain Sage, just a link to the Sage Notebook. Hmm, interesting. The webpage led me to believe that it does include Sage. Thanks for checking. Jason -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
Re: [sage-devel] Sage Days in Bobo-Dioulasso debriefing; Sage in developping countries
On Thursday, November 15, 2012 2:56:44 PM UTC-5, Thierry (sage-googlesucks@xxx) wrote: Also, SAGE_FAT_BINARY essentially means pick reasonable defaults on non-museum hardware for the sage binary tarball. The only bug is that the variable has a strange name for historical reasons. As of today, this seems not to be fixed in the spkg proposed in #10508 : SAGE_FAT_BINARY default still overwrites SAGE_ATLAS_ARCH when it is set. The combination is nonsensical: You either want a binary that runs on all reasonably old hardware for distribution, or you want to specify the architecture in detail. Which one is it? I don't mind adding support for nonsensical combinations if there is demand. But the only bug here is that it requires SSE2 on i386, which is probably too much. Note that the old ATLAS (which we currently ship, and probably will for a while) doesn't have generic archdefs to start with so it always was a crapshot. Also, in the #10508 package, configure_base() method adds 3DNow set of instructions to some Intel architecture, which seems not to know it: https://en.wikipedia.org/wiki/3DNow! So? Sage will never run with only the original 8086 instruction set. For many of the processors on your web page you'll have to recompile a linux distro from source, never mind Sage. -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
[sage-devel] Re: Conventions for writing documentation
For code (if it makes sense to type it into Sage), use double quotes. ``self``, ``x==0``. For math, use single quotes `x=0`, On Thursday, November 15, 2012 2:09:58 PM UTC-5, Charles Bouillaguet wrote: Hi, Skimming over the reference manual, it seems that there is no clear standard regarding how to write some things. For instance, sometimes self is double-quoted (``self``), sometimes it isn't. Sometimes True and False are double-quoted, sometimes not. Sometimes the name of arguments (say, x) is single-quoted (when they are mathematical variables), sometimes they are double-quoted, and sometimes they are not quoted at all, etc. etc. etc. What is the preferred way to go? Also, to describe what a function does, is it better to write maths in latex (i.e., if `x = 0`) or in sage code (i.e., if ``x == 0``) ? Thanks, --- Charles Bouillaguet http://www.lifl.fr/~bouillaguet/ -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
[sage-devel] Re: Conventions for writing documentation
On Thursday, November 15, 2012 3:06:48 PM UTC-5, Travis Scrimshaw wrote: Hey, From my understanding there is a lot of documentation put in before the current standards were set (for example, look at how many Yup, and unless someone wants to update ALL the doc at once with this and then personally rebase all current patches to it, it's probably better to update it piecemeal as things are changed, which often does happen. -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
[sage-devel] Re: Conventions for writing documentation
To avoid this dichotomy, I would suggest writing in language if ``x`` equals zero. On 11/16/2012 06:14 AM, Volker Braun wrote: For code (if it makes sense to type it into Sage), use double quotes. ``self``, ``x==0``. For math, use single quotes `x=0`, On Thursday, November 15, 2012 2:09:58 PM UTC-5, Charles Bouillaguet wrote: Hi, Skimming over the reference manual, it seems that there is no clear standard regarding how to write some things. For instance, sometimes self is double-quoted (``self``), sometimes it isn't. Sometimes True and False are double-quoted, sometimes not. Sometimes the name of arguments (say, x) is single-quoted (when they are mathematical variables), sometimes they are double-quoted, and sometimes they are not quoted at all, etc. etc. etc. What is the preferred way to go? Also, to describe what a function does, is it better to write maths in latex (i.e., if `x = 0`) or in sage code (i.e., if ``x == 0``) ? Thanks, --- Charles Bouillaguet http://www.lifl.fr/~bouillaguet/ http://www.lifl.fr/~bouillaguet/ -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
Re: [sage-devel] Re: How to proceed to reduce Sage's memory leaking?
On 2012-11-14 23:34, Nils Bruin wrote: On Nov 14, 11:28 am, Jeroen Demeyer jdeme...@cage.ugent.be wrote: FYI: it's a Fedora 16 system with an Intel(R) Pentium(R) 4 CPU 3.60GHz processor running Linux 3.3.7-1.fc16.x86_64. That sounded convenient because my desktop is similar: Fedora 16 running 3.6.5-2.fc16.x86_64 #1 SMP on Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz Could you try again with sage-5.5.beta1? -- You received this message because you are subscribed to the Google Groups sage-devel group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
