> Just for clarification, you're only talking about distributiong the
> OUTPUT of
> a non-GPL'd program? You're not distributing the program itself at
> all but
> just the output of the program, right?
Correct. I guess it's confusing since the output of said program _is_
a program.
>> Wi
On Tue, Mar 4, 2008 at 1:04 AM, Ivan Andrus <[EMAIL PROTECTED]> wrote:
>
> Fluid has been updated fixing the largest (in my mind) bug.
> Therefore, I have created a version of Sage.app which I am happy
> enough with to share with people. I have added instructions on the
> wiki at http://wiki.
Fluid has been updated fixing the largest (in my mind) bug.
Therefore, I have created a version of Sage.app which I am happy
enough with to share with people. I have added instructions on the
wiki at http://wiki.sagemath.org/SageMacApplication and would like to
add a pre-packaged version
Hi All,
I've recently written some sage code for manipulating and simplifying
propositional calculus statements.
The code can be downloaded at
http://sage.math.washington.edu/home/goreckc/sage/logic/logic.tgz
if anyone is interested in checking it out.
Also, I was wondering if anyone knew of a go
Hello folks,
the rc1 release is finally out. Various old doctest failures, most new
patches got their failures fixed along the way. Instead of a deep
freeze I ended up merging quite some number of patches to stay on top
of things. Tarball is at
http://sage.math.washington.edu/home/mabshoff/relea
At the request of Jason Grout, I've posted another Sage+tvtk 3D
graphics demo at
http://sage.math.washington.edu/home/cwitty/demo-tangent-tvtk.py
.
This is essentially a copy of
http://demonstrations.wolfram.com/TangentToASurface/
: it draws a 3D plot of a surface, lets you spin the surface wit
Dan Drake wrote:
> Hello all,
>
> I made a significant update to the Sage-LaTeX embedding stuff. A current
> patch is attached to trac #1766 (ignore the Mercurial stuff). The LaTeX
> style file and Python module now work much, much better and have
> complete documentation. Can someone review this
Hello all,
I made a significant update to the Sage-LaTeX embedding stuff. A current
patch is attached to trac #1766 (ignore the Mercurial stuff). The LaTeX
style file and Python module now work much, much better and have
complete documentation. Can someone review this patch?
Thanks,
Dan
--
---
On Mar 3, 2008, at 7:52 AM, David Roe wrote:
> I was not suggesting eliminating the ability to directly
> access .value from Cython. Rather, I see set_si() and get_si() as
> convenience functions so that if the only thing you're doing is
> converting back and forth between sage integer and
Fixing the ubiquitous accessing of .value would be far more work that it's
worth. The main functionality that I would like is a get_si() with bounds
checking. Given that, I think having a set_si as well is reasonable.
David
On Mon, Mar 3, 2008 at 9:36 AM, Joel B. Mohler <[EMAIL PROTECTED]>
wrote
Integer ndigit method isn't so hot at the low end. Remarkably, the low end is
pretty high!
sage: n=2^500
sage: %timeit len(n.digits(10))
1 loops, best of 3: 61.6 µs per loop
sage: %timeit n.ndigits(10)
1 loops, best of 3: 98.4 µs per loop
sage: len(n.digits(10))==n.ndigits(10)
True
sage
On Monday 03 March 2008 08:42:53 am David Roe wrote:
> I think they should still exist, but should be cdef'd. This means I can
> interface between C longs and sage Integers without having to reach in and
> grab n.value, but one can't use them to make Integers mutable in Python. A
> function get_
I was not suggesting eliminating the ability to directly access .value from
Cython. Rather, I see set_si() and get_si() as convenience functions so
that if the only thing you're doing is converting back and forth between
sage integer and long, one can use object oriented notation (and so that you
Down again!
{{{
Python Traceback
Traceback (most recent call last):
File "/var/lib/python-support/python2.4/trac/web/main.py", line 387,
in dispatch_request
dispatcher.dispatch(req)
File "/var/lib/python-support/python2.4/trac/web/main.py", line 237,
in dispatch
resp = chosen_handler.
On Mar 3, 5:42 am, "David Roe" <[EMAIL PROTECTED]> wrote:
> I think they should still exist, but should be cdef'd. This means I can
> interface between C longs and sage Integers without having to reach in and
> grab n.value, but one can't use them to make Integers mutable in Python. A
> function
Hello everyone,
Quick question: Is anyone interested in running a Sage exhibition
booth at the upcoming CMS summer meeting in Montreal (1--6 June 2008)?
Some things to note:
1. No funding is available.
2. I have secured a promise from the CMS of two tables---not a full
exhibition booth---in th
Trac is back. (I restarted it.)
William
On Mon, Mar 3, 2008 at 8:10 AM, David Harvey <[EMAIL PROTECTED]> wrote:
>
> Proxy Error
>
> The proxy server received an invalid response from an upstream server.
> The proxy server could not handle the request GET /sage_trac/.
>
> Reason: Error reading f
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /sage_trac/.
Reason: Error reading from remote server
?
david
--~--~-~--~~~---~--~~
To post to this group, send email to sag
I think they should still exist, but should be cdef'd. This means I can
interface between C longs and sage Integers without having to reach in and
grab n.value, but one can't use them to make Integers mutable in Python. A
function get_si() would also be useful if it did bounds checking so that I
Hi,
These methods set_si & set_str violate immutability:
sage: n=300
sage: n.set_si(12)
sage: n
12
Shouldn't they be called _set_unsafe_xx? Better yet, shouldn't they be
deleted altogether since I can't find anywhere they are used in code aside
from doc-tests? Or, was that the point -- to do
20 matches
Mail list logo
