[sage-devel] Re: limit bug that I'm really sure used to work correctly

Yes Maxima's unsigned inf is converted to Sage's unsigned inf. And: sage: unsigned_infinity Infinity versus sage: +Infinity +Infinity So you really got unsigned inf first. BTW, SymPy names it zoo which I like. On Wednesday, June 8, 2016 at 6:48:48 AM UTC+2, john_perry_usm wrote: > > I decide

[sage-devel] Re: limit bug that I'm really sure used to work correctly

I decided to dig further. Maxima's documentation contains information that Sage's docs lack: infinity (complex infinity) is returned when the limit of the absolute > value of the expression is positive infinity, but the li

Re: [sage-devel] proposal: possibly remove Watkins Sympow from Sage

> On 8/06/2016, at 10:14, William Stein wrote: > > On Tue, Jun 7, 2016 at 6:12 PM, Francois Bissey > wrote: >> The version from the sage-on-gentoo overlay has been hacked to explicitly >> write data generated by the user in ~/.sympow. If indeed you make a system >> wide install where the user c

[sage-devel] Build Error for 7.3 beta 3 on Mac OS X 10.11.5

You need to perform an explicit installation of the Xcode command line tools. I had the same error recently and that solved it. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send

Re: [sage-devel] Build Error for 7.3 beta 3 on Mac OS X 10.11.5

Not really without some logs. But I guess I’ll try locally at some point… when I have dealt with other problems... François > On 8/06/2016, at 10:33, Rebecca Miller wrote: > > Any thoughts on how to get around this? > -- You received this message because you are subscribed to the Google Grou

[sage-devel] Build Error for 7.3 beta 3 on Mac OS X 10.11.5

I'm having trouble building the newest beta. I have updated my OS X and XCode to the latest version. I have make distclean. The error I'm getting is " Error installing package gcc-4.9.3.p1". Any thoughts on how to get around this? Thanks, Rebecca M -- You received this message because you ar

Re: [sage-devel] proposal: possibly remove Watkins Sympow from Sage

On Tue, Jun 7, 2016 at 6:12 PM, Francois Bissey wrote: > The version from the sage-on-gentoo overlay has been hacked to explicitly > write data generated by the user in ~/.sympow. If indeed you make a system > wide install where the user cannot write it will certainly fail. This is indeed exactly

Re: [sage-devel] proposal: possibly remove Watkins Sympow from Sage

The version from the sage-on-gentoo overlay has been hacked to explicitly write data generated by the user in ~/.sympow. If indeed you make a system wide install where the user cannot write it will certainly fail. I don’t remember if I or Christopher did the hack or if we lifted it from a debian

[sage-devel] Re: limit bug that I'm really sure used to work correctly

I should elaborate on this after rereading the limit documentation more carefully. It states: Return the limit as the variable v approaches a from the given direction. expr.limit(x = a) expr.limit(x = a, dir='above') INPUT: * "dir" - (default: None); dir may have the valu

[sage-devel] limit bug that I'm really sure used to work correctly

This surprised me today: > limit(1/x, x=0) Infinity I was expecting something more like this: > limit(x/abs(x), x=0) und The help on Infinity wasn't illuminating: > Infinity? Type: PlusInfinity String form: +Infinity ...and so forth. This implies to me that Infinity and +Infinity a

[sage-devel] Program for Sage Days 78

Dear all, the program for Sage Days 78 in Vancouver is now on line: https://wiki.sagemath.org/days78 If you intend to join us please register if you haven't done so already! Best Viviane -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsu

[sage-devel] Re: Build failure Sage 7.3.beta3 on Mac OS 10.9 with binary-pkg

> > I'm wondering, if we should delete the beta3 and beta0 variants to avoid > confusion? > That definitely seems like the right move to me. Nathan -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receivi

[sage-devel] Re: Build failure Sage 7.3.beta3 on Mac OS 10.9 with binary-pkg

