Mike Hansen writes:
> There is a patch at http://trac.sagemath.org/sage_trac/ticket/12659
> which builds the Sage library in place just using distutils.
Yup, I'm subscribed to the ticket :) I just found out about distutils2
and thought I'd mention it here.
-Keshav
Join us in #sagemath on i
There is a patch at http://trac.sagemath.org/sage_trac/ticket/12659
which builds the Sage library in place just using distutils.
--Mike
On Sat, Mar 17, 2012 at 10:36 AM, Keshav Kini wrote:
> Hmm. What is this? http://stackoverflow.com/a/6522905 Maybe it's worth
> looking into using this new thin
Hmm. What is this? http://stackoverflow.com/a/6522905 Maybe it's worth
looking into using this new thing?
-Keshav
Join us in #sagemath on irc.freenode.net !
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+u
> We should. The only reason we don't is because when I set things up
> in 2004 (?) I think setuptools "python setup.py develop" either didn't
> exist, or I had never heard of it. What *should* happen is that we
> use setuptools instead of distutils, and the Sage library would live
> 100% and o
"Nicolas M. Thiery" writes:
> Besides, this would solve the problem of unrelevant files not being
> cleared up from the build directory when applying / unapplying patches
> which create new files. I have just been hit by this, and this
> confused Sphinx, and it was a pain to fix.
I was just about
William Stein writes:
> On Fri, Mar 9, 2012 at 11:17 PM, Keshav Kini wrote:
>> Jeroen Demeyer writes:
>>> On 2012-03-09 15:48, Keshav Kini wrote:
I'm probably missing something obvious, but why do you need a repository
in order to apply a patch to files? Doesn't `patch` work fine?
>>>
