[sage-devel] RE: Sage Days: Transitioning to Git

Time to commit: If you plan on participating and will not need lodging or any significant reimbursements (such as if you live in the Portland area, or are planning on participating remotely), feel free to update the wiki page appropriately. Otherwise, please send me an email with an estimate of yo

Re: [sage-devel] Re: sage 5.6.beta1 build error (mercurial-2.2.2.p0) on OS X 10.8.2

On Sunday, January 6, 2013 11:16:10 PM UTC, Robert Zeier wrote: > I can share the updates and/or the diffs. > Did you mean http://trac.sagemath.org/13898 ? > Should I ask for a trac account ? > Please do. Instructions are on the Sage trac homepage. -- You received this message because you are s

Re: [sage-devel] Re: sage 5.6.beta1 build error (mercurial-2.2.2.p0) on OS X 10.8.2

I can share the updates and/or the diffs. Did you mean http://trac.sagemath.org/13898 ? Should I ask for a trac account ? Am Samstag, 5. Januar 2013 10:29:35 UTC+1 schrieb Volker Braun: > > Can you post your updated spkgs to > http://trac.sagemath.org/sage_trac/ticket/13309, or at least the diffs

[sage-devel] Re: Where is SAGE_DATA?

Hi Volker, On 2013-01-06, Volker Braun wrote: > In fact, $SAGE_ROOT data is not in the tarball but a symlink that something > creates during build. It is not deleted during "make distclean" but becomes > a dangling symlink. Ah! It is a symlink to SAGE_SHARE! So, I'll be using SAGE_SHARE instea

[sage-devel] Re: Where is SAGE_DATA?

In fact, $SAGE_ROOT data is not in the tarball but a symlink that something creates during build. It is not deleted during "make distclean" but becomes a dangling symlink. On Sunday, January 6, 2013 8:56:43 PM UTC, Simon King wrote: > > Hi! > > I just noticed that SAGE_DATA seems to have disa

[sage-devel] Where is SAGE_DATA?

Hi! I just noticed that SAGE_DATA seems to have disappeared (sage-5.6.beta2), which means that my modular group cohomology package will soon need to be upgraded. However, SAGE_ROOT/data still exists. Question: What is the right place to put a database into? Is os.path.join(SAGE_ROOT,"data") fine

[sage-devel] Re: Failing doctest for sage_getsourcelines

Hi! On 2013-01-06, Simon King wrote: > On 2013-01-06, Julien Puydt wrote: >> I now get a failing doctest: >> sage: cython('''cpdef test_funct(x,y): return''') >> sage: sage_getsourcelines(test_funct) >> (['cpdef test_funct(x,y): return\n'], 6) >> now returns (['cpdef t

Re: [sage-devel] Re: How to make Sage worksheets publically available

On Sat, Jan 5, 2013 at 9:14 AM, Jason Grout wrote: > On 1/4/13 8:11 PM, William Stein wrote: > >> >> >> On Fri, Jan 4, 2013 at 2:50 PM, Dan Drake > **> wrote: >> >> On Fri, 04 Jan 2013 at 11:30AM +, John Cremona wrote: >> > Have others found a good soluti

[sage-devel] Re: Failing doctest for sage_getsourcelines

Hi! On 2013-01-06, Julien Puydt wrote: > I now get a failing doctest: > sage: cython('''cpdef test_funct(x,y): return''') > sage: sage_getsourcelines(test_funct) > (['cpdef test_funct(x,y): return\n'], 6) > now returns (['cpdef test_funct(x,y): return\n'], 5) > > I have

[sage-devel] Failing doctest for sage_getsourcelines

Hi, I'm working on trac #12728 -- and hence I'm patching sage by changing include paths in the code, not really changing said source code. I now get a failing doctest: sage: cython('''cpdef test_funct(x,y): return''') sage: sage_getsourcelines(test_funct) (['cpdef test_