[sage-devel] Re: LaTeX code to Sage expression?
On 5/12/11 11:38 PM, Dan Drake wrote: If I have a Sage expression, I can do latex(foo) to get LaTeX code. Is there an inverse to that function? Frequently, I do a calculation in Sage and get something complicated. I find it easier to look at when typeset by TeX, so I call latex(), paste the result into a document, then typeset. Conversely, sometimes I write something in LaTeX and would like to do some calculations with it. So I'd like to call...something, paste the result into Sage, and compute. I'm generally working with reasonably simple symbolic expressions. Is this possible? I know that a full parser is practically impossible, but it seems like a relatively simple parser could work pretty well. I think I'm asking for a complement to Rob Beezer's tex2sws. Thoughts? If we had this, it would be a lot simpler to do a web-based equation editor. Jason -- 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] LaTeX code to Sage expression?
If I have a Sage expression, I can do latex(foo) to get LaTeX code. Is there an inverse to that function? Frequently, I do a calculation in Sage and get something complicated. I find it easier to look at when typeset by TeX, so I call latex(), paste the result into a document, then typeset. Conversely, sometimes I write something in LaTeX and would like to do some calculations with it. So I'd like to call...something, paste the result into Sage, and compute. I'm generally working with reasonably simple symbolic expressions. Is this possible? I know that a full parser is practically impossible, but it seems like a relatively simple parser could work pretty well. I think I'm asking for a complement to Rob Beezer's tex2sws. Thoughts? Dan -- --- Dan Drake - http://mathsci.kaist.ac.kr/~drake --- signature.asc Description: Digital signature
Re: [sage-devel] Patch rejected after merge
> If a ticket's been merged, unless it's found to have a genuine > flaw, it should supersede ... tickets ... which have not been > merged. +1 -- Robert L. Miller http://www.rlmiller.org/ -- 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] Patch rejected after merge
I've been reviewing #10804, which was merged in sage-4.7.1.alpha0. I though this was a done deal... but apparently not. In the meantime, #10549 got a positive review. It conflicted with #10804. Jeroen, acting RM (for which I'm immensely grateful), backed out #10804 and marked both patches needs_work. Now, I've gotta re-review #10804. I've already put in lots of time into this review so as long as tests pass, I'm gonna give a +1. The work's done, problem solved. No hard feelings (note: posting to sage-devel, not sage-flame). Fortunately, Robert was the author of both patches, but if that wasn't the case, I imagine both authors scrambling to rebase / re-review. Bottom line: I think this was handled wrong. If a ticket's been merged, unless it's found to have a genuine flaw, it should supersede (IMO) tickets with positive reviews which have not been merged. Thoughts? -- 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: New guidelines for spkg's
> On Thursday, May 12, 2011 3:18:29 PM UTC-7, Ondrej Certik wrote:
> > On Thu, May 12, 2011 at 5:29 AM, Maarten Derickx
> > wrote:
> > [...]
> >
> > >> What would be the advantage of having it in the SPKG itself?
> > >
> > > That it wil be compatible with parallel building as mentioned earlier.
> > >
> > >> Like if you want to install two packages that overwrite the same file?
> > >
> > > I don't think we should never do (or even want) such a thing. I think
> > > every spkg should only touch it's own files (or else we will get into
> > > an unpredictable mess if we also want uninstall and parallel
> > > building), if you really want an spkg to touch a file created by for
> > > example foo.spkg, one should instead make a patch for the foo.spkg.
> > > Maybe we should add some code that checks if there are spkg's breaking
> > > this rule.
> >
> > Definitely, two packages should not override the same files.
>
> Does ATLAS sometimes (depending on the OS) overwrite files from the lapack
> installation?
>
> Certainly *if* two packages can affect the same files, their dependencies
> should reflect it, so for example, ATLAS depends on lapack,
That's certainly a valid question! We usually first install blas which produce
a libf77blas then lapack which will produce liblapack. Finally it is ATLAS's
turn. ATLAS if I am not mistaken overwrite libf77blas from blas purely and
simply. Then it takes liblapack and modifies it.
Note that the current plans that we have for blas/lapack/atlas with Volker
involves getting rid of the blas spkg and of the individual lapack spkg and
build {f77,c}blas and lapack in one go in the ATLAS spkg.
Francois
This email may be confidential and subject to legal privilege, it may
not reflect the views of the University of Canterbury, and it is not
guaranteed to be virus free. If you are not an intended recipient,
please notify the sender immediately and erase all copies of the message
and any attachments.
Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
information.
--
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: New guidelines for spkg's
On Thursday, May 12, 2011 3:18:29 PM UTC-7, Ondrej Certik wrote: > > On Thu, May 12, 2011 at 5:29 AM, Maarten Derickx > wrote: > [...] > >> > >> What would be the advantage of having it in the SPKG itself? > >> > > That it wil be compatible with parallel building as mentioned earlier. > > > >> Like if you want to install two packages that overwrite the same file? > > I don't think we should never do (or even want) such a thing. I think > > every spkg should only touch it's own files (or else we will get into > > an unpredictable mess if we also want uninstall and parallel > > building), if you really want an spkg to touch a file created by for > > example foo.spkg, one should instead make a patch for the foo.spkg. > > Maybe we should add some code that checks if there are spkg's breaking > > this rule. > > Definitely, two packages should not override the same files. > Does ATLAS sometimes (depending on the OS) overwrite files from the lapack installation? Certainly *if* two packages can affect the same files, their dependencies should reflect it, so for example, ATLAS depends on lapack, -- 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
Re: [sage-devel] Re: New guidelines for spkg's
On Thu, May 12, 2011 at 5:29 AM, Maarten Derickx wrote: [...] >> >> What would be the advantage of having it in the SPKG itself? >> > That it wil be compatible with parallel building as mentioned earlier. > >> Like if you want to install two packages that overwrite the same file? > I don't think we should never do (or even want) such a thing. I think > every spkg should only touch it's own files (or else we will get into > an unpredictable mess if we also want uninstall and parallel > building), if you really want an spkg to touch a file created by for > example foo.spkg, one should instead make a patch for the foo.spkg. > Maybe we should add some code that checks if there are spkg's breaking > this rule. Definitely, two packages should not override the same files. So what you have in mind is: * automatically generate the list of files from *sequential* builds, store it in spkg (or possibly somewhere else) * use this in all default builds (either parallel or sequential), Sage would store the list of files somewhere, and use it for uninstall Is that right? Ondrej -- 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: new Sage mirror (Singapore)
Harald, sorry, it should be Nanyang Technological University On May 13, 2:15 am, Harald Schilly wrote: > Done! > > H -- 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: new Sage mirror (Singapore)
Done! H -- 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: 237 tickets need review
On Thursday, May 12, 2011 6:13:16 PM UTC+1, William wrote: > > It's even conceivable that a tutorial in Russian > (say) might be a bit different than the English version of the > tutorial, due to cultural differences (I have no idea how). > For example, the Polish translation could use Reverse Polish notation throughout :-) -- 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: Error Building sage 4.7
Thanks Volker, >I'm a bit confused as to what Suse is shipping, the latest ppl release is 11.2 Looking a little at the opensuse site it says that the version of libppl is 11. and the release (of the package?) is 3.3 if this helps? >As a workaround, you can delete $SAGE_LOCAL/lib/libppl.so.9.0.0 and replace it >with a symlink to your system libppl (/usr/lib64/libppl.so or >somesuch). Then >re-run make. Have done this and it now seems to be compiling fine thanks again. 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
Re: [sage-devel] Re: 237 tickets need review
On Thu, May 12, 2011 at 6:26 AM, kcrisman wrote: > >> If, on the other hand, we would require that a translation of the >> documentation describing X into language Y is just something that >> describes X in good/acceptable language Y, then for a native/fluent >> speaker of Y the review process reduces to pretty much just reading >> documentation without any worries about its relation to the >> original... > > Right, this is what I'm talking about. If we can agree on something > like this, that would be helpful. Presumably these tickets will not > be the last ones to have localization! I definitely like this suggest: positive review if document Y is a useful readable document that doesn't contain SPAM, lots of basic writing errors, etc. It's even conceivable that a tutorial in Russian (say) might be a bit different than the English version of the tutorial, due to cultural differences (I have no idea how). > (Not even for the languages in question - after all, there are LOTS of > other useful documents to localize... not to mention the reference > manual, which I have no idea how we'd localize, especially given that > the commands would still be in Roman orthography with English > names...) > > - kcrisman > > -- > 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 > -- William Stein Professor of Mathematics University of Washington http://wstein.org -- 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: 4.6.2 build on Ubuntu 11.04 alpha 3 fails on crypt.so
On 24 Kwi, 15:26, pipedream wrote: > We expect below spkg to be in sage 4.7.1. In the meantime, if you > runUbuntu11.04(Natty) > and stable sage 4.6.2, you can replace SAGE_ROOT/spkg/standard/ > python-2.6.4.p9.spkg > with this: > > http://users.aims.ac.za/~jan/python-2.6.4.p10.spkg > I did that and it helped. However, I then installed the flask notebook (as on http://code.google.com/r/rkirov-flask/ ) and I get the error again:" /home/anna/sage/sage-4.6.2/devel/rkirov-flask/sagenb/notebook/all.py in () 14 from sage_email import email 15 ---> 16 from notebook_object import notebook, inotebook 17 18 from interact import interact, input_box, slider, range_slider, selector, checkbox, input_grid, text_control, color_selector /home/anna/sage/sage-4.6.2/devel/rkirov-flask/sagenb/notebook/ notebook_object.py in () 15 import time, os, shutil, signal, tempfile 16 ---> 17 import notebook as _notebook 18 19 import run_notebook /home/anna/sage/sage-4.6.2/devel/rkirov-flask/sagenb/notebook/ notebook.pyc in () 44 import server_conf # server configuration 45 import user_conf# user configuration ---> 46 import user # users 47 from template import template, prettify_time_ago 48 /home/anna/sage/sage-4.6.2/devel/rkirov-flask/sagenb/notebook/user.py in () 1 # -*- coding: utf-8 -* 2 import copy > 3 import crypt 4 import cPickle 5 import os ImportError: No module named crypt Error importing ipy_profile_sage - perhaps you should run %upgrade? WARNING: Loading of ipy_profile_sage failed. -- 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] new Sage mirror (Singapore)
Hi people, we now have this up and running, thanks to our sysadmins at NTU (Hi, Melvin!) http://jambu.spms.ntu.edu.sg/sage/ Could someone please add it to the list of mirrors? Thanks, Dima -- 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-4.7 release schedule
Hello all, At this point nothing is blocking the sage-4.7 release any more. So it would be nice if everybody could try to build and test Sage, to see whether there are any remaining issues. If not, I will release sage-4.7 in about a week or so. Jeroen. -- 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: 237 tickets need review
> If, on the other hand, we would require that a translation of the > documentation describing X into language Y is just something that > describes X in good/acceptable language Y, then for a native/fluent > speaker of Y the review process reduces to pretty much just reading > documentation without any worries about its relation to the > original... Right, this is what I'm talking about. If we can agree on something like this, that would be helpful. Presumably these tickets will not be the last ones to have localization! (Not even for the languages in question - after all, there are LOTS of other useful documents to localize... not to mention the reference manual, which I have no idea how we'd localize, especially given that the commands would still be in Roman orthography with English names...) - kcrisman -- 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: Is there a sparse univariate polynomial ring implemented with NTL?
Hi David, On 12 Mai, 13:55, David Roe wrote: > All sparse polynomials are implemented within Sage, in > sage.rings.polynomial.polynomial_generic_sparse. It would be good if the > constructor only used the implementation as part of the key for dense > polynomials. Thank you for the clarification! 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] Re: New guidelines for spkg's
On May 11, 9:41 am, Ondrej Certik wrote: > On Tue, May 10, 2011 at 11:23 PM, Maarten Derickx > > > > > > > > > > wrote: > > > On May 10, 9:10 am, Ondrej Certik wrote:. > > >> It just occurred to me, that it should be possible to keep the current > >> SPKG format, and implement uninstall. One just needs to keep track of > >> all files in SPKG_LOCAL, then see what new files were added + which > >> files have changed. > > >> If a file has changed, then a warning should be produced, and we would > >> look at each case manually. Maybe it's possible to make the whole Sage > >> (or Qsnake in my case) to build without changing any files, just keep > >> adding them. > > > A brilliant idea. This allows us to transition smoothly to a more > > distribution friendly setup. I'm interested to see a list of spkgs > > which modify files (and offcourse the files being edited). > > > Is SPKG_LOCAL really an environment variable used in sage? If so the > > next step might be to temporarily change it to SPKG_LOCAL/ > > Sage uses SAGE_LOCAL, but SPKG_LOCAL is more project neutral, so I use that. > > > packagename.versionnr before each install of an SPKG and see what > > breakes (probably a lot). But if we get things working again then > > uninstall is just as easy as deleting a directory. This would make the > > step to something like nix very small. > > > Note that a lot of SPKG's also install stuff into something like > > python*/site-packages. > > > And I second the idea that the list of files should not be > > autogenerated during install but be a part of the SPKG. Although the > > initial file lists in the SPKG can be autogenerated offcourse :). > > What would be the advantage of having it in the SPKG itself? > That it wil be compatible with parallel building as mentioned earlier. > Like if you want to install two packages that overwrite the same file? I don't think we should never do (or even want) such a thing. I think every spkg should only touch it's own files (or else we will get into an unpredictable mess if we also want uninstall and parallel building), if you really want an spkg to touch a file created by for example foo.spkg, one should instead make a patch for the foo.spkg. Maybe we should add some code that checks if there are spkg's breaking this rule. > > Ondrej -- 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] Is there a sparse univariate polynomial ring implemented with NTL?
All sparse polynomials are implemented within Sage, in
sage.rings.polynomial.polynomial_generic_sparse. It would be good if the
constructor only used the implementation as part of the key for dense
polynomials.
David
On Wed, May 11, 2011 at 04:37, Simon King wrote:
> Hi!
>
> When constructing a polynomial ring, one can provide arguments
> "sparse" and "implementation". But it seems that there is no sparse
> version based on NTL implementation:
>
> sage: R. = PolynomialRing(ZZ, sparse=False, implementation='NTL')
> sage: R.is_sparse()
> False
> sage: R
> Univariate Polynomial Ring in x over Integer Ring (using NTL)
> sage: S. = PolynomialRing(ZZ, sparse=True, implementation='NTL')
> sage: S.is_sparse()
> True
> sage: S
> Sparse Univariate Polynomial Ring in x over Integer Ring
>
> So, S is sparse, but the implementation is not mentioned (so, it seems
> to be the default, i.e. FLINT).
>
> However, providing "implementation" is not ignored, it is used for the
> cache key:
> sage: T. = PolynomialRing(ZZ, sparse=True)
> sage: T
> Sparse Univariate Polynomial Ring in x over Integer Ring
> sage: S is T
> False
>
> Question 1:
> What is the underlying implementation of S? Is it NTL, as requested?
>
> Question 2, if the implementation of S is based on FLINT (the
> default):
> Should the "implementation" argument be silently ignored, so that "S
> is T" in the example above?
> Or should an error be raised instead ("explicit is better than
> implicit")?
>
> If the answer to question 1 is that it does use NTL, then of course it
> should be mentioned in the string representation.
>
> Best regards,
> 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
>
--
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] PLEASE somebody update the virtual box info (e.g., remove?)
I created a ticket for this: http://trac.sagemath.org/sage_trac/ticket/11330 -- 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: Error Building sage 4.7
I'm a bit confused as to what Suse is shipping, the latest ppl release is 11.2 As a workaround, you can delete $SAGE_LOCAL/lib/libppl.so.9.0.0 and replace it with a symlink to your system libppl (/usr/lib64/libppl.so or somesuch). Then re-run make. Volker -- 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: Error Building sage 4.7
This is (again) caused by overriding the shared library search path LD_LIBRARY_PATH. In this case, the Sage version of ppl is incompatible with the OS version of ppl. Because we are forcefully loading the Sage version, gcc no longer works. We had similar problems with readline before. The only long-term solution is to use RPATH/RUNPATH instead of the LD_LIBRARY_PATH mechanism. -- 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: Error Building sage 4.7
> what do you mean by "latest 4.7" ? > The latest testing release is 4.7.rc1, and the latest stable is 4.6.2 > Ah right I meant 4.7.rc1 by the lastest 4.7. Should have posted to another group? 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] Re: DAE solver on Sage, Python wrapper for SUNDIALS
Hi Johan, Thank you for you brief overview. > I am involved in the JModelica/Assimulo effort, and I have also used > CasADi in collaboration with the Leuven team, so I thought I offer my > five cents. I actually emailed Christian Andersson asking for "blessing" before I move forward. I also contacted yesterday Joel Andersson here in Leuven. > I think that both JModelica/Assimulo and CasADi would be valuable > additions to Sage, since they address different problems, even though > there is some overlapping functionality. Also, there is ongoing work > to integrate JModelica.org and CasADi. I agree, but first I was thinking simpler and aiming at the ODE/DAE solvers only. :) Sage (and SciPy by the way) are in need of a straightforward interface to solvers like SUNDIALS and Radau. I understand that offering the whole pack JModelica/Assimulo/CasADi would imediatelly give rise to a simulator/optimization for a more engineering-like and applied math environment reachable via Sage. This would become attractive also for people doing any sort of Simulink or VHDL-AMS modeling (which I did some time ago). As long as we can smoothly integrate the above environment with the symbolic capabilities of Sage I think it is very good thing to have. My aim is to have the ability to manipulate any sort of equation and hand it down to a solver. Pretty much as you do with other math packages. If now I can lump this equations into a module (say Modelica) connect further other modules and arbitrarily drop them into a system simulator/optimizer, that would be really good. What do you think? That would be equally good for the more math or engineering oriented people out there. I am looking on how to put some of this on Sage, hoping to get further inputs from the experienced people there. Best, Guilherme -- 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: Coefficients of univariate polynomials
> On Tue, May 10, 2011 at 10:37 PM, Mike Hansen wrote: > > On Tue, May 10, 2011 at 6:52 PM, Rob Beezer wrote: > >> OK, thanks for the explanation, Tom. p.exponents() was the missing > >> piece I did not have. > > > It would probably make sense to have p.monomials() method to be > > consistent with the multivariate case: > > > sage: R. = QQ[] > > sage: p = t^4 + 8 > > sage: p.coefficients() > > [1, 8] > > sage: p.monomials() > > [t^4, 1] > > sage: sum(c*m for c,m in zip(p.coefficients(), p.monomials())) > > t^4 + 8 > > +1 +1 (with documentation with benchmarching -- p.monomials() might be more expensive than the analogous loop over p.exponents()). > > p.coeffs() might be better off renamed to something like > > all_coefficients or dense_coefficients or I suggest deprecation and reference in p.coefficients to p.list. > I use p.coeffs() pretty often. Perhaps p.coefficients should take an > additional argument: p.coeffs could be an alias to > p.coefficients(dense=True), and get deprecated. +1 to deprecation I'm opposed to different behaviour for p.coeffs and p.coefficients, which can only be a source of confusion. As long as p.list() is documented in p.coefficients() then I'm neutral on adding the dense keyword -- like p.coeffs() [see docstring] it is likely to be slower, and people are likely to use it. I was at first surprised by p.coefficients but it seems useful, efficient, and compatible with sparse and dense representations; p.list() is completely standard Python syntax. --David -- 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] Book on Sage published.
I got an email from the publisher today confirming the book on Sage has been published, although the web site still says to be published in May 2011. http://www.packtpub.com/sage-beginners-guide/book Some fraction of sales will go to Sage, though I'm not sure what fraction, or if there needs to be a minimum number of books sold first. Having been a reviewer, I know the book address more numerical problems, plotting and has nothing whatsoever to do with number theory, which is clearly one of Sage's strongest points. There's a bit on using Maxima for symbolic calculations. We have a long way to go to get the number of books written about Sage as there is for MATLAB or Mathematica. I think there are over 500 for Mathematica and MATLAB must have many times that. But I think it's useful to have a book written about Sage that not from William or someone else at the uni of Washington. (That said, there are numerous points in the book where a developer would know more. This problem is compounded somewhat by the fact that some of the documentation on Sage is wrong. The "install from source" section was very bad until recently, and as someone mentioned, there's a lot of confusing references to VirtualBox and VMware, with one bit of documentation recommending VirtualBox and the other VMware. Anyway, I should have a copy of the book soon. I've not seen it in full yet, as I've only seen drafts. 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
Re: [sage-devel] PLEASE somebody update the virtual box info (e.g., remove?)
On 05/11/11 08:48 PM, Volker Braun wrote: I think this would be possible. The command-line utility VBoxManage lets you do everything you can with the GUI. The only caveat is that it needs quite a bit of storage and root permissions to start/stop virtual machines. The program could be made set uid root, so that program could run as root, without allowing any other program to be run as root. Or sudo could be configured to allow a specific set of user(s) to run a specific application. sudo is *not* an "all or nothing". -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? -- 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