On Tuesday, June 7, 2016 at 8:20:49 PM UTC+2, Harald Schilly wrote: > > On Tue, Jun 7, 2016 at 8:06 PM, Karl-Dieter Crisman wrote: > > What I meant was of course for someone to take the binaries kindly > mentioned ... > ok, files landed, and one of them is 7.1 which seems to been already ther

Re: [sage-devel] sage infrastructure at UW

On Tuesday, June 7, 2016 at 6:27:41 PM UTC+1, kcrisman wrote: > > Having now read the comment [1] I agree that while it may not be true > about French universities in general, it was certainly phrased as "my > experience" and was limited to the relatively narrow technical comment of > who admi

Re: [sage-devel] Re: hosting wiki and trac

On Jun 7, 2016 19:36, "kcrisman" wrote: > > > >> >> >> +1 to hosting at at Tier 1 cloud provider >> >> > > > Just as a point of information, are there any other "Tier 1 cloud providers" who might be alternatives (usable for Sage development) for anyone who has some philosophical objection to one p

Re: [sage-devel] Re: hosting wiki and trac

On Tuesday, June 7, 2016 at 6:36:26 PM UTC+1, kcrisman wrote: > > > > >> >> +1 to hosting at at Tier 1 cloud provider >> >> >> > > Just as a point of information, are there any other "Tier 1 cloud > providers" who might be alternatives (usable for Sage development) for > anyone who has some

[sage-devel] Re: Build failure Sage 7.3.beta3 on Mac OS 10.9 with binary-pkg

On Tue, Jun 7, 2016 at 8:06 PM, Karl-Dieter Crisman wrote: > What I meant was of course for someone to take the binaries kindly mentioned > earlier in this thread (at http://unhyperbolic.org/sage/) and put them to > the general place, not any particular mirror. I don't have that capability. Ahh,

[sage-devel] Re: Build failure Sage 7.3.beta3 on Mac OS 10.9 with binary-pkg

Volker Braun wrote: > Thats probably the shebang length limit. Can you try to reduce LENGTH in > binary_pkg/path_placeholder.py (80 or so should keep you in the limit, then) Or try exporting SAGE_BUILD_DIR (the temporary folder in which spkgs are built) with some shorter path; not sure whether tha

[sage-devel] Re: Build failure Sage 7.3.beta3 on Mac OS 10.9 with binary-pkg

On Tue, Jun 7, 2016 at 7:32 PM, kcrisman wrote: > > Harald, could you do that? We could use more binaries for various versions > of OS X. I'm not building any osx binaries and I don't think anyone has push capabilities for the mit mirror. In doubt, just use the main http://files.sagemath.org/osx

[sage-devel] Re: Build failure Sage 7.3.beta3 on Mac OS 10.9 with binary-pkg

> > > > Harald, could you do that? We could use more binaries for various > versions > > of OS X. > > I'm not building any osx binaries and I don't think anyone has push > capabilities for the mit mirror. In doubt, just use the main > http://files.sagemath.org/osx/intel/index.html > > What I meant

[sage-devel] Re: SageMath 7.3.beta3 build failure on OS X versions 10.8 and 10.9.

> > Is there a ticket for this? > I just created one --- trac was down when I posted originally: http://trac.sagemath.org/ticket/20779#ticket Nathan -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop recei

Re: [sage-devel] Re: hosting wiki and trac

> >> +1 to hosting at at Tier 1 cloud provider > >> > Just as a point of information, are there any other "Tier 1 cloud providers" who might be alternatives (usable for Sage development) for anyone who has some philosophical objection to one particular such provider? Also, not to beat a

[sage-devel] Re: SageMath 7.3.beta3 build failure on OS X versions 10.8 and 10.9.

On Monday, June 6, 2016 at 4:08:06 PM UTC-4, Nathan Dunfield wrote: > > I have successfully compiled Sage 7.2, which has an earlier version of >> NTL, from source on both 10.8 and 10.9. >> > > Checking the logs for my Sage 7.2 builds, the old NTL version 9.6.2 spkg > did *not* specify the "-ma

[sage-devel] Re: Build failure Sage 7.3.beta3 on Mac OS 10.9 with binary-pkg

Let me know about this and I will try it out. I had a LOT of trouble using binary-pkg a couple weeks ago (computer was essentially unusable for hours) and it seems to do a heck of a lot more than the old sage-bdist, so if this is the new normal it would be nice to make it as error-free as possi

Re: [sage-devel] sage infrastructure at UW

Having now read the comment [1] I agree that while it may not be true about French universities in general, it was certainly phrased as "my experience" and was limited to the relatively narrow technical comment of who administrators might feel comfortable allowing access to. I have already bee

Re: [sage-devel] Re: sage infrastructure at UW

I'll let you know tomorrow. It's possible someone already added me, but if so they used a key that's only on a computer I'm not using right now Erik On Tue, Jun 7, 2016 at 1:00 PM, Volker Braun wrote: > Sholud have been public key, of course. Though you all can send me your > private keys, too,

Re: [sage-devel] Re: sage infrastructure at UW

Sholud have been public key, of course. Though you all can send me your private keys, too, if you want ;-) On Tuesday, June 7, 2016 at 12:59:08 PM UTC-4, Jan Groenewald wrote: > > > On 7 June 2016 at 18:54, Volker Braun > > wrote: > >> I can probably set you up if you send me your private key.

