Hi,
MSRI has decided to generously fund and host a 2-week graduate student
summer Sage Days workshop on some area of number theory this coming summer:
June 28 - July 9, 2010. So if you're a grad student at an "MSRI sponsoring
institution" (there are many such) and are interested in attending, be
Thank you for your excellent work on canvas3d! I never imagined
canvas3d finding a place on smartphones, but this is really exciting.
Maybe someday Sage could be an iPhone app!
We should figure out how to incorporate this code into Sage. Is is
legal for us to use a modified version of Pre3d? Pete
On Tue, 06 Oct 2009 at 03:25PM +0100, Dr. David Kirkby wrote:
> With Winter approaching, I was looking for a way to heat my garage
> somewhat to stop the water freezing. (There's a small room in the
> garage, which has water)
>
> I thought running my HP C3600 HP-UX workstation would make a good
>
On Tue, 06 Oct 2009 at 03:23AM -0700, Robert Bradshaw wrote:
> Is there not a way to invoke a bash script in such a way that it
> can't change the invoking environment?
You sound like you want the `env' command:
env FOO=bar command args
runs "command args" with the variable $FOO set to "ba
Robert Miller wrote:
>> However, Robert Miller has been notably silent on this topic. We
>> should try to get him to weigh in before making any sweeping
>> decisions, since he's (at the very least) the most familiar with the
>> code.
>
> I have spent months trying to make function calls just lik
> As far as it being *possible* to split up graph.py... It's a ten
> minute job, but nobody's done it. You could split it in three right
> away by having generic_graph.py, graph.py and digraph.py.
+1
Nick
--~--~-~--~~~---~--~~
To post to this group, send an email
> However, Robert Miller has been notably silent on this topic. We
> should try to get him to weigh in before making any sweeping
> decisions, since he's (at the very least) the most familiar with the
> code.
I have spent months trying to make function calls just like, e.g.
G.predecessors(3), as
On Tue, Oct 6, 2009 at 8:30 AM, Nick Alexander wrote:
>> That's probably for the best -- it was a pretty bad idea, and any
>> implementation that one comes up with is probably going to be terrible
>> in one way or another. Don't do it.
>
> I (and you?) did something similar for torsion subgroup
On Tue, Oct 6, 2009 at 1:45 PM, john_perry_usm wrote:
>
> Hi,
>
> From what I can tell, Sage lacks an explicit function to compute
> implicit derivatives, akin say to Maple's implicit_diff command. See
> this (really) old thread:
>
>
> http://groups.google.com/group/sage-devel/browse_thread/t
William Stein wrote:
> > This code below *should* have been in sage-env, not every single
> > spkg-install. If that had been the case, I doubt you would be so
> > annoyed by it, since you could trivially just delete the Darwin part:
> >
> > if [ `uname` = "Darwin" -a $SA
On 6 Okt., 22:15, Jason Grout wrote:
> Please reply with any comments.
>
only organisatorial: trac also has a wiki system, it would be good to
actually use it for information like this!
my proposal: go to http://trac.sagemath.org/sage_trac/wiki/guidelines
and create the page, add this info, mov
Robert Bradshaw wrote:
> I still think the issue field should be a select menu (to make
> searching easier).
I agree (at least, making it a set of checkboxes, anyway---a menu only
allows one selection, but surely we'd like to specify several areas in
which the ticket needs work). I'm just n
We just finished putting the new workflow on trac. From now on, instead
of declaring the status of a ticket using "[with patch, needs review]"
and other such annotations on the title, please select the appropriate
status at the bottom of the ticket. For a typical ticket, you'll be
able to ch
On Oct 6, 2009, at 10:08 AM, Jason Grout wrote:
>
> Robert Bradshaw wrote:
>> On Oct 1, 2009, at 7:17 PM, Jason Grout wrote:
>>
>>> Robert Bradshaw wrote:
>>>
I think process rather than ownership centric is a good move.
Certainly better than what we have. Is there a "merged" transition
On Tue, Oct 6, 2009 at 11:11 AM, Dr. David Kirkby
wrote:
>
> William Stein wrote:
>
> > Also, the suggestion(s) to put the -m64 stuff in sage-env make a huge
> > amount of sense to me. The more that is factored out and less redundant
> > in the spkg's the better. In fact, that's a good general p
On Tue, Oct 6, 2009 at 11:47 AM, Enrique Gonzalez Jimenez <
enrique.gonzalez.jime...@gmail.com> wrote:
> Hi!
>
> The following output in a MacPro with Snow Leopard (OS X 10.6):
>
> luna:Oct09 enrique$ /Applications/sage/sage
> --
Hi Enrique,
On Wed, Oct 7, 2009 at 5:47 AM, Enrique Gonzalez Jimenez
wrote:
> Hi!
>
> The following output in a MacPro with Snow Leopard (OS X 10.6):
>
> luna:Oct09 enrique$ /Applications/sage/sage
> --
> | Sage Version 4.1.1, R
Hi!
The following output in a MacPro with Snow Leopard (OS X 10.6):
luna:Oct09 enrique$ /Applications/sage/sage
--
| Sage Version 4.1.1, Release Date: 2009-08-14 |
| Type notebook() for the GUI, and license(
On Oct 6, 2009, at 10:08 AM, Jason Grout wrote:
>
> Robert Bradshaw wrote:
>> On Oct 1, 2009, at 7:17 PM, Jason Grout wrote:
>>
>>> Robert Bradshaw wrote:
>>>
I think process rather than ownership centric is a good move.
Certainly better than what we have. Is there a "merged" transition
William Stein wrote:
> Also, the suggestion(s) to put the -m64 stuff in sage-env make a huge
> amount of sense to me. The more that is factored out and less redundant
> in the spkg's the better. In fact, that's a good general principle in
> coding.
OK, so what should we factor out? (I'll us
Hi,
>From what I can tell, Sage lacks an explicit function to compute
implicit derivatives, akin say to Maple's implicit_diff command. See
this (really) old thread:
http://groups.google.com/group/sage-devel/browse_thread/thread/f374f76bb3cd0361
Is this still the current situation? I've wri
Dear All,
Here is the full content of the file linear.py... I particularly like the
second comment (2006-12) from William :-). I was just wondering if there is a
reason to keep this file other than anyone didi take care of removing it...
Cheers,
Florent
"""
Linear Groups
AUTHORS:
- W
Robert Bradshaw wrote:
> On Oct 1, 2009, at 7:17 PM, Jason Grout wrote:
>
>> Robert Bradshaw wrote:
>>
>>> I think process rather than ownership centric is a good move.
>>> Certainly better than what we have. Is there a "merged" transition
>>> from positive review to closed?
>> I was imagining th
On Tue, Oct 6, 2009 at 3:12 AM, Dr. David Kirkby wrote:
>
> Simon King wrote:
> > Hi!
> >
> > On Oct 6, 9:22 am, Robert Bradshaw
> > wrote:
> >> Even easier, it seems, would be to to add -m46 (or equivalent) to
> >> CFLAGS directly in sage-env, rather than having the if [ $SAGE64 ...]
> >> test i
Rob Beezer wrote:
> On Oct 3, 2:47 am, Nathann Cohen wrote:
>> DiGraph.out_neighbors() and DiGraph.in_neighbors() would be much easier to
>> find and more natural...
>
> I'd suggest
>
> neighbors_in()
> neighbors_out()
> neighbors()
>
> to make tab completion easier and to group them next to e
>> I have no clue how to write what you are describing. Graph.neighbors
>> would be a subobject, does that mean an independent class ? Wouldn't
>> this slow down the whole Graph class, as these functions are among
>> the
>> most used ? Here I feel that I do not know Python enough to
>> help..
With Winter approaching, I was looking for a way to heat my garage
somewhat to stop the water freezing. (There's a small room in the
garage, which has water)
I thought running my HP C3600 HP-UX workstation would make a good
heater. In fact the machine is throwing out very little heat - far le
Robert Bradshaw wrote:
> We're talking about the IRC channels here, not the mailing lists,
> which should certainly stay separate. Currently, there's rarely
> anyone logged into #sage-support, so it's not near as helpful as
> #sage-devel (where some people do hang out).
>
> - Robert
Oops,
Robert Bradshaw wrote:
> On Oct 6, 2009, at 3:12 AM, Dr. David Kirkby wrote:
>> Hence it's probably safer to have each spkg-install start with
>>
>> CFLAGS=$SAGE64_CFLAG
>>
>> and add others as needed.
>>
>> This would not be an issue if someone write
>>
>> ./configure CFLAGS="$CFLAGS -foobar"
>>
On Oct 6, 12:23 pm, "Dr. David Kirkby"
wrote:
> One way is to compare the postings for *support* issues to sage-support...
not postings, IRC channel! #sage-support (# implies irc channel) is
quasi dead and you only get answers if you are in #sage-devel.
Anyways, there is now a link to the irc l
On Oct 6, 2009, at 3:23 AM, Dr. David Kirkby wrote:
>
> Harald Schilly wrote:
>
>> I only included the most useful and often visited pages, also, until
>> recently it pointed to the #sage-support channel where support was
>> rather bad and nobody there. Do you think it's better now after
>> redir
Harald Schilly wrote:
> I only included the most useful and often visited pages, also, until
> recently it pointed to the #sage-support channel where support was
> rather bad and nobody there. Do you think it's better now after
> redirecting all support to #sage-devel?
>
> H
One thing I believe
On Oct 6, 2009, at 3:12 AM, Dr. David Kirkby wrote:
> Simon King wrote:
>> Hi!
>>
>> On Oct 6, 9:22 am, Robert Bradshaw
>> wrote:
>>> Even easier, it seems, would be to to add -m46 (or equivalent) to
>>> CFLAGS directly in sage-env, rather than having the if
>>> [ $SAGE64 ...]
>>> test in ever
Simon King wrote:
> Hi!
>
> On Oct 6, 9:22 am, Robert Bradshaw
> wrote:
>> Even easier, it seems, would be to to add -m46 (or equivalent) to
>> CFLAGS directly in sage-env, rather than having the if [ $SAGE64 ...]
>> test in every spkg-install.
>
> This sounds reasonable to me. If I am not
On Oct 6, 4:14 am, Jason Grout wrote:
> Is there a link to the IRC logs on sagemath.org?
Logs are very new and the questions is, if their location is final ;)
> I also half-expected "IRC" to be one of the links next to
> the search box on the top.
I only included the most useful and often vi
Hi!
On Oct 6, 9:22 am, Robert Bradshaw
wrote:
> Even easier, it seems, would be to to add -m46 (or equivalent) to
> CFLAGS directly in sage-env, rather than having the if [ $SAGE64 ...]
> test in every spkg-install.
This sounds reasonable to me. If I am not mistaken, it has the
additional a
On Oct 6, 2009, at 12:07 AM, Dr. David Kirkby wrote:
>
> William Stein wrote:
>
>> I think a bit over a year ago there was no SAGE64 flag. Then Michael
>> Abshoff decided "Hey, I'll port Sage to 64-bit OS X!".He then
>> introduced a SAGE64 flag and used it specifically for the 64-bit OS X
>
William Stein wrote:
> On Wed, Sep 30, 2009 at 2:50 PM, Dr. David Kirkby
>> Dave
>>
>> If you have $50 spare in your grants, perhaps offer $50 prize to anyone
>> that can find the *real* cause! That might drum up a bit more interest
>> in solving a problem on a platform which most people do not u
William Stein wrote:
> I think a bit over a year ago there was no SAGE64 flag. Then Michael
> Abshoff decided "Hey, I'll port Sage to 64-bit OS X!".He then
> introduced a SAGE64 flag and used it specifically for the 64-bit OS X
> port.He then systematically went through *every* packag
39 matches
Mail list logo
