Hi all,
3.3.rc2 built fine on MacIntel Core2Duo Mac OS X 10.4.11 with Xcode
2.5, the only testlong failures were:
The following tests failed:
sage -t -long "devel/sage/sage/graphs/graph_plot.py"
sage -t -long "devel/sage/sage/plot/plot.py"
sage -t -long "devel/sage/sage/
Bill must have looked at my hand-crafted web pages, since he knows I
have little design sense. I'm sticking to mathematics, don't
worry. ;-)
Strikes me there are two related ideas being discussed here.
1. How does a new user know/learn how to create a new cell (of either
type)?
Right now, a
> > How about this:
>
> > If you are in a text cell:
> > * ctrl-; splits the text cell, puts in a new math cell, and focuses on
> > the math cell.
>
> > If you are in a math cell:
> > * ctrl-; splits the math cell, focusing on the second math cell
> > * ctrl-shift-; splits the math cell, inser
> > Similarly, current TinyMCE behavior does not seem to join two existing
> > adjacent text cells together - which is not a bug, but just a little
> > weird at times. Say for instance you had a math cell between two text
> > areas and you delete the math cell; should the text areas join or not
>
>
> William Stein wrote:
>> This could be implemented by having a button in the palette on the
>> top to insert a new "math" cell. The cell itself could just be some
>> special HTML (maybe with a comment) that gets post-processed
>> by Sage and turned into an input cell. See the attached "Pict
William Stein wrote:
>
> That is a good idea.
>
> This could be implemented by having a button in the palette on the top to
> insert
> a new "math" cell. The cell itself could just be some special HTML
> (maybe with a comment) that gets post-processed by Sage and turned
> into an input cell.
On Wed, Feb 18, 2009 at 3:58 PM, Nick Alexander wrote:
>
>
> On 18-Feb-09, at 3:30 PM, Nicolas M. Thiery wrote:
>
>>
>> Dear Robert,
>>
>> On Sat, Feb 14, 2009 at 03:57:07PM -0800, Robert Bradshaw wrote:
>>> ...
Would it be possible to add the following functionality (with
whateve
On 18-Feb-09, at 3:30 PM, Nicolas M. Thiery wrote:
>
> Dear Robert,
>
> On Sat, Feb 14, 2009 at 03:57:07PM -0800, Robert Bradshaw wrote:
>> ...
>>> Would it be possible to add the following functionality (with
>>> whatever
>>> appropriate syntax):
>>>
>>> declare_conversion(source, t
On Feb 18, 2009, at 09:33 , mabshoff wrote:
>
> Hello folks,
>
> 3.3.rc2 has been out for a good half day, but we are only announcing
> it now since I did build it over night on a bunch of machines. Enough
> people were hanging out in IRC to know that it was ready, so we are
> having a good idea
Dear Robert,
On Sat, Feb 14, 2009 at 03:57:07PM -0800, Robert Bradshaw wrote:
> ...
> > Would it be possible to add the following functionality (with whatever
> > appropriate syntax):
> >
> > declare_conversion(source, target, morphism)
> >
> > which would adds the morphism from sourc
On Feb 18, 3:35 pm, mabshoff wrote:
> Normally you would either run
>
> make test
> or
> make testlong
Yeah, I included that line since I knew there was the possibility I
was doing it wrong. After running 'make test', I get on
"devel/sage/sage/plot/plot.py".
> > Evidently there's still a
On Wed, Feb 18, 2009 at 4:21 PM, Jason Grout wrote:
>
> kcrisman wrote:
>
>>
>> Also (this is now just wild speculation) would it ever be possible to
>> make a new math cell *in the middle of a text cell*? That would be
>> really awesome, let me tell you. Though perhaps impossible?
>
> Can you g
mabshoff wrote:
> Ooops, I forgot to mention one very important thing to do, so here
> goes another double post: If you are upgrading make sure to delete
> matplotlibrc from
>
> * $SAGE_ROOT
> * $SAGE_ROOT/tmp
> * $DOT_SAGE
>
> since otherwise you will see a lot of deprecation warnings during
>
> > 3. A segfault on OS X 10.5 32-bit Intel (bsd.math.washington.edu):
>
> > sage -t -long "devel/sage/sage/schemes/elliptic_curves/ell_finite_field.py"
> > A mysterious error (perphaps a memory error?) occurred, which may have
> > crashed doctest.
> > [22.7 s]
>
> > Doing this again w
kcrisman wrote:
>
> Also (this is now just wild speculation) would it ever be possible to
> make a new math cell *in the middle of a text cell*? That would be
> really awesome, let me tell you. Though perhaps impossible?
Can you give us a more specific use-case? You mean, you want to "split
On Feb 18, 12:28 pm, mark mcclure wrote:
> On Feb 18, 12:33 pm, mabshoff wrote:
Hi Mark,
> > 3.3.rc2 has been out for a good half day,
>
> Build went smoothly on my Intel MacPro running OS X 10.5.5.
> Passed all tests from 'sage -t devel/sage/sage/misc/all.py'.
Mhh, did you just test that f
On Feb 18, 12:33 pm, mabshoff wrote:
> 3.3.rc2 has been out for a good half day,
Build went smoothly on my Intel MacPro running OS X 10.5.5.
Passed all tests from 'sage -t devel/sage/sage/misc/all.py'.
Evidently there's still a little more to building the groovy Sage.app,
though?
Mark McClure
On Feb 18, 11:48 am, mark mcclure wrote:
> On Feb 18, 1:44 pm, mabshoff wrote:
Hi Mark,
> > Ok, I know what went wrong. I assume this is a MacIntel. Can you send
> > me the complete compressed log?
>
> Correct, this is an Intel based Mac. I'll gzip the log and email it
> to you
> shortly.
>
On Feb 18, 1:44 pm, mabshoff wrote:
> Ok, I know what went wrong. I assume this is a MacIntel. Can you send
> me the complete compressed log?
Correct, this is an Intel based Mac. I'll gzip the log and email it
to you
shortly.
Mark McClure
--~--~-~--~~~---~--~~
On Feb 18, 11:16 am, William Stein wrote:
> This is about 3.3.rc2.
>
> 1. On my macbookpro os x 10.5 intel,
> sage -t -long "devel/sage/sage/misc/package.py"
> **
> File "/Users/wstein/build/build/sage-3.3.rc2/devel/sage/sage/
On Wed, Feb 18, 2009 at 7:36 AM, Alex McFerron wrote:
> It turns out that it will not be possible for me to make these dates due to
> a work conflict but i hope to make another one.
>
> Will anyone be at PyCon in Chicago from Sage?
I don't know of anybody who will be. I've cc'd this response to
This is about 3.3.rc2.
1. On my macbookpro os x 10.5 intel,
sage -t -long "devel/sage/sage/misc/package.py"
**
File "/Users/wstein/build/build/sage-3.3.rc2/devel/sage/sage/misc/package.py",
line 50:
sage: sage.misc.package.i
On Feb 18, 10:41 am, mark mcclure wrote:
> On Feb 18, 12:33 pm, mabshoff wrote:
Hi Mark,
> > 3.3.rc2 has been out for a good half day,
>
> I get an error building GMP on my MacBook Pro running
> OS X 10.4.11. The partial log, starting where I think
> things went awry, is below.
Ok, I know
On Feb 18, 12:33 pm, mabshoff wrote:
> 3.3.rc2 has been out for a good half day,
I get an error building GMP on my MacBook Pro running
OS X 10.4.11. The partial log, starting where I think
things went awry, is below.
It's currently building on my Mac Pro with OS X 10.5.5
and looks good so far.
On Wed, Feb 18, 2009 at 9:20 AM, mabshoff wrote:
>
>
>
> On Feb 18, 8:37 am, Martin Albrecht
> wrote:
>> > So I'd like to know whether the focus should be on trying to
>> > get Macaulay2 integrated in Sage, or to develop this stuff natively in Sage
>> > using Macaulay2 as a cheat sheet (= portin
Ooops, I forgot to mention one very important thing to do, so here
goes another double post: If you are upgrading make sure to delete
matplotlibrc from
* $SAGE_ROOT
* $SAGE_ROOT/tmp
* $DOT_SAGE
since otherwise you will see a lot of deprecation warnings during
doctesting.
Cheers,
Michael
--~
On Wed, Feb 18, 2009 at 12:03 PM, Jason Grout wrote:
>
> Bill Page wrote:
>>
>> What if the bar included "evaluate" as well?
>> ___
>> |__ evaluate |_ new command _| new text _|
>
>
>
> A problem with this pro
Hello folks,
3.3.rc2 has been out for a good half day, but we are only announcing
it now since I did build it over night on a bunch of machines. Enough
people were hanging out in IRC to know that it was ready, so we are
having a good idea what is left to be fixed since some people already
reporte
On Feb 18, 8:37 am, Martin Albrecht
wrote:
> > So I'd like to know whether the focus should be on trying to
> > get Macaulay2 integrated in Sage, or to develop this stuff natively in Sage
> > using Macaulay2 as a cheat sheet (= porting functionality to Sage bit by
> > bit, I guess is what I'm s
Bill Page wrote:
> On Wed, Feb 18, 2009 at 12:39 AM, Rob Beezer wrote:
>> Sure! The best of both worlds?
>
> I do not consider this the "best" but rather a "lowest common
> denominator" kind of thing. I quite dislike the evaluate links
> scattered down the page, although I have seen many times t
Not sure what I think about the various annotate ideas, though
probably something like this should be available. It is actually
quite important what you call it, because none of the names (new text,
annotate, etc.) seems to quite characterize it. I don't have any
better ideas, unfortunately.
I
> So I'd like to know whether the focus should be on trying to
> get Macaulay2 integrated in Sage, or to develop this stuff natively in Sage
> using Macaulay2 as a cheat sheet (= porting functionality to Sage bit by
> bit, I guess is what I'm saying).
Hi, due to the issues pointed out by Michael
Its true, new users love the evaluate button. It would be nice to
have an expert mode, or perhaps "elegant" mode, that turned that off.
But for beginners, I like the idea of an "annotate" button on the
right, opposite the evaluate button.
-Marshall
On Feb 18, 3:31 pm, Bill Page wrote:
> On Wed
On Wed, Feb 18, 2009 at 12:39 AM, Rob Beezer wrote:
>
> Sure! The best of both worlds?
I do not consider this the "best" but rather a "lowest common
denominator" kind of thing. I quite dislike the evaluate links
scattered down the page, although I have seen many times that this is
what almost ev
On Feb 18, 5:01 am, Alex Ghitza wrote:
> Hi sage-devel,
Hi Alex,
> I'm trying to get ready for Sage Days 14, and given the focus of the
> workshop some natural questions that occur to me (and are bound to be asked)
> are:
>
> (1) What is the current relationship between Macaulay2 and Sage?
>
Hi sage-devel,
I'm trying to get ready for Sage Days 14, and given the focus of the
workshop some natural questions that occur to me (and are bound to be asked)
are:
(1) What is the current relationship between Macaulay2 and Sage?
(2) Could we eventually make Macaulay2 a standard package? How ab
Carl Witty wrote:
> Unfortunately, it's far too slow to be useful for anything ...
cool story, but how about sympy, have you tried it? it's maybe worth a
try!
h
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe f
37 matches
Mail list logo