Re: [sage-devel] Re: sage infrastructure at UW

On Tue, Jun 7, 2016 at 12:54 PM, Volker Braun wrote: > Right now its apache; You should really go and look around on the > trac.sagemath.org vm for how its set up right now. If you don't have an > account there I can probably set you up if you send me your private key. Oh, it's back up again! I

Re: [sage-devel] Re: sage infrastructure at UW

On 7 June 2016 at 18:54, Volker Braun wrote: > I can probably set you up if you send me your private key. private key or public key? Regards, Jan -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receivin

[sage-devel] Re: sage infrastructure at UW

On Tue, Jun 7, 2016 at 12:50 PM, Erik Bray wrote: > On Tue, Jun 7, 2016 at 12:14 PM, Volker Braun wrote: >> On Tuesday, June 7, 2016 at 11:22:10 AM UTC-4, William wrote: >>> >>> Erik has volunteered to setup trac, and will do so soon. >> >> >> There are a bunch of caveats to that one as far as I

[sage-devel] Re: sage infrastructure at UW

Right now its apache; You should really go and look around on the trac.sagemath.org vm for how its set up right now. If you don't have an account there I can probably set you up if you send me your private key. On Tuesday, June 7, 2016 at 12:50:27 PM UTC-4, Erik Bray wrote: > > On Tue, Jun 7, 2

[sage-devel] Re: Build failure Sage 7.3.beta3 on Mac OS 10.9 with binary-pkg

Dima Pasechnik wrote: > On Tuesday, June 7, 2016 at 5:18:15 PM UTC+1, leif wrote: > > Nathan Dunfield wrote: > > I used the instructions on > https://github.com/sagemath/binary-pkg > > >

Re: [sage-devel] Developing sage-based code out of tree

On Sun, Jun 05, 2016 at 11:25:01PM -0400, William Stein wrote: > We had tons of discussion on sage-devel about exactly this topic > recently. One thing is that Chris made > > https://github.com/cswiercz/sage_packages > > but that seems to have gone nowhere. There is also this wiki page that we

[sage-devel] Re: sage infrastructure at UW

On Tue, Jun 7, 2016 at 12:14 PM, Volker Braun wrote: > On Tuesday, June 7, 2016 at 11:22:10 AM UTC-4, William wrote: >> >> Erik has volunteered to setup trac, and will do so soon. > > > There are a bunch of caveats to that one as far as I remember: > > * The ssh key management plugin for trac shar

[sage-devel] Re: Build failure Sage 7.3.beta3 on Mac OS 10.9 with binary-pkg

