I forward the following from sage-support because I know to little to
answer those issues competently and I also think those questions
shouldn't pass uncommented:
From:
http://groups.google.com/group/sage-support/browse_thread/thread/c46950723108a191#
Hi there,
here are some bugs which may or ma
On 2012-02-19 06:53, John H Palmieri wrote:
> On the plus side, on the laptop where I had problems before, Sage built
> and passed all doctests using the default compiler:
You mean 5.0.beta4 worked or do you mean my 5.0.beta4-gcc?
--
To post to this group, send an email to sage-devel@googlegroups
Hi Keshav (et al.),
I think the reason I implemented the kludgy "sage -clone" Sage branch
thing (way back in maybe March 2006) was because we had no dependency
checking for Pyrex files. Now that we have dependency checking,
lightweight branching should be able to accomplish the same thing much
m
On Sun, Feb 19, 2012 at 9:38 PM, Keshav Kini wrote:
> Hope that helps. Evidently other people in this thread do not know that
> I have been maintaining a git version of the Sage library, so hopefully
> it will help them too, if they're interested :)
Can we add a better .gitignore?
git status
...
On Sun, Feb 19, 2012 at 9:38 PM, Keshav Kini wrote:
> William Stein writes:
>> Hi Keshav (/Sage-devel),
>>
>> I want to switch to using git to develop the core Sage library (though
>> I'll still submit patches using hg for now).
>> How can I do this?
>
> Hi William,
>
> Just fork sagemath/sagelib
Mike Hansen writes:
> This doesn't seem to be what William wants -- he wants to make the
> changes in git and be able to contribute those to Sage (as if he
> hadn't used git). Other than producing patches with git and then say
> qimporting them into hg, the best bet looks to be
> https://github.c
Jonathan writes:
> For example I'm trying to patch base.pyx inside SAGE_ROOT/devel/sage/
> sage/plot/plot3d and get this error message
> {{{
> unable to find 'plot/plot3d/base.pyx' for patching
> }}}
> I assume this means I somehow made the patch with the incorrect path.
> What should the root of
William Stein writes:
> Hi Keshav (/Sage-devel),
>
> I want to switch to using git to develop the core Sage library (though
> I'll still submit patches using hg for now).
> How can I do this?
Hi William,
Just fork sagemath/sagelib on github, then do
$ cd $SAGE_ROOT/devel/
$ git clone g...@githu
On Sun, Feb 19, 2012 at 12:58 PM, Mike Hansen wrote:
> On Sun, Feb 19, 2012 at 12:39 PM, Minh Nguyen wrote:
>> To preserve the commit history under Mercurial, we need to convert
>> from hg to git format. This can be done using various tools. I've
>> personally used fast-export [1] before to con
Dear sage-dev gurus,
I've made some patches to upgrade the interface of Jmol once the Flask
notebook is rolled into Sage (trac #12299). However, when I tried to
apply my own patches to a copy of 5.0.betaX with the Flask installed,
I get the error that the file/directory can't be found.
For exampl
About import_statements which does the following:
sage: import_statements(RationalField, IntegerRing)
from sage.rings.rational_field import RationalField
from sage.rings.integer_ring import IntegerRing
On Sat, Feb 18, 2012 at 12:34:41PM -0800, Anne Schilling wrote (slightly edited)
>
On Sun, Feb 19, 2012 at 12:39 PM, Minh Nguyen wrote:
> To preserve the commit history under Mercurial, we need to convert
> from hg to git format. This can be done using various tools. I've
> personally used fast-export [1] before to convert a hg repository to a
> git repo. From there, we shoul
Hi William,
On Mon, Feb 20, 2012 at 6:21 AM, William Stein wrote:
> I want to switch to using git to develop the core Sage library (though
> I'll still submit patches using hg for now).
> How can I do this?
To preserve the commit history under Mercurial, we need to convert
from hg to git format.
Hi Keshav (/Sage-devel),
I want to switch to using git to develop the core Sage library (though
I'll still submit patches using hg for now).
How can I do this?
William
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
--
To post to this group, send an email
14 matches
Mail list logo
