On Wed, Jun 24, 2009 at 01:46:29PM -0700, Robert Miller wrote:
>
> On Jun 24, 10:34 pm, Robert Miller wrote:
> > > I really like having the ticket number first, it makes it easy to see
> > > (given an ordered list of patches) what patches belong as part of a
> > > single ticket. E.g.
> >
> >
Hi Sébastien!
On Thu, Jun 25, 2009 at 03:06:15PM -0700, slabbe wrote:
> This weekend I was introducing Sage to a friend. To illustrate Jmol, I
> showed him some 3d Cayley graphs of some finite groups :
>
> {{{
> sage: S = SymmetricGroup(4)
> sage: S.cayley_graph()
> Digraph on 24 vertice
On 64-bit Fedora 10, I see these doctest failures:
sage -t "devel/sage/doc/fr/tutorial/programming.rst"
sage -t "devel/sage/sage/misc/darwin_utilities.pyx"
Kiran
On Jun 25, 2:18 pm, Robert Miller wrote:
> This release is primarily the Python upgrade. The source tarball and
>
Can someone verify that this is a bug? Any hope a fix? (This is with
sage-4.0.2 on sage.math.)
{{{
sage: complex_plot((x^2 + I).sqrt().real_part(), (-2, 2), (-2, 2))
---
RuntimeError Traceback
On Thu, Jun 25, 2009 at 9:16 PM, Golam Mortuza
Hossain wrote:
>
> Hi,
>
...
>
> If I gather properly, we are having two different step functions
> (at least for now) as
>
> (2) Heaviside:
> (a) represented as: "heaviside"
> (b) latex name :"H"
> (c) heaviside(0): "heaviside(0)
I got the following on an intel mac, 10.4.11, not sure which are known
or unknown issues at this point:
The following tests failed:
sage -t "devel/sage/doc/fr/tutorial/programming.rst"
sage -t "devel/sage/sage/graphs/graph.py"
sage -t "devel/sage/sage/misc/darwin_util
Hi,
On Tue, Jun 23, 2009 at 6:45 PM, Maurizio wrote:
> Honestly, I don't actually know whether it means that much, but at
> this point I think that it could be useful for us to follow
> Mathematica in defining two different functions: Heaviside which is
> undefined in 0 and that is defined as the
On Jun 25, 11:18 am, Robert Miller wrote:
> This release is primarily the Python upgrade. The source tarball and
> sage.math binary are here:
>
> http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1.tarhttp://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1-s...
>
> If
Thanks for that explanation, gsw. I feel like I have a better sense
of why that happened so often in class!
- kcrisman
On Jun 25, 4:10 pm, gsw wrote:
> Hi,
>
> I suspect you're just running out of RAM.
> Not necessarily physically, but the construction Sage --> expect
> interface --> Maxima --
Nice video embedding.
Btw, it seems the first video is repeated twice (hence the double
length). Click to minute 49.
Rado
On Jun 25, 2:51 pm, Ondrej Certik wrote:
> Hi,
>
> On Tue, Jun 23, 2009 at 11:50 PM, William Stein wrote:
>
> > Hi,
>
> > Video and slides for *all* the talks so far from S
Hi,
This weekend I was introducing Sage to a friend. To illustrate Jmol, I
showed him some 3d Cayley graphs of some finite groups :
{{{
sage: S = SymmetricGroup(4)
sage: S.cayley_graph()
Digraph on 24 vertices
}}}
Then, he asked me to show the Cayley graph of some groups he often
works with :
Maybe we should just bump all the version numbers of python
packages...
I thought this would be a better approach (as did William, who first
suggested it), but I wanted to see if upgrading worked with copying
site-packages first.
--~--~-~--~~~---~--~~
To post to th
These test failures on 32-bit ubuntu (fresh build):
.//home/john/sage-4.1.alpha1/devel/sage/doc/common
.//home/john/sage-4.1.alpha1/devel/sage/doc/en
.//home/john/sage-4.1.alpha1/devel/sage/doc/fr
.//home/john/sage-4.1.alpha1/devel/sage/sage
after these error mess
On Thu, Jun 25, 2009 at 11:21 PM, Tom Boothby wrote:
>
> fails on sage.math, too
Just so you know, upgrading from Python 2.5 to Python 2.6 is really
hard. At a minimum, doing it right should involve rebuilding *every*
Python package in all of Sage. My understanding is that maybe Mike
shortcu
fails on sage.math, too
On Thu, Jun 25, 2009 at 1:56 PM, Jaap Spies wrote:
>
> Robert Miller wrote:
>> This release is primarily the Python upgrade. The source tarball and
>> sage.math binary are here:
>>
>> http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1.tar
>> http://sage.ma
On Thu, Jun 25, 2009 at 9:51 PM, Ondrej Certik wrote:
>
> Hi,
>
> On Tue, Jun 23, 2009 at 11:50 PM, William Stein wrote:
>>
>> Hi,
>>
>> Video and slides for *all* the talks so far from Sage Days 16 are now
>> posted here:
>>
>> http://wiki.sagemath.org/days16
>
> I have embedded the first two v
Robert Miller wrote:
> This release is primarily the Python upgrade. The source tarball and
> sage.math binary are here:
>
> http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1.tar
> http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1-sage.math-only-x86_64-Linux.ta
> On Thu, Jun 25, 2009 at 02:19:38AM -0700, Jason Grout wrote:
> > When Mike was experimenting with trac 0.11, he made a plugin or
> > something that put a "raw" link next to the attachment link, so an
> > attachment would look like:
>
> > trac_3948_description.patch (raw) Apply on top of previous
On Thu, Jun 25, 2009 at 9:09 PM, David Joyner wrote:
>
> On Thu, Jun 25, 2009 at 11:41 AM, Nick Alexander wrote:
>>
>>
>> On 25-Jun-09, at 5:10 AM, David Joyner wrote:
>>
>>> Build failed for intel macbook 10.4.11
>>>
>>> Should I post the full log somewhere? Here is the tail:
>>>
>>>
>>> /Users/d
On Jun 25, 10:39 pm, Utpal Sarkar wrote:
> The link to the sage tutorial from the knol article seems to be broken
>
thx, fixed.
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
Unfortunately, I don't have access to a OSX <= 10.4 box otherwise I
would have ported this code to those versions when I originally wrote
the code for this patch. If anyone has a machine available with OSX
10.4 or 10.3 I'd be happy to port this code to it.
On Thu, Jun 25, 2009 at 9:47 AM, Robert
The link to the sage tutorial from the knol article seems to be broken
On Jun 24, 7:19 pm, Harald Schilly wrote:
> On Jun 24, 6:16 pm, Robert Bradshaw
> wrote:
>
> > I'll second this. Wikipedia is the highest source of traffic for
> > Cython after google and people typing in cython.org direc
Hi,
I suspect you're just running out of RAM.
Not necessarily physically, but the construction Sage --> expect
interface --> Maxima --> Lisp implementation is a fragile one. If the
Lisp implementation "thinks" it runs out of space, this is not handled
too gracefully by Maxima, and as a consequenc
Upgrade from 4.0.2 failed (as predicted by the original poster!)
during build of sage.spkg on PPC X.4, with a lot of ImportErrors e.g.
no module named mercurial, no module named jinja (to import from). It
also pulled the outputs of the documentation, which seemed strange to
me (as opposed to buil
Perhaps your computation required more space than was available in the
Lisp system that was running your version of Maxima.
You might, for example, run out of "string" space on some Lisp
systems, without totally using up all storage.
Since you do not give enough information to reproduce your prob
Hi,
On Tue, Jun 23, 2009 at 11:50 PM, William Stein wrote:
>
> Hi,
>
> Video and slides for *all* the talks so far from Sage Days 16 are now
> posted here:
>
> http://wiki.sagemath.org/days16
I have embedded the first two videos here:
http://sage.math.washington.edu/home/ondrej/scratch/sd16/v
On Thu, Jun 25, 2009 at 11:41 AM, Nick Alexander wrote:
>
>
> On 25-Jun-09, at 5:10 AM, David Joyner wrote:
>
>> Build failed for intel macbook 10.4.11
>>
>> Should I post the full log somewhere? Here is the tail:
>>
>>
>> /Users/davidjoyner/sagefiles/sage-4.1.alpha0/local/include/python2.5
>> -c
Hi folks,
On Fri, Jun 26, 2009 at 4:18 AM, Robert Miller wrote:
>
> This release is primarily the Python upgrade.
The following tickets were merged in Sage 4.1.alpha1:
#6085: Robert Miller: Finish full implementation of c_graphs [Reviewed
by Tom Boothby]
#6359: Mike Hansen: update to Python 2
This release is primarily the Python upgrade. The source tarball and
sage.math binary are here:
http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1.tar
http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1-sage.math-only-x86_64-Linux.tar.gz
If you care to try upgrad
Jason Grout wrote:
> When Mike was experimenting with trac 0.11, he made a plugin or
> something that put a "raw" link next to the attachment link, so an
> attachment would look like:
>
> trac_3948_description.patch (raw) Apply on top of previous patches
>
> where clicking on trac_... would br
> Someone please back out patch #6027, and set it to "needs work".
>
> It's clearly is the reason for this brokenness, and wasn't tested on
> Mac OS X 10.4 at all. As it is stated in its comments.
William is working on this right now, and will post a patch
momentarily.
rlm
--~--~-~--~---
Sorry, I forgot to post a location. I will for alpha1, which will drop
shortly.
On Jun 25, 3:39 pm, kcrisman wrote:
> > Is there an -upgrade location to go to?
>
> If the answer is no for the foreseeable future, that's
> understandable. Just asking!
>
> - kcrisman
--~--~-~--~~--
Hi Brendan,
On Thu, 25 Jun 2009 11:58:59 -0400
Brendan Rooney wrote:
> Hello
>
> I am currently attempting to use sage to research graph polynomials.
> In particular, I am trying to generate and store the matchings
> polynomial for as many graphs as is possible. The routines I am
> employing a
Hello
I am currently attempting to use sage to research graph polynomials. In
particular, I am trying to generate and store the matchings polynomial
for as many graphs as is possible. The routines I am employing are
simple, and I have used them extensively (computing the matchings
polynomial f
On 25 Jun., 14:10, David Joyner wrote:
> Build failed for intel macbook 10.4.11
>
> Should I post the full log somewhere? Here is the tail:
>
> /Users/davidjoyner/sagefiles/sage-4.1.alpha0/local/include/python2.5 -c
> sage/misc/darwin_memory_usage.c -o
> build/temp.macosx-10.3-i386-2.5/sage/misc/
On 25-Jun-09, at 5:10 AM, David Joyner wrote:
> Build failed for intel macbook 10.4.11
>
> Should I post the full log somewhere? Here is the tail:
>
>
> /Users/davidjoyner/sagefiles/sage-4.1.alpha0/local/include/python2.5
> -c sage/misc/darwin_memory_usage.c -o build/temp.macosx-10.3-
> i386-
On Thu, Jun 25, 2009 at 02:19:38AM -0700, Jason Grout wrote:
> >> At the bottom of the html view, there's a link entitled "original
> >> format" which gives the raw patch. It's the same as the html-view
> >> url, but with "attachment" replaced with "raw-attachment."
> >>
> >
> > And it is a major
Hi Burcin,
On Wed, Jun 24, 2009 at 6:54 PM, Burcin Erocal wrote:
> I attached a patch to the trac ticket that contains an initial attempt
> at the MMA notation:
>
> http://trac.sagemath.org/sage_trac/ticket/6344
>
>
> It doesn't work well for text mode:
>
> sage: f = function('f')
> sage: f(x).d
William Stein wrote:
>>> Cheers,
>>> Simon
>> Unix is tricky, as Solaris works, on some machines, but is not fully
>> supported. (To be precise about this, one needs a definition of 'support').
>
> Sage works on OS X, and OS X has been officially certified to be "UNIX".
There is a separate
On Thu, 25 Jun 2009 at 09:37AM +0100, John Cremona wrote:
> I did not know that, which will be useful. What is the canonical
> recipe for getting the patch's URL? When I try I sometimes find I
> have downloaded some html thing by mistake.
I didn't know that qimport did that either, so I made thi
>
> Is there an -upgrade location to go to?
If the answer is no for the foreseeable future, that's
understandable. Just asking!
- kcrisman
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send
On Mon, Jun 22, 2009 at 4:29 PM, jyr wrote:
>
> Below is a python script that implements the above and sets
> environment variables for parallel compiles. Just save the script to
> makesage.py (say) in the sage root dir and run it via
>
> python makesage.py -j8
>
> It reduced the sage-4.0.2 compil
Dear all, this seems like a bug to me:
--
| Sage Version 4.0.2, Release Date: 2009-06-18 |
| Type notebook() for the GUI, and license() for information.|
-
Thanks for the quick reply. This is now Ticket #6403. How much effort
would it be to expose this Pynac functionality?
Cheers,
Stan
Burcin Erocal wrote:
> On Thu, 25 Jun 2009 13:22:46 +0200
> Stan Schymanski wrote:
>
>
>> Dear all,
>>
>> I have been asked to forward the below to the sage-dev
On Thu, Jun 25, 2009 at 1:06 PM, Dr. David
Kirkby wrote:
>
> Simon King wrote:
>> Hi
>>
>> On Jun 24, 8:33 pm, kcrisman wrote:
>>> A related page to look at would
>>> behttp://en.wikipedia.org/wiki/Comparison_of_computer_algebra_systems
>
> I updated that somewhat, expanded the description simil
Build failed for intel macbook 10.4.11
Should I post the full log somewhere? Here is the tail:
/Users/davidjoyner/sagefiles/sage-4.1.alpha0/local/include/python2.5 -c
sage/misc/darwin_memory_usage.c -o
build/temp.macosx-10.3-i386-2.5/sage/misc/darwin_memory_usage.o -w
sage/misc/darwin_memory_usa
On Thu, 25 Jun 2009 13:22:46 +0200
Stan Schymanski wrote:
>
> Dear all,
>
> I have been asked to forward the below to the sage-devel list. Ticket
> #6290 introduced a way to custom-define the latex style of functions,
> but it would be great if something similar was made possible for any
>
Dear all,
I have been asked to forward the below to the sage-devel list. Ticket
#6290 introduced a way to custom-define the latex style of functions,
but it would be great if something similar was made possible for any
variable. Is there a way for this already? I used to do it in the
followin
Simon King wrote:
> Hi
>
> On Jun 24, 8:33 pm, kcrisman wrote:
>> A related page to look at would
>> behttp://en.wikipedia.org/wiki/Comparison_of_computer_algebra_systems
I updated that somewhat, expanded the description similar to that for
Mathematica. I removed the 'Boolean Computation' whi
On Thu, Jun 25, 2009 at 11:53 AM, Peter
Jeremy wrote:
> On 2009-Jun-25 09:09:02 +0200, William Stein wrote:
>>The main problems with building Sage on BSD, in my experience, are
>>that (1) you have to "gmake" instead of "make" to run the GNU version
>>of Make, which is a pain,
>
> My approach to t
On 2009-Jun-25 09:09:02 +0200, William Stein wrote:
>The main problems with building Sage on BSD, in my experience, are
>that (1) you have to "gmake" instead of "make" to run the GNU version
>of Make, which is a pain,
My approach to this was to symlink gmake to $SAGE_ROOT/local/bin/make
since the
William Stein wrote:
>
>> * Tools for image processing [5]
>
> yes, in pylab, plus also there is the Python Imagining Library. (PIL)
>
Also, don't forget openCV (http://code.google.com/p/ctypes-opencv/, for
example). There are also a few other references to using openCV with
numpy. N
William Stein wrote:
> On Thu, Jun 25, 2009 at 10:48 AM, Robert
> Bradshaw wrote:
>> On Jun 25, 2009, at 1:37 AM, John Cremona wrote:
>>
>>> 2009/6/25 Jason Grout :
Robert Miller wrote:
I think the following is a counterexample to "The trac_ prefix
does
not bring an
On Thu, Jun 25, 2009 at 10:48 AM, Robert
Bradshaw wrote:
>
> On Jun 25, 2009, at 1:37 AM, John Cremona wrote:
>
>> 2009/6/25 Jason Grout :
>>>
>>> Robert Miller wrote:
>>> I think the following is a counterexample to "The trac_ prefix
>>> does
>>> not bring any useful information."
>>>
On Jun 25, 2009, at 1:37 AM, John Cremona wrote:
> 2009/6/25 Jason Grout :
>>
>> Robert Miller wrote:
>> I think the following is a counterexample to "The trac_ prefix
>> does
>> not bring any useful information."
> I still think it's not really, and it is just making the name
2009/6/25 Jason Grout :
>
> Robert Miller wrote:
> I think the following is a counterexample to "The trac_ prefix does
> not bring any useful information."
I still think it's not really, and it is just making the name longer,
but I don't really care either.
>>> I don't see the us
On Thu, Jun 25, 2009 at 9:17 AM, wrote:
> On 2009-Jun-24 00:56:38 +0100, "Dr. David Kirkby"
> wrote:
>>Would it not be sensible to ask around on some FreeBSD/NetBSD mailing
>>lists etc, and see if one could drum up enough support to start a port?
>
> I've done some work on getting Sage to work
On 2009-Jun-24 00:56:38 +0100, "Dr. David Kirkby"
wrote:
>Would it not be sensible to ask around on some FreeBSD/NetBSD mailing
>lists etc, and see if one could drum up enough support to start a port?
I've done some work on getting Sage to work on FreeBSD but there is
still a way to go. For va
Nick Alexander wrote:
>> I think I'm not communicating my point very clearly. I'm suggesting
>> that the release manager have in his patch application script an
>> automated "prepend 'Trac #: ' to the commit message" step.
>
> I thought of implementing this but couldn't think of a way to dis
On Thu, Jun 25, 2009 at 5:49 AM, Robert
Bradshaw wrote:
>
> On Jun 23, 2009, at 4:56 PM, Dr. David Kirkby wrote:
>
>>
>> From the top README.txt
>>
>> ---
>> NOT SUPPORTED:
>> * FreeBSD
>> * Arch Linux
>> * Gentoo Linux
>>
60 matches
Mail list logo