Thats probably the shebang length limit. Can you try to reduce LENGTH in binary_pkg/path_placeholder.py (80 or so should keep you in the limit, then) On Tuesday, June 7, 2016 at 12:18:15 PM UTC-4, leif wrote: > > Nathan Dunfield wrote: > > I used the instructions on https://github.com/sage

[sage-devel] Re: sage infrastructure at UW

On Tuesday, June 7, 2016 at 5:37:47 PM UTC+1, Volker Braun wrote: > > Our git server is read/write, of course. Authentication is so that only > you can push to branches matching u/dimpase/.*, and that is handled by > gitolite. > > There is no authentication for the cgit repo viewer, as you said

[sage-devel] Re: sage infrastructure at UW

Our git server is read/write, of course. Authentication is so that only you can push to branches matching u/dimpase/.*, and that is handled by gitolite. There is no authentication for the cgit repo viewer, as you said. Ideally, everything but the git server and the trac database would be separa

Re: [sage-devel] Re: Developing sage-based code out of tree

> > That made me think that sage fails to set everything required to let > "--user" work properly (I noticed installation path names containing > ".../.sage/..." so at least it was trying something distinct from what > python would do in a standard config.) > Hmmm, I install Python packages in

[sage-devel] Re: Build failure Sage 7.3.beta3 on Mac OS 10.9 with binary-pkg

On Tuesday, June 7, 2016 at 5:18:15 PM UTC+1, leif wrote: > > Nathan Dunfield wrote: > > I used the instructions on https://github.com/sagemath/binary-pkg > > to build sage .app.dmg > > packages for Mac OS 10.9. > > It works for 7.1 and

[sage-devel] Re: sage infrastructure at UW

On Tuesday, June 7, 2016 at 5:14:01 PM UTC+1, Volker Braun wrote: > > On Tuesday, June 7, 2016 at 11:22:10 AM UTC-4, William wrote: >> >> Erik has volunteered to setup trac, and will do so soon. > > > There are a bunch of caveats to that one as far as I remember: > > * The ssh key management plu

[sage-devel] Re: Build failure Sage 7.3.beta3 on Mac OS 10.9 with binary-pkg

Nathan Dunfield wrote: > I used the instructions on https://github.com/sagemath/binary-pkg > to build sage .app.dmg > packages for Mac OS 10.9. > It works for 7.1 and 7.2*, but I compiling ECL failed with the > attached log for 7.3.beta3

Re: [sage-devel] Re: Developing sage-based code out of tree

On Tuesday, June 7, 2016 at 8:18:04 AM UTC-7, William wrote: > > The standard way to build in place but have things written to a search > path is > > python setup.py develop --user > > Yes, initially I tried a version of that (perhaps with "install" rather than "develop"), but it didn't w

[sage-devel] Re: sage infrastructure at UW

On Tuesday, June 7, 2016 at 11:22:10 AM UTC-4, William wrote: > > Erik has volunteered to setup trac, and will do so soon. There are a bunch of caveats to that one as far as I remember: * The ssh key management plugin for trac shares the keys over the local file system with gitolite authentica

[sage-devel] Re: proposal: possibly remove Watkins Sympow from Sage

On Tuesday, June 7, 2016, John Cremona wrote: > Yes, modular degrees -- I use sympow for that to compute modular > degrees for (almost) every curve in my tables. I could instead use > Magma or revert to using my own installation of sympow, which I used > to do before Sage either one of whic

Re: [sage-devel] Fwd: proposal: possibly remove Watkins Sympow from Sage

Yes, modular degrees -- I use sympow for that to compute modular degrees for (almost) every curve in my tables. I could instead use Magma or revert to using my own installation of sympow, which I used to do before Sage either one of which seems like a step backwards! John On 7 June 2016 at

Re: [sage-devel] Developing sage-based code out of tree

> > While this might work for simple projects, this won't work when you need > the metadata that cythonize() adds. For example, anything using > cysignals really must use cythonize(), it won't work otherwise. > Jeroen, As of Cython 0.22, it looks like the metadata you refer to is cached in th

