On Mon, Mar 3, 2008 at 11:57 PM, Ivan Andrus <[EMAIL PROTECTED]> wrote:
>
> > 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?
>
> C
On Mon, Mar 3, 2008 at 11:04 PM, 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
Hi,
Before we can release Sage-3.0 the doctest coverage must reach 50%.
This is one of the more
difficult goals for Sage-3.0. Thus I propose that we have a "Sage Doc
Days" this Sunday.
Whose interested in helping?
-- William
--
William Stein
Associate Professor of Mathematics
University of W
On Mar 6, 2008, at 1:01 PM, William Stein wrote:
> Before we can release Sage-3.0 the doctest coverage must reach 50%.
> This is one of the more
> difficult goals for Sage-3.0. Thus I propose that we have a "Sage Doc
> Days" this Sunday.
> Whose interested in helping?
Sure.
david
--~--~
Hi all,
after the Scipy/Sage Days 8 meeting, we were all very impressed by the
progress made by Cython. For those not familiar with it, Cython:
http://www.cython.org/
is an evolved version of Pyrex (which is used by numpy and scipy) with
lots of improvements. We'd like to position Cytho
Sorry, I am tied up on Sunday (though possibly will no longer be by
the time the sun rises over Seattle. Assuming that it does.)
However I have benn trying to contribute to doctests where competent
and will continue to do so when possible!
John
On 06/03/2008, David Harvey <[EMAIL PROTECTED]> w
I would love to help!
On Mar 6, 10:17 am, "John Cremona" <[EMAIL PROTECTED]> wrote:
> Sorry, I am tied up on Sunday (though possibly will no longer be by
> the time the sun rises over Seattle. Assuming that it does.)
>
> However I have benn trying to contribute to doctests where competent
> and
Currently if I try to run valgrind on sage.math, it just says
permission denied. Is that intentional, or did the permissions get
screwed up somehow?
Bill.
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from thi
I will try to help, although my weekends get consumed by family
obligations sometimes. I'm not sure what areas are low in coverage
that I am competent to help with.
Almost all of my use of sage involves optional packages - phcpack,
biopython, and polymake. The easiest thing for me would be to a
On Mar 6, 8:39 pm, Bill Hart <[EMAIL PROTECTED]> wrote:
Hi Bill,
> Currently if I try to run valgrind on sage.math, it just says
> permission denied. Is that intentional, or did the permissions get
> screwed up somehow?
>
> Bill.
Nope, that version has been disabled on purpose since it can't
The following code causes a crash:
R = BooleanPolynomialRing(2)
f = 1 + R.gens()[0]
s = f.set()
t = set(s)
# this happened on sagenb.org, as well as the latest SAGE version
installed locally.
Unhandled SIGSEGV: A segmentation fault
Will you be publishing a list of which modules are lacking acceptable
doctest coverage?
On Thu, Mar 6, 2008 at 1:01 PM, William Stein <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Before we can release Sage-3.0 the doctest coverage must reach 50%.
> This is one of the more
> difficult goals for Sage
I'm in. I'll likely work on either modular/hecke (24.7%) or
modular/modsym (14.2%).
-cc
On Thu, Mar 6, 2008 at 10:01 AM, William Stein <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Before we can release Sage-3.0 the doctest coverage must reach 50%.
> This is one of the more
> difficult goals for Sa
I'll be there. So far I've been doctest-ing various files in sage/
rings (ring.pyx, ideal.pyx, integer_ring.pyx). I'd like to see where
people want to see more detailed docstrings and doctests.
--
Chris Swierczewski
--~--~-~--~~~---~--~~
To post to this group, sen
On Thu, Mar 6, 2008 at 2:04 PM, Chris Swierczewski <[EMAIL PROTECTED]> wrote:
>
> I'll be there. So far I've been doctest-ing various files in sage/
^^
Hey, you're local. Want to meet at a coffee shop, e.g., one in
Capitol Hill?
> Will you be publishing a list of which modules are
On Thu, 06 Mar 2008 at 10:01AM -0800, William Stein wrote:
> Before we can release Sage-3.0 the doctest coverage must reach 50%.
> This is one of the more difficult goals for Sage-3.0. Thus I propose
> that we have a "Sage Doc Days" this Sunday. Whose interested in
> helping?
Since I opened a tic
On Mar 6, 3:06 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> Hey, you're local. Want to meet at a coffee shop, e.g., one in
> Capitol Hill?
Sure thing! I'd like to get some Sage work done in the morning.
(Algebra study session in the mid-afternoon.) Are there any other
Seattle-ites out there
I think the best one for me would be interfaces; if other people are
interested in something in there please let me know so I don't
duplicate effort. I am most interested in (and will start with) the
phc, mathematica, and tachyon interfaces.
Will this be coordinated on IRC, or a wiki, or somethi
On Thu, Mar 6, 2008 at 9:07 PM, mhampton <[EMAIL PROTECTED]> wrote:
>
> I think the best one for me would be interfaces; if other people are
> interested in something in there please let me know so I don't
> duplicate effort. I am most interested in (and will start with) the
> phc, mathematic
> The following might be acceptable.
>
> (1) The user downloads a Fluid app.
>
> (2) The user downloads a separate sage-2.10.2.dmg (say).
>
> (3) When Fluid app runs it asks for the location of the sage dmg,
> extracts it
> "into itself", and uses that.
>
> Then the combination of Fluid with Sa
On Thu, 6 Mar 2008 12:53:43 -0800 (PST)
VictorMiller <[EMAIL PROTECTED]> wrote:
>
> The following code causes a crash:
>
> R = BooleanPolynomialRing(2)
> f = 1 + R.gens()[0]
> s = f.set()
> t = set(s)
>
> # this happened on sagenb.org, as well as the latest SAGE version
> installed locally.
T
Does one just add a bunch of documentation and make a patch and submit
it? Or does one make a bunch of Trac tickets and make a ton of
patches?
On Mar 6, 9:55 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Thu, Mar 6, 2008 at 9:07 PM, mhampton <[EMAIL PROTECTED]> wrote:
>
> > I think the bes
On Mar 7, 8:53 am, Timothy Clemans <[EMAIL PROTECTED]> wrote:
> Does one just add a bunch of documentation and make a patch and submit
> it? Or does one make a bunch of Trac tickets and make a ton of
> patches?
>
The idea is to add doctests. One would add doctests to one file or
directory of fi
Hi,
I was at Sage Days 8 and I posted what we were doing in there to my blog:
http://ondrejcertik.blogspot.com/2008/03/sage-days-8.html
here I'd like to put some points related to SymPy and Sage.calculus.
We discussed quite a lot of it in Austin, but I'd like to have it in
the mailinglist as we
24 matches
Mail list logo
