On 2014-05-31, Volker Braun wrote:
> On Saturday, May 31, 2014 1:42:44 AM UTC+1, Dima Pasechnik wrote:
>>
>> everything, as for rebuilding docs nothing short of "make distclean &&
>> make" works.
>>
>
> sage -sync-build && sage -b && make doc-clean && make doc
>
> almost always works (there has
IMHO: use gap.Lucas(1,-1,10), or even better libgap.Lucas(1,-1,10).
Function call notation is more readable than eval calls.
Here is the libgap fix for huge ints (needs review):
http://trac.sagemath.org/16419
On Saturday, May 31, 2014 5:35:21 PM UTC+1, Travis Scrimshaw wrote:
>
> First
First encountered by Ralf on #15625, Sage can't translate back from GAP
with eval for extremely large numbers:
sage: ans=gap.eval("Lucas(%s,%s,%s)[1]"%(1,-1,100))
sage: ans
'354224848179261915075'
sage: ans=gap.eval("Lucas(%s,%s,%s)[1]"%(1,-1,10))
sage: ans
''
although this does work for
gap
On Saturday, May 31, 2014 3:14:41 PM UTC+1, leif wrote:
>
> Did someone meanwhile track down what exactly went wrong / broke
> docbuilding (such that it hangs)?
>
I can't reproduce it, works for me.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" grou
And which part of it being a common assumption among git users that the
first merge commit points back to the branch did you not understand?
On Saturday, May 31, 2014 2:52:15 PM UTC+1, Nathann Cohen wrote:
>
> That's my question from last november :
> https://groups.google.com/d/msg/sage-git/Nok
Volker Braun wrote:
On Saturday, May 31, 2014 1:42:44 AM UTC+1, Dima Pasechnik wrote:
everything, as for rebuilding docs nothing short of "make distclean &&
make" works.
sage -sync-build && sage -b && make doc-clean && make doc
almost always works (there has been maybe one case where
By the way I improved this gtmp method since, so that it prepares a
commit message which makes the history clearer (at least to a human)
function gtmp
{
cd ~/sage
git checkout d
rel="$(git log --oneline d ^d~1 | sed s/.*\ //g)"
tn="$(echo "$1" | grep -o "[0-9]*")"
echo "===
> There is nothing wrong with merges
>
> * if you need them
> * if the original branch is the first parent.
>
> Doing it the wrong way makes the history more difficult to understand, and
> we shouldn't teach or facilitate that antipattern.
That's my question from last november :
https://groups.goo
There is nothing wrong with merges
* if you need them
* if the original branch is the first parent.
Doing it the wrong way makes the history more difficult to understand, and
we shouldn't teach or facilitate that antipattern.
On Saturday, May 31, 2014 2:35:30 PM UTC+1, Nathann Cohen wrote:
Yo !
> If you want to edit the ticket branch (that is, add additional
> commits) you cannot use `git trac try`. You must use `git trac
> checkout` to get the actual ticket branch as a starting point.
Why can't you add commits after a merge ? I do this all the time O_o
Nathann
--
You rece
I've implemented a version of this now. From the README:
* Review tickets with minimal recompiling. This assumes that you are
currently on the "develop" branch, that is, the latest beta. Just
checking out an older ticket would most likely reset the Sage tree
to an older version, so you would
#16260: Python 2.7.6
#16415: Ignore case in package directory
http://trac.sagemath.org/ticket/16260
http://trac.sagemath.org/ticket/16415
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails fro
On Friday, May 30, 2014 5:11:08 PM UTC+1, kcrisman wrote:
> Right, but the problem is that currently I am uploading it ;-)
Which is exactly why it ought to be difficult to make wrong-way merges in a
branch, so that you can't accidentally/misguidedly upload without
understanding enough of git t
On Saturday, May 31, 2014 1:42:44 AM UTC+1, Dima Pasechnik wrote:
>
> everything, as for rebuilding docs nothing short of "make distclean &&
> make" works.
>
sage -sync-build && sage -b && make doc-clean && make doc
almost always works (there has been maybe one case where it didn't, and
that w
14 matches
Mail list logo