Re: [sage-devel] Developing sage-based code out of tree

On 2016-06-07 17:20, William Stein wrote: I was going to post that my understanding is that shipping Cython-generated files is the current standard way of shipping Cython code (for better or worse). While this might work for simple projects, this won't work when you need the metadata that cyth

[sage-devel] Fwd: proposal: possibly remove Watkins Sympow from Sage

Some very useful remarks from Mark... -- Forwarded message -- From: Mark Watkins Date: Tue, Jun 7, 2016 at 11:43 AM Subject: Re: proposal: possibly remove Watkins Sympow from Sage To: William Stein William Stein wrote: > > Hi, > > Long ago in 2006, I put Mark Watkins amazing C

Re: [sage-devel] proposal: possibly remove Watkins Sympow from Sage

I have been wondering why the LMFDB, which builds on Sage, has its own version of sympow. (It's what allows web pages like http://www.lmfdb.org/L/SymmetricPower/3/EllipticCurve/Q/11.a/ to appear). That code was written by Mark himself, but I don't know why he moved the two files in https://github

Re: [sage-devel] Developing sage-based code out of tree

> > > Agreed, it's certainly what the Cython docs recommend: > > > > > http://docs.cython.org/src/reference/compilation.html#distributing-cython-modules > > > Ah, okay. I didn't see that before. At least it's the recommended > best practice. It should be easier to do automatically though

Re: [sage-devel] Re: hosting wiki and trac

On Tue, Jun 7, 2016 at 9:54 AM, William Stein wrote: > On Tue, Jun 7, 2016 at 9:42 AM, Volker Braun wrote: >> +1 to hosting at at Tier 1 cloud provider >> >> Also, if you have any arguments pro or con then send it to the mailinglist >> and not to William's private email. > > +1 -- SageMath should

Re: [sage-devel] Developing sage-based code out of tree

On Tue, Jun 7, 2016 at 11:27 AM, Nathan Dunfield wrote: >> > Interesting, I didn't realize that build-time (as opposed to run-time) >> > dependencies were even *possible* with setuptools, even if it does >> > require a >> > hack. With SnapPy, we just ship the Cython-generated C/C++-files in the >

Re: [sage-devel] Developing sage-based code out of tree

On Tue, Jun 7, 2016 at 11:20 AM, William Stein wrote: > On Tue, Jun 7, 2016 at 11:18 AM, Nathan Dunfield wrote: >> Erik, >> >> Interesting, I didn't realize that build-time (as opposed to run-time) >> dependencies were even *possible* with setuptools, even if it does require a >> hack. With Snap

Re: [sage-devel] Developing sage-based code out of tree

> > > Interesting, I didn't realize that build-time (as opposed to run-time) > > dependencies were even *possible* with setuptools, even if it does > require a > > hack. With SnapPy, we just ship the Cython-generated C/C++-files in the > > tarball that we post on PyPI. > > I was going to pos

[sage-devel] Re: hosting wiki and trac

+1 for Google, I'm not a data-paranoiac, these are open data, and better (ob)served by Google than the French gov (or any other nation). -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from

Re: [sage-devel] Re: Developing sage-based code out of tree

On Tue, Jun 7, 2016 at 11:17 AM, William Stein wrote: > On Tue, Jun 7, 2016 at 11:14 AM, Nils Bruin wrote: >> On Sunday, June 5, 2016 at 12:59:57 PM UTC-7, Nils Bruin wrote: >>> >>> The problem arose specifically when I was looking at >>> https://github.com/abelfunctions/abelfunctions which packa

Re: [sage-devel] Developing sage-based code out of tree

Erik, Interesting, I didn't realize that build-time (as opposed to run-time) dependencies were even *possible* with setuptools, even if it does require a hack. With SnapPy, we just ship the Cython-generated C/C++-files in the tarball that we post on PyPI. It adds a bit to the tarball's size,

[sage-devel] Re: sage infrastructure at UW

On Tue, Jun 7, 2016 at 11:12 AM, William Stein wrote: > Hi, > > The Air Conditioning and power at UW have been fixed, and everything > turned back on. I've pointed DNS back at trac.sagemath.org and > wiki.sagemath.org so you should see them shortly. > > I'm setting up very frequent periodic auto

Re: [sage-devel] Developing sage-based code out of tree

On Tue, Jun 7, 2016 at 11:18 AM, Nathan Dunfield wrote: > Erik, > > Interesting, I didn't realize that build-time (as opposed to run-time) > dependencies were even *possible* with setuptools, even if it does require a > hack. With SnapPy, we just ship the Cython-generated C/C++-files in the > tar

Re: [sage-devel] Re: Developing sage-based code out of tree

On Tue, Jun 7, 2016 at 11:14 AM, Nils Bruin wrote: > On Sunday, June 5, 2016 at 12:59:57 PM UTC-7, Nils Bruin wrote: >> >> The problem arose specifically when I was looking at >> https://github.com/abelfunctions/abelfunctions which packages itself as an >> spkg. Obviously, I didn't want to install

Re: [sage-devel] sage infrastructure at UW

On Tuesday, June 7, 2016 at 3:24:43 PM UTC+1, Thierry (sage-googlesucks@xxx) wrote: > > Hi, > > On Mon, Jun 06, 2016 at 02:35:22PM -0400, William Stein wrote: > [...] > > I am flat out strongly against hosting the Sage wiki, trac, etc.,. > > They should be properly hosted in the cloud, where

[sage-devel] Re: Developing sage-based code out of tree

On Sunday, June 5, 2016 at 12:59:57 PM UTC-7, Nils Bruin wrote: > > The problem arose specifically when I was looking at > https://github.com/abelfunctions/abelfunctions which packages itself as > an spkg. Obviously, I didn't want to install this (when trying it out!) in > a system-wide sage, bu

[sage-devel] Re: sage infrastructure at UW

Hi, The Air Conditioning and power at UW have been fixed, and everything turned back on. I've pointed DNS back at trac.sagemath.org and wiki.sagemath.org so you should see them shortly. I'm setting up very frequent periodic automatic backups right now to /orig on the GCE machines. I eagerly aw

Re: [sage-devel] proposal: possibly remove Watkins Sympow from Sage

On 2016-06-07 16:10, William Stein wrote: I do have to wonder why this isn't tested. I think that it's not tested because it writes data files in $SAGE_ROOT. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and sto

[sage-devel] Re: proposal: possibly remove Watkins Sympow from Sage

Also works in Sage 7.2 for me on OS X version 10.9 and a hoary RHEL 6 derivative. In both cases, Sage was compiled straight from the source tarball. Nathan -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop

Re: [sage-devel] sage infrastructure at UW

On Tue, Jun 07, 2016 at 10:35:19AM -0400, William Stein wrote: > Hi Thierry, > > I don't really know who you are, and I've never met you. But given > your claims that I'm "spreading wrong and racist statements about > french universities"... etc., I guess I do now. Many thanks for the > clarifi

[sage-devel] Re: proposal: possibly remove Watkins Sympow from Sage

It also works for me on two different gentoo boxes. Both compiling locally from source and in a system wide sage-on-gentoo install. El martes, 7 de junio de 2016, 16:28:34 (UTC+2), John H Palmieri escribió: > > > > On Tuesday, June 7, 2016 at 7:11:08 AM UTC-7, William wrote: >> >> Hi, >> >> Long

Re: [sage-devel] Re: proposal: possibly remove Watkins Sympow from Sage

On Tue, Jun 7, 2016 at 10:28 AM, John H Palmieri wrote: > > > On Tuesday, June 7, 2016 at 7:11:08 AM UTC-7, William wrote: >> >> Hi, >> >> Long ago in 2006, I put Mark Watkins amazing C program "sympow" in Sage: >> >> >> http://doc.sagemath.org/html/en/reference/lfunctions/sage/lfunctions/sympow.h

Re: [sage-devel] sage infrastructure at UW

Hi Thierry, I don't really know who you are, and I've never met you. But given your claims that I'm "spreading wrong and racist statements about french universities"... etc., I guess I do now. Many thanks for the clarification. -- William On Tue, Jun 7, 2016 at 8:32 AM, Thierry wrote: > Hi,

[sage-devel] Re: Build failure Sage 7.3.beta3 on Mac OS 10.9 with binary-pkg

> > I used the instructions on https://github.com/sagemath/binary-pkg to > build sage .app.dmg packages for Mac OS 10.9. > It works for 7.1 and 7.2*, but I compiling ECL failed with the attached > log for 7.3.beta3 - this seems to be a regression. > Weird, I was able to build the ECL in 7.3.bet

[sage-devel] Re: proposal: possibly remove Watkins Sympow from Sage

On Tuesday, June 7, 2016 at 7:11:08 AM UTC-7, William wrote: > > Hi, > > Long ago in 2006, I put Mark Watkins amazing C program "sympow" in Sage: > > > http://doc.sagemath.org/html/en/reference/lfunctions/sage/lfunctions/sympow.html > > > In case you're not a number theorist, this progra

Re: [sage-devel] sage infrastructure at UW

Hi, On Mon, Jun 06, 2016 at 02:35:22PM -0400, William Stein wrote: [...] > I am flat out strongly against hosting the Sage wiki, trac, etc.,. > They should be properly hosted in the cloud, where anybody can be > added as admins, FUD > we can make global backups, FUD > move the machines to ha

[sage-devel] proposal: possibly remove Watkins Sympow from Sage

Hi, Long ago in 2006, I put Mark Watkins amazing C program "sympow" in Sage: http://doc.sagemath.org/html/en/reference/lfunctions/sage/lfunctions/sympow.html In case you're not a number theorist, this program computes values of generating functions attached to symmetric power representation

Re: [sage-devel] Re: hosting wiki and trac

On Tue, Jun 7, 2016 at 9:42 AM, Volker Braun wrote: > +1 to hosting at at Tier 1 cloud provider > > Also, if you have any arguments pro or con then send it to the mailinglist > and not to William's private email. +1 -- SageMath should be as open a project as possible. See, e.g., "Avoid Private D

[sage-devel] Re: hosting wiki and trac

+1 to hosting at at Tier 1 cloud provider Also, if you have any arguments pro or con then send it to the mailinglist and not to William's private email. On Tuesday, June 7, 2016 at 8:28:07 AM UTC-4, William wrote: > > Hi, > > I am being pressured by various people to host trac and wiki in Par

[sage-devel] hosting wiki and trac

Hi, I am being pressured by various people to host trac and wiki in Paris henceforth. Technically, "the cloud" is now a far superior platform for hosting as compared to "some guy with some computers at a specific university". For starter, it is easy to make the compute available in any of numerou

Re: [sage-devel] Developing sage-based code out of tree

On Tue, Jun 7, 2016 at 9:53 AM, Erik Bray wrote: > On Mon, Jun 6, 2016 at 5:01 PM, Jeroen Demeyer wrote: >> On 2016-06-06 16:05, William Stein wrote: >>> >>> Isn't there one canonical one to use now? >> >> >> I guess the "canonical" one is setuptools. But setuptools makes the annoying >> assumpti

Re: [sage-devel] Developing sage-based code out of tree

On Tue, Jun 7, 2016 at 10:59 AM, Jeroen Demeyer wrote: > On 2016-06-07 10:57, Erik Bray wrote: >> >> Yes, but it's a pain in the butt to do and would require support from >> the setuptools end > > > I must be missing something... setuptools allows declaring dependencies, > right? Yes but again th

Re: [sage-devel] Developing sage-based code out of tree

On 2016-06-07 10:57, Erik Bray wrote: Yes, but it's a pain in the butt to do and would require support from the setuptools end I must be missing something... setuptools allows declaring dependencies, right? -- You received this message because you are subscribed to the Google Groups "sage-d

Re: [sage-devel] Developing sage-based code out of tree

On Tue, Jun 7, 2016 at 10:36 AM, Jeroen Demeyer wrote: > On 2016-06-07 10:21, Erik Bray wrote: >> >> It's one thing to depend on a package at runtime. It's another thing >> to have a dependency just so that `./setup.py --help` can work without >> raising an ImportError :) > > > Well, could it be

