I am proud to report that Sage has been "officially" recognized as
"very suitable for rapid prototyping". Also, Sage is "a fine tool for
many applications".
This recognition is because I won the lightning round (for the "rapid
prototyping" recognition) and got second place in the main contest
(fo
On Mon, Sep 13, 2010 at 5:32 AM, Nathann Cohen wrote:
>> I've posted the .sws tohttp://wiki.sagemath.org/Talks. You can see
>> video of my demo, and (eventually) of all the talks at ICMS 2010,
>> athttp://fe.math.kobe-u.ac.jp/Movies/ms/icms2010/icms2010-video.html.
>
> Looks like all the links t
.kobe-u.ac.jp/Movies/ms/icms2010/icms2010-video.html .
Carl Witty
--
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-
On Mon, Aug 23, 2010 at 3:45 PM, Dr. David Kirkby
wrote:
> I've created a patch for sympow, which the release manager has agreed to
> merge in 4.5.3 - in fact, he has kindly made it a blocker!!
>
> He is happy with it, but wants someone able to comment on the changes I made
> to the file fpu.c.
..
On Fri, Aug 20, 2010 at 9:26 PM, Dr. David Kirkby
wrote:
> Unless OS X rounds by default to 64-bits, I can't understand how this would
> have ever worked. Why was it not necessary to change the rounding behavior
> of an Intel based OS X system?
Modern x86 family chips actually have two totally se
On Tue, Feb 17, 2009 at 8:52 PM, Carl Witty wrote:
> I have compiled and run Sage 3.2.3 on my T-Mobile G1 cell phone, and
> large portions of it actually work.
Two people have asked me for a copy of my build.
Let me emphasize that many doctests failed, and you'd need an ARM
device w
On Thu, Aug 19, 2010 at 10:35 AM, Dr. David Kirkby
wrote:
> Of course I know it depends on swap space, operating system, lots of things,
> so nobody can give an exact answer, but I'd be interested to know if
> building Sage on a machine with only 1 GB of RAM is likely to be possible.
>
> The machi
On Wed, Aug 18, 2010 at 6:47 AM, tuxiano wrote:
> Hi everybody
>
> I've tried to search in the archive but couldn't find if Sage is
> available or will ever available on Android operating system. As far
> as I know, Android is Linux-based so I was wondering if porting Sage
> to Android is feasible
On Mon, Aug 16, 2010 at 1:22 PM, Jay wrote:
> Hi!
>
> Yes, bpython is quite wonderful :).
>
> If I try to `easy_install bpython` from within a sage subshell I get
>
> ... (Full traceback if you'd like)
> ImportError: /opt/sage/local/lib/python2.6/lib-dynload/operator.so:
> undefined symbol: _PyUni
On Fri, Aug 13, 2010 at 12:08 AM, Dr. David Kirkby
wrote:
> How can I add a comment to the doc test, which will not be printed in the
> documentation? I'd like to add the result from a high-precision computation,
> so anyone looking at the doctest in future could see what's a reasonable
> answer a
On Mon, Aug 9, 2010 at 1:42 AM, Sergey Bochkanov
wrote:
> It is somehow connected to patch by Carl Witty which adds ability to
> work with Sage matrices/vectors. This patch works OK when package is
> used from Sage. But when we run test suite from spkg-check with
> "
On Fri, Aug 6, 2010 at 9:18 AM, Dr. David Kirkby
wrote:
> On 08/ 6/10 05:14 AM, Robert Bradshaw wrote:
>>
>> On Thu, Aug 5, 2010 at 3:25 AM, Bill Hart
>> wrote:
>>>
>>> The single biggest improvement in my mind would be made to MPIR. And I
>>> know the MPIR devels would absolutely love to have th
On Thu, Aug 5, 2010 at 4:06 PM, Simon King wrote:
> I think it is easier to do
> from sage.all import ZZ
> instead of providing its exact location (from sage.rings.integer...).
>
> Moreover, using sage.all is more stable, because the exact location of
> things can change (so that "from sage.rings
On Thu, Aug 5, 2010 at 2:59 PM, Dr. David Kirkby
wrote:
> On 08/ 5/10 06:17 PM, Sergey Bochkanov wrote:
>>
>> Hello,
>>
>>> Hmmm... Didn't thought about this situation yet. Definitely we can't
>>> solve this problem with any kind of regular expressions. One
>>> possible solution is to
On Thu, Aug 5, 2010 at 10:23 AM, David Kirkby wrote:
> BTW, do you have any ideas why the second failure at #9099 might occur
>
> sage -t -long devel/sage/sage/symbolic/expression.pyx
> **
> File
> "/home/palmieri/fulvia/sage-4.
On Thu, Aug 5, 2010 at 9:44 AM, David Kirkby wrote:
> With all the numerical noise issues I've seen in Sage, the three dots
> solves its. So if we expect
>
> 1.00
> but get
> 1.01
> we can change that to
> 1.0...
> and the test will pass.
>
> However, what if we
On Wed, Jul 28, 2010 at 11:38 PM, Sergey Bochkanov
wrote:
> My proposal is to make
> * boolean vector/matrix = GF(2), RDF (non-zero = True)
> * integer vector/matrix = RDF
> * real = RDF
> * complex = CDF
I've attached a patch to make alglib allow input in the following formats:
* boolean vector/
On Wed, Jul 28, 2010 at 11:38 PM, Sergey Bochkanov
wrote:
>> My suggestion would be to support Sage vectors and matrices over
>> GF(2), RDF, and CDF (machine floats and complex numbers), as well as
>> numpy arrays and matrices of appropriate types.
>
> +1
>
> My proposal is to make
> * boolean vec
On Thu, Jul 29, 2010 at 10:25 AM, Sergey Bochkanov
wrote:
> Hello, Carl.
>
> Here is some documentation about Python-ALGLIB interface (called
> X-interface in this document):
>
> http://www.alglib.net/share/2010-07-26-alglib-for-sage/x-interface.pdf
Thanks.
> It is very short, but shoul
On Wed, Jul 28, 2010 at 7:07 PM, William Stein wrote:
> On Wednesday, July 28, 2010, kcrisman wrote:
>> But for True and False, we would rather have
>>
>> if n is True:
>>
>> not
>>
>> if n==True:
>>
>> correct? I've seen that cause some problems in code I've reviewed,
>> where things that shoul
On Mon, Jul 26, 2010 at 4:43 AM, Sergey Bochkanov
wrote:
> Hello!
>
> Second beta of ALGLIB.spkg is ready. It can be downloaded from
> http://www.alglib.net/share/2010-07-26-alglib-for-sage/
Cool. Compiles for me, but I didn't try any tests.
> -- SAGE INTEGRATION --
>
> Well, ALGLIB c
On Tue, Jul 27, 2010 at 2:22 PM, Jeroen Demeyer wrote:
> My working on the big PARI-upgrade (#9343) has sprouted many ideas. One
> of these (possibly crazy) ideas is the following: we might manage to
> some extent to make 32-bit PARI behave like 64-bit PARI. Because right
> now various doctests
On Mon, Jul 26, 2010 at 2:52 AM, Simon King wrote:
> Nonetheless, Cython needs to know what argument type and type of
> output to expect. Therefore, one has "long lgefint(GEN x)" in the
> Cython header.
>
> It works (at least for me). I admit that it somehow looks wrong, and
> indeed it results in
On Sun, Jul 25, 2010 at 8:11 PM, Dan Drake wrote:
> On Sun, 25 Jul 2010 at 07:11PM -0700, Carl Witty wrote:
>> Hmm... looks like the current state of affairs is a mess. Looking
>> through the 'def __hash__' grep hits in sage/rings, there are quite a
>> few of eac
On Sun, Jul 25, 2010 at 6:33 PM, Dan Drake wrote:
> Hello,
>
> Ticket #9590 fixes a problem with hashing; it looks like the hash value
> in the doctest is 32- or 64-bit specific, and of course it fails on
> systems that don't match. The solution there is to change a doctest like
>
> sage: h
On Sun, Jul 25, 2010 at 10:27 AM, Robert Miller wrote:
> On Sun, Jul 25, 2010 at 2:01 PM, Nathann Cohen
> wrote:
>> Nononon, I understood why there are two copies of what appears to
>> be a "zero", and I think it's fine like that !
>
> This is definitely *not* fine, since we have
>
> sage: i
On Sat, Jul 24, 2010 at 2:29 PM, Burcin Erocal wrote:
> Hi,
>
> At Sage Days 24, I learned that Python allows the user to do arithmetic
> with bools:
>
> In [1]: 5+True
> Out[1]: 6
>
> In [2]: True + False
> Out[2]: 1
>
> In [3]: 5+False
> Out[3]: 5
>
> Sage seems to follow this convention as well
On Sat, Jul 24, 2010 at 11:54 AM, Rob Beezer wrote:
> So it is a verb. ;-)
>
> Looks like similar comments apply to edges().
>
> I'm thinking that optionally passing in a comparison function would be
> a nice thing to add - a minor convenience, but also it would drive
> home the point that the
On Fri, Jul 23, 2010 at 3:45 AM, Dr. David Kirkby
wrote:
> I just tried to build Sage, and got a failure with building IML. See log
> here.
>
> http://boxen.math.washington.edu/home/kirkby/iml-1.0.1.p12.log
>
> As soon as I restarted "make" again, so the build completed ok.
Well, in the following
On Thu, Jul 22, 2010 at 5:20 PM, Dan Drake wrote:
> Hello,
>
> Ticket #9502, when applied to 4.5.2.alpha0, prevents Sage from even
> starting -- the result is "ImportError: cannot import name SR", even
> though the patch at #9502 barely touches the symbolics code, and does so
> in a way that, to m
On Thu, Jul 22, 2010 at 3:05 PM, Martin Albrecht
wrote:
...
Pretty pictures! It would be nice, though, to have some sort of
indication on the picture whether Magma is red or blue...
For example, you could put "Magma" next to the 4 on the right-hand
scale, and "Sage" next to the -4 -- or vice-ve
On Tue, Jul 20, 2010 at 9:46 PM, Dan Drake wrote:
> Hello all,
>
> When building from source, I can set MAKE and have the Sage library
> build in parallel. Is there a way I can do the same thing when using
> "sage -b"? In analogy to "sage -t" and "sage -tp", it would be nice to
> have "sage -bp".
On Tue, Jul 20, 2010 at 2:46 PM, Vincent D <20100.delecr...@gmail.com> wrote:
> Jmodelica seems to be very interesting... but from
> http://www.jmodelica.org/page/14
> (or see the copy below) they argue that the software is their property
> (is that a problem for inclusion in Sage?). On the other
On Tue, Jul 20, 2010 at 7:37 AM, John Cremona wrote:
> I am having trouble with sage -pkg to make a new spkg from a directory
> my-spkg/. (I have done this before). Am I doing something stupid?
>
> After typing
>
> sage -pkg my-spkg
>
> nothing apparently happens (no new prompt) BUT a file with
I've created a proof-of-concept WebGL backend for Sage plot3d in the
notebook; if you have a WebGL-enabled browser, see
http://sagenb.org/home/pub/2263/ . And if you don't have a
WebGL-enabled browser, you should get one; see
http://learningwebgl.com/blog/?p=11 .
WebGL is an emerging standard for
On Mon, Jul 19, 2010 at 9:10 AM, David Kirkby wrote:
> Yes - see below.
>
> sage: quit
> Exiting Sage (CPU time 0m0.29s, Wall time 0m3.52s).
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x7e6627ec in _free_unlocked () from /lib/64/libc.so.1
> (gdb) bt
> #0 0x7e6627ec
On Sat, Jul 17, 2010 at 5:57 AM, Robert Miller wrote:
> Although
>
> http://trac.sagemath.org/sage_trac/ticket/5906
>
> was supposed to eliminate this problem for good, sometimes random
> (i.e. spring-layout) algorithms seem to trigger it, in particular when
> a short path happens to get put into
On Fri, Jul 16, 2010 at 8:21 PM, koffie wrote:
> Dear All,
>
> I was writing some code for sage and ran into trouble. The code was
> working just fine when it was a standalone function. Then I tried to
> add it to a pyx file (sage/rings/fraction_field_element.pyx to be
> precise) and ran into trou
On Fri, Jul 16, 2010 at 4:34 PM, Dr. David Kirkby
wrote:
> How does this sound.
>
> 1) We add an environment variable SAGE_ATLAS_THREADS
> 2) If unset, then the behavior is unchanged, so we build an unthreaded
> ATLAS.
> 3) If set to "auto":
>
> $ export SAGE_ATLAS_THREADS=auto
>
> then we let ATL
On Thu, Jul 15, 2010 at 1:38 PM, Andrey Novoseltsev wrote:
> Hi Carl,
>
> For example this installation of sage-4.5.alpha1
>
> novos...@sage:/scratch/novoselt/sage-4.5.alpha1/devel/sage-main$ hg
> qapplied
> trac_9502_basis_parent_bug_in_FreeModule.patch
> trac_9128-sphinx_links_all-fh.patch
> tra
On Thu, Jul 15, 2010 at 1:27 PM, Carl Witty wrote:
> One very simple change might be easier to implement/use. How about if
> there were both a "share" button and a "publish" button, and these
> went in to separate sections? I'm guessing that people asking for
On Tue, Feb 23, 2010 at 1:14 PM, Robert Bradshaw
wrote:
> On Feb 23, 2010, at 8:39 AM, Dr. David Kirkby wrote:
>
>> If one sets up a Sage server for public use, there is the opportunity for
>> someone to publish worksheets, there is a section:
>>
>>
>> "Browse published Sage worksheets
>> (no logi
On Tue, Jul 13, 2010 at 6:39 AM, Andrey Novoseltsev wrote:
> On Jul 13, 3:37 am, Carl Witty wrote:
>> On Thu, Jun 17, 2010 at 2:18 PM, Volker Braun wrote:
>> > Unsurprisingly, setting the random seed makes the random_expr() always
>> > return the same value:
&g
On Sat, Jul 3, 2010 at 6:27 AM, Volker Braun wrote:
> I would propose a mercurial patch queue in the spgk root directory.
> Then sage -pkg simply checks that either all patches in the queue are
> applied or that there exists an old-style /patches directory and no
> queue.
Since we all seem to lik
On Wed, Jul 14, 2010 at 2:43 PM, Mike Hansen wrote:
> On Wed, Jul 14, 2010 at 2:31 PM, Johannes wrote:
>> i want to check which part of the sagecode makes problems when trying to
>> port it to python 3.x. For that, I want want to build it with the '-3'
>> option, but i dont want to edit every sin
On Sun, Jul 11, 2010 at 5:38 AM, William Stein wrote:
> Cool. There are numerous parameters one could imagine a nagbot
> having. E.g,. max emails per week, how often messages sent, etc.,
> which should be easily customized by each recipient. Ideas? Please
> suggest them.
It should keep track
On Thu, Jul 1, 2010 at 8:36 AM, kcrisman wrote:
>
>
> On Jul 1, 10:30 am, Jason Grout wrote:
>> Is there an easy way to make this work?
>>
>> % sage -R
>>
>> R version 2.10.1 (2009-12-14)
>> Copyright (C) 2009 The R Foundation for Statistical Computing
>> ISBN 3-900051-07-0
>>
>> R is free softwa
amework automatically runs set_random_seed(0) before
testing every docstring, so this shouldn't be necessary.
Carl Witty
--
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
I realize this thread is 4 months old, but let me respond to this one
technical question:
On Thu, Mar 4, 2010 at 2:10 AM, Simon King wrote:
> Hi!
>
> On Mar 4, 8:24 am, Robert Bradshaw
> wrote:
>> I believe there is also some randomized testing that is done in the
>> category code that takes ran
Dirk, I'd prefer to have this discussion on sage-devel, where it will
be archived and other people can chip in as well. So I'm replying
both to you and to sage-devel... I hope you don't mind.
On Sun, Jul 11, 2010 at 3:56 AM, Dirk Laurie wrote:
> On Fri, Jul 09, 2010 at 11:3
x>y iff (a>0 and a*x>a*y)
or (a<0 and a*xy).
sage: qepcad('[a /= 0 ==> [x > y <==> [ [a x > a y /\ a > 0] \/ [a x <
a y /\ a < 0] ] ] ]', vars=('a','x','y'))
TRUE
> Carl Witty has (unreleased) Sage code for doing such
(Yes, I realize I'm responding to an 8-month-old email.)
On Wed, Nov 11, 2009 at 12:38 PM, kcrisman wrote:
>
> It would be worth trying this out in Maxima. If Maxima can do it, we
> can try to expose more stuff; if not, we'll have to return to other
> things if people really need this. A while
Sorry to be so late (10 months late!) in responding to this; I'm
getting back to Sage development and I'm reading through my sage-devel
archives.
Dirk, I don't know if you still care about this... I'm the original
author of the code (and documentation) in question. I basically made
up the behavio
On Tue, Jun 9, 2009 at 6:08 PM, Golam Mortuza
Hossain wrote:
>
> Hi,
>
> On Tue, Jun 9, 2009 at 9:45 PM, Jason Grout
> wrote:
>
>>> (4) Should we switch to old maxima format for "diff"?
>>
>> Can you clarify with an example what you mean? In other words, can you
>> give an example of the "new" w
On Thu, Jun 4, 2009 at 4:36 PM, Jason Grout wrote:
>
> It seems confusing and inconsisent that for a matrix m, m.change_ring(R)
> returns m when R==self.base_ring(), but otherwise returns a copy of m
> (coerced to the right ring).
>
> If you always just do new_mat = m.change_ring(R), you don't kn
On Mon, May 25, 2009 at 7:06 PM, Nicolas M. Thiery
wrote:
> Adding a couple calls like:
>
> register_unpickle_override('sage.categories.category', 'Sets', Sets)
>
> did the trick (thanks Carl!). By the way, where in the Sage source
> tree should I put those?
Well, obviously we don't have
On Fri, May 22, 2009 at 2:00 PM, Nick Alexander wrote:
>
>> We do this to avoid the (large) overhead of re-creating constants in
>> the bodies of loops, functions, etc. Perhaps we need to detect the
>> Integer=xxx line explicitly?
>
> Doing this accurately is equivalent to the halting problem. T
On Wed, May 13, 2009 at 11:02 AM, Robert Bradshaw
wrote:
>
> I recently noticed that complex interval fields have a very different
> notion of equality than real interval fields. For RIF, a != b if a is
> *definitely* not equal to b, but CIF just compares endpoints. I think
> we should change CIF
On Thu, May 7, 2009 at 7:01 AM, kcrisman wrote:
> I am hoping to help the push to 75% by adding some doctests to some of
> the plotting primitives. But for some reason, the following always
> occurs:
>
> sage: G = some graphics object
> sage: G == loads(dumps(G))
> False
>
> Nonetheless, no matt
On Wed, May 6, 2009 at 2:16 PM, Yann wrote:
> or print the error digit 4.?1 (expicit is better than implicit,
> etc :) )
Well, again this was an explicit decision; the thinking was that if
somebody saw 1.234567? they might be able to guess approximately what
it means without reading the document
On Wed, May 6, 2009 at 1:46 PM, Yann wrote:
>> In other words,
>> sage: RealIntervalField(4)(0, 1)
>> 1.?
>> prints as the interval [0 .. 2], rather than [-1 .. 1], because IMHO
>> it is useful to be able to know that an interval is nonnegative; and
>> we do this by always picking the result fart
On Wed, May 6, 2009 at 2:20 AM, Yann wrote:
>
> Just for the record,
> isn't the following a bug?
>
> sage: p=RealIntervalField(4)(3.1)
> sage: p.str(style='brackets')
> '[3.00 .. 3.25]'
> sage: p
> 4.?
It's a deliberate design decision. To quote from real_mpfi.pyx:
When there are two
On Fri, Apr 24, 2009 at 5:36 AM, Pat LeSmithe wrote:
>
> chris wuthrich wrote:
>> * In one of my files i have a line "power_series = series". This
>> produces the full docstring of series to appear twice in the
>> documentation, once under series and once under power_series. How can
>> I exclude
On Thu, Apr 23, 2009 at 9:19 PM, Jason Grout
wrote:
> Anyone know where the CSS file is? The color is set in a default.css
> file, but the only default.css files I see are in _static directories,
> which sounds like they are automatically generated somehow.
It comes (originally) from src/sphinx
On Wed, Apr 22, 2009 at 3:59 PM, Tim Lahey wrote:
>
> On Wed, Apr 22, 2009 at 6:54 PM, Carl Witty wrote:
>>
>>
>> Would it be better to test the results numerically? (For instance,
>> evaluate the integral returned and the desired result at 100 random
>>
On Wed, Apr 22, 2009 at 3:35 PM, Tim Lahey wrote:
> The problem arises with all the different integration systems. Usually some
> kind of simplification is needed on the integral returned, even if there
> aren't
> multiple solutions. This complicates the testing procedure since the steps to
> pe
On Sun, Apr 19, 2009 at 7:44 AM, Maurizio wrote:
> Carl, I took advantage of your suggestion, even though I assume I
> can't still go through the whole process with the current gcd
> capabilities in Pynac. But before than that, I'd like to point out
> something strange I did notice, and maybe als
On Sat, Apr 18, 2009 at 6:55 PM, William Stein wrote:
>>> First problem with QQbar: it seems that resultant() doesn't like it,
>>> because it is not able to convert it to a Singular ring (this is the
>>> error, I'm not attaching all the output, tell me if you need it)
>>>
>>> TypeError: no conver
On Sat, Apr 18, 2009 at 6:04 PM, Maurizio wrote:
>> QQ is the rational numbers (fractions). QQbar is the algebraic
>> closure of QQ; this means it includes every complex number which is
>> the root of a polynomial with rational coefficients. So it includes
>> things like sqrt(2) (which is a roo
On Sat, Apr 18, 2009 at 2:46 PM, Maurizio wrote:
> Could you be clearer? As I told, I'm not familiar with rings. I don't
> even know the meaning of the argument of GF (I took the number 5 from
> an example I see in sage-support group, I think). Do you think that QQ
> [] could fit in this case? Mo
On Sat, Apr 18, 2009 at 2:46 PM, William Stein wrote:
> I posted a patch so that
>
> (1) doctests are ran in the same order as the file
> (2) doctests can be run in random order
> (3) doctests can be run in random order specified by a seed
>
> Carl, maybe you can referee it:
>
> http://trac.sage
On Tue, Apr 14, 2009 at 11:57 AM, John H Palmieri
wrote:
> I figured out how to fix the problem, although I still don't know why
> adding a docstring should cause it.
>
> To fix it: the docstring for "print_or_typeset" contains the lines
...
Well, I can tell you why adding a docstring will cause
On Thu, Apr 16, 2009 at 3:43 PM, Maurizio wrote:
> Finally, even assuming that I can get the right answer from this,
> which is the recommended way to get the roots of an equation given by
> a "univariate polynomials == 0"? This is supposed to be the next step
> of the algorithm.
Taking a quick
On Thu, Apr 9, 2009 at 12:22 AM, Stan Schymanski wrote:
>
> Dear all,
>
> I encountered some mysterious problems earlier when I used .subs(locals
> ()), where some global variables such as pi and e were lost (see. e.g.
> thread
> http://groups.google.com/group/sage-support/browse_thread/thread/0
On Tue, Apr 7, 2009 at 12:16 PM, Brian Granger wrote:
>
> Ahh, that makes sense. It is the sympy.python thing that causes the
> problem. This hack seems to work fix the issue in the notebook:
>
> import sympy
> sympy.sage_python = sympy.python
> del sympy.python
> from sympy import *
>
> But an
On Sun, Apr 5, 2009 at 12:33 AM, jeffblakeslee wrote:
>
> Here's how I got it. Ctrl-c after a couple seconds on the first one,
> and then try the next.
> --
> | SAGE Version 3.0.6, Release Date: 2008-07-30
On Sat, Apr 4, 2009 at 6:53 PM, mabshoff wrote:
>
> Hello folks,
>
> for the last couple hours Sage's trac has been very slow or completely
> unresponsive. This is caused by the MS as well as Yahoo search engines
> hammering the website (as can be seen by the proxy error log as well
> as trac's l
On Sat, Apr 4, 2009 at 11:55 AM, jeffblakeslee wrote:
>
> Hello, This looks like a bug. It seems that after 3316 bits of
> precision
> the approximation of pi just puts out 0's. This doesn't seem to
> occur with the approximation of e.
>
> pi.n(3330)
> 3.1415926535897932384626433832795028841971
On Sun, Mar 29, 2009 at 4:13 PM, Rob Beezer wrote:
> So is the following *hypothetical* behavior not possible (or not
> desirable)?
>
> sage: preparse( 'differentiate(y^3, y)' )
> '_ = var("y"); differentiate(y**Integer(3), y)'
>
> If such a thing were indeed possible, I think it would make simp
On Sun, Mar 29, 2009 at 5:27 AM, Burcin Erocal wrote:
> * We raise an error whenever a function object is specified without
> variables.
>
> Comments?
+1 for raising an error.
Carl
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@goo
On Sat, Mar 28, 2009 at 7:59 PM, William Stein wrote:
>
> Hi,
>
> I created a new 2-page Sage quick reference based on the one Peter
> Jipsen made a while ago.
>
> http://sage.math.washington.edu/home/wstein/patches/quickref.pdf
>
> It's different than Peter's because it has some pictures and has
On Sat, Mar 28, 2009 at 10:50 AM, Martin Raum
wrote:
> Are you aware of any discussion about what should be comparable?
> Otherwise I will work our something and post it to Trac. I think this
> is the way to do it, isn't it?
People have specifically complained about the complex numbers and
numbe
On Sat, Mar 28, 2009 at 10:37 AM, Florent Hivert
wrote:
> I also like the following one because it has a very high precedence and also
> because it reminds XML tags
>
> [1,2,3] [1,2,3]
That one is nice; it's very pretty. Unfortunately, it doesn't work
with the same implementation, because
On Sat, Mar 28, 2009 at 5:28 AM, Jason Grout
wrote:
> Aha, the one custom infix operator that I know of in Sage.
>
> In the backslash operator and in the article posted, the rmul only
> stored the argument and the __mul__ only performed the operation. Are
> you always guaranteed that __rmul__ wi
On Fri, Mar 27, 2009 at 4:35 PM, Bill Hart wrote:
>
> Not to press the point, but isn't:
>
> "Our long-term proposal is to replace CPython's custom virtual machine
> with a JIT built on top of LLVM, while leaving the rest of the Python
> runtime relatively intact."
>
> the explanation of how they
On Wed, Mar 25, 2009 at 10:13 PM, William Stein wrote:
> 3. I would also like to see the default symbolics switch from
> maxima-based to pynac, which would I think really clearly justify the
> switch to 4.0, since it will have a *dramatic* impact on the usability
> of Sage by many users (the spee
On Wed, Mar 25, 2009 at 4:42 PM, Dan Drake wrote:
> On Wed, 25 Mar 2009 at 03:05PM -0700, Henryk Trappmann wrote:
>> I just encountered the ambiguouty:
>>
>> binomial(-1.0,2) == 1.0
>> binomial(-1,2) == 0
>>
>> do we need 2 diferent names? I think the second form is also needed
>> somewhere.
>> B
On Sun, Mar 22, 2009 at 3:55 AM, Henryk Trappmann
wrote:
>
> Another evil example:
> parametric_plot((lambda x: arctan(x),lambda x: arctan(x)**2),
> (-1000,1000))
>
> It seems that the plot algorithm is somehow deficient in those cases.
In both cases, it's plotting points approximately evenly sp
On Thu, Mar 19, 2009 at 3:45 PM, Maurizio wrote:
> For example, how does SAGE generate an instance of
> "sage.rings.integer.Integer"? I hope this can help me.
Well, I can at least answer this question. When you type at the sage:
prompt, or in the notebook, the input is run through the "preparse
On Wed, Mar 18, 2009 at 11:40 PM, Jan Groenewald wrote:
>
> Hi
>
> I did sage -docbuild all html to provide local
> documentation on each of 100 PCs on which I image
> from a central server. It is a nice way to provide
> a lab in a low-bandwidth environment with
> sage and sage docs locally.
>
>
On Wed, Mar 18, 2009 at 6:28 PM, John H Palmieri wrote:
> This is a very interesting idea, and I think I can do it for ZZ,
> QQbar, etc., but I don't know how to deal with GF(p). That is, in
> docstrings, you presumably want GF(p) to appear as is, while to
> evaluate latex(GF(p)), indeed to eval
On Wed, Mar 18, 2009 at 5:35 AM, John Cremona
> Therefore (if I am right) there needs to be a planned procedure for
> completing the ReSTification of Sage. For a start, is there anywhere
> a list showing which files have not yet been converted?
You can generate such a list for yourself, using
On Tue, Mar 17, 2009 at 4:46 PM, William Stein wrote:
>
> On Tue, Mar 17, 2009 at 4:41 PM, John H Palmieri
> wrote:
>> So I think it's easy to implement TeX macros into Sage: see > trac.sagemath.org/sage_trac/ticket/>. What macros should we
>> implement? I have \ZZ, \CC, \RR, and \QQ so far
On Tue, Mar 17, 2009 at 11:55 AM, John H Palmieri
wrote:
> Well, I've been trying to modify 'latex_preamble' in sage/doc/common/
> conf.py, and I'm having no luck at all: no changes I make have any
> effect. It seems like a good place to put a few macros (like \ZZ), but
> maybe that variable isn'
On Tue, Mar 17, 2009 at 11:28 AM, Justin Walker wrote:
>
>
> On Mar 17, 2009, at 10:07 AM, Nicolas M. Thiery wrote:
>> Just a mini-warning so that we don't stomp on each other's foot: I
>> made a couple very minor changes in the schemes code for the
>> categories (essentially in the parent's cons
On Tue, Mar 17, 2009 at 11:10 AM, John H Palmieri
wrote:
> I think \ZZ is a good option, too. Does anyone know if the file
> $SAGE_ROOT/devel/sage/doc/common/macros.tex has any role, currently?
I'm pretty sure it doesn't. (I searched through the whole sage/doc
tree for the word "macros", and i
On Tue, Mar 17, 2009 at 9:59 AM, Martin Albrecht
wrote:
>
> On Tuesday 17 March 2009, Carl Witty wrote:
>> My vote would be for `H_d(X, \ZZ)` (for easier typing), combined with
>> some sort of LaTeX-to-plain-text processing to change \ZZ to Z or ZZ
>> (I'm not sure
On Tue, Mar 17, 2009 at 9:35 AM, John H Palmieri wrote:
>
> Do we have any conventions or standards for the use of LaTeX in
> docstrings? Consider this:
>
> r"""
> This computes the integral homology `H_d(X, ZZ)` of `X` in
> dimension `d`.
> """
>
> versus
>
> r"""
> This computes
On Mon, Mar 16, 2009 at 9:58 PM, J Elaych wrote:
> Also, I built sage-3.4 from source on 64bit Ubuntu 8.10 AMD XP2 with
> 'export MAKE=make -j2' and I have to say that you folks have done an
> amazing job in that it all just built. Not so lucky with some 'sage -
> i' commands, but the problem w
On Mon, Mar 16, 2009 at 11:51 AM, Joel B. Mohler wrote:
>
> On Monday 16 March 2009 12:27:10 pm kcrisman wrote:
>> sage: integrate(y^2)
>> ---
>> TypeError Traceback (most recent call
>> last)
1 - 100 of 308 matches
Mail list logo