Re: [sage-devel] Developing sage-based code out of tree

On 2016-06-07 10:21, Erik Bray wrote: It's one thing to depend on a package at runtime. It's another thing to have a dependency just so that `./setup.py --help` can work without raising an ImportError :) Well, could it be possible to arrange things such that Cython is needed at *build-time* b

Re: [sage-devel] Developing sage-based code out of tree

On 2016-06-07 10:19, Francois Bissey wrote: It does exactly what it should. “—root” is the equivalent of DESTDIR for autotooled packages. It is meant for use by distribution to install in a staging area. No, really not! I think that --root/DESTDIR should only change the absolute installation p

Re: [sage-devel] Developing sage-based code out of tree

On Tue, Jun 7, 2016 at 10:17 AM, Jeroen Demeyer wrote: > On 2016-06-07 09:56, Erik Bray wrote: >> >> This should probably be fixed. Do you know if there has been any >> discussion about this or just a lack of maintenance? > > > No idea. > >>> I don't mind assuming that Cython is installed. It mak

Re: [sage-devel] Developing sage-based code out of tree

On Tue, Jun 7, 2016 at 10:14 AM, Jeroen Demeyer wrote: > On 2016-06-07 09:53, Erik Bray wrote: >> >> $ ./setup.py install --root=root > > > Well, it seems that setuptools behaves completely differently if --root is > set, no idea why... I explained this is because --root implicitly disables easy_

Re: [sage-devel] Developing sage-based code out of tree

> On 7/06/2016, at 20:14, Jeroen Demeyer wrote: > > On 2016-06-07 09:53, Erik Bray wrote: >> $ ./setup.py install --root=root > > Well, it seems that setuptools behaves completely differently if --root is > set, no idea why... > > With --root=/tmp > > [...] > copying banshees.txt -> /tmp/usr

Re: [sage-devel] Developing sage-based code out of tree

On 2016-06-07 09:56, Erik Bray wrote: This should probably be fixed. Do you know if there has been any discussion about this or just a lack of maintenance? No idea. I don't mind assuming that Cython is installed. It makes things a lot simpler. Users will mind, I guarantee it There are ma

Re: [sage-devel] Developing sage-based code out of tree

On 2016-06-07 09:53, Erik Bray wrote: $ ./setup.py install --root=root Well, it seems that setuptools behaves completely differently if --root is set, no idea why... With --root=/tmp [...] copying banshees.txt -> /tmp/usr/local/src/sage-git/local/shared/siouxsie [...] Without --root [...]

Re: [sage-devel] Developing sage-based code out of tree

On Tue, Jun 7, 2016 at 9:24 AM, Jeroen Demeyer wrote: > On 2016-06-07 08:55, Erik Bray wrote: >> >> In fact Cython used >> to advertise a CythonBuildExt command (i forget of that's exactly the >> name) that overrides the default build_ext command to also compile >> Cython modules as needed. > > >

Re: [sage-devel] Developing sage-based code out of tree

On Mon, Jun 6, 2016 at 5:01 PM, Jeroen Demeyer wrote: > On 2016-06-06 16:05, William Stein wrote: >> >> Isn't there one canonical one to use now? > > > I guess the "canonical" one is setuptools. But setuptools makes the annoying > assumption that a Python package is completely self-contained and t

Re: [sage-devel] Developing sage-based code out of tree

On 2016-06-07 08:55, Erik Bray wrote: In fact Cython used to advertise a CythonBuildExt command (i forget of that's exactly the name) that overrides the default build_ext command to also compile Cython modules as needed. This still exists in the Cython package, but they no longer document it.