Re: [sagemath-admins] Re: [sage-devel] Re: http://trac.sagemath.org vs https://trac.sagemath.org

Thats what I initially said about stuff necessarily being on the same file system; Afair our trac plugin creates the merge object in the git store and cgit then displays the diff; I think it in https://github.com/sagemath/sage_trac_plugin/blob/master/sage_trac/git_merger.py On Wednesday,

Re: [sagemath-admins] Re: [sage-devel] Re: http://trac.sagemath.org vs https://trac.sagemath.org

On Wed, Jun 8, 2016 at 7:06 PM, Andrew wrote: > On Wednesday, 8 June 2016 18:03:47 UTC+2, Erik Bray wrote: >> >> On another note, I have a copy of trac.sagemath.org up and running on >> GCE here: http://104.197.143.230/ >> >> In the process of setting it up I also

Re: [sagemath-admins] Re: [sage-devel] Re: http://trac.sagemath.org vs https://trac.sagemath.org

On Wed, Jun 8, 2016 at 7:03 PM, Volker Braun wrote: > The diff viewer doesn't work; I'm not sure if its supposed to but here we > go: > > 1) go to http://104.197.143.230/ticket/20739 > 2) Click on Branch: public/20739 > > Results in: > > Bad object name:

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

John Cremona wrote: > William, how much work would it be for a good student programmer to > rewrite sympow in a way which would make everyone happy? I expect that > Mark would cooperate even though he does not seem to want to do this > himself. Sympow is in several separate files so the task

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

William, how much work would it be for a good student programmer to rewrite sympow in a way which would make everyone happy? I expect that Mark would cooperate even though he does not seem to want to do this himself. Sympow is in several separate files so the task could be split up. One

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

Dima Pasechnik wrote: > > > On Wednesday, June 8, 2016 at 3:28:26 PM UTC+1, Jeroen Demeyer wrote: > > On 2016-06-08 15:07, William Stein wrote: > > Thanks. Here is the *actual* code from sympow: > > > > fclose(F); printf("Left with %i entries in param_data\n",i); > >

[sage-devel] Re: http://trac.sagemath.org vs https://trac.sagemath.org

El miércoles, 8 de junio de 2016, 15:46:47 (UTC+2), Frédéric Chapoton escribió: > > What about https for patchbot.sagemath.org ? > > @mmarco, I can open an account for you on this machine if you want. > > Sure. If you give me an email address, I can send you my RSA keys. That looks great--I

Re: [sagemath-admins] Re: [sage-devel] Re: http://trac.sagemath.org vs https://trac.sagemath.org

On Wednesday, 8 June 2016 18:03:47 UTC+2, Erik Bray wrote: > > On another note, I have a copy of trac.sagemath.org up and running on > GCE here: http://104.197.143.230/ > > In the process of setting it up I also upgraded to the latest Trac > version (1.1.6). If anyone has a minute please give

Re: [sagemath-admins] Re: [sage-devel] Re: http://trac.sagemath.org vs https://trac.sagemath.org

The diff viewer doesn't work; I'm not sure if its supposed to but here we go: 1) go to http://104.197.143.230/ticket/20739 2) Click on Branch: public/20739 Results in: Bad object name: cbb26b6406d3a1665299fdd3e2f32cf08e7de7ac On Wednesday, June 8, 2016 at 12:03:47 PM UTC-4, Erik Bray wrote:

Re: [sagemath-admins] Re: [sage-devel] Re: http://trac.sagemath.org vs https://trac.sagemath.org

On another note, I have a copy of trac.sagemath.org up and running on GCE here: http://104.197.143.230/ In the process of setting it up I also upgraded to the latest Trac version (1.1.6). If anyone has a minute please give it a look and see if anything seems amiss (the data itself is a couple

Re: [sagemath-admins] Re: [sage-devel] Re: http://trac.sagemath.org vs https://trac.sagemath.org

On Wed, Jun 8, 2016 at 11:04 AM, Volker Braun wrote: > Of course trac pages are mostly dynamic content, so this would only help > with a couple of icons etc. I'm pretty sure Trac tickets can be cached by the browser. Every time a ticket is modified its modification time

Re: [sagemath-admins] Re: [sage-devel] Re: http://trac.sagemath.org vs https://trac.sagemath.org

Of course trac pages are mostly dynamic content, so this would only help with a couple of icons etc. On Wednesday, June 8, 2016 at 8:54:20 AM UTC-4, William wrote: > > Of some relevance -- Harald Schilly was recently in the process of > putting a CloudFlare 'pro subscription' in front of all

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

On 2016-06-08 16:52, Dima Pasechnik wrote: F=fopen("datafiles/param_data","w"); for (j=0;j

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

On Wednesday, June 8, 2016 at 3:28:26 PM UTC+1, Jeroen Demeyer wrote: > > On 2016-06-08 15:07, William Stein wrote: > > Thanks. Here is the *actual* code from sympow: > > > > fclose(F); printf("Left with %i entries in param_data\n",i); > > F=fopen("datafiles/param_data","w"); > > ...

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

On 2016-06-08 15:07, William Stein wrote: Thanks. Here is the *actual* code from sympow: fclose(F); printf("Left with %i entries in param_data\n",i); F=fopen("datafiles/param_data","w"); ... The interesting stuff is what is below the fopen() call, i.e. the stuff hidden by the "..."

[sage-devel] Re: http://trac.sagemath.org vs https://trac.sagemath.org

What about https for patchbot.sagemath.org ? @mmarco, I can open an account for you on this machine if you want. Le mercredi 8 juin 2016 12:34:48 UTC+2, mmarco a écrit : > > I volunteered some time ago to set up a letsencrypt certificate in the > wiki. I didn't include trac server in that move

Re: [sage-devel] Re: Sage infrastructure repository + GitHub cleanup

On Wed, Jun 8, 2016 at 8:50 AM, Volker Braun wrote: > Some of those repos are out of date, too. If in doubt check with whats > actually on the trac VM. > > Really we need a better (any!) configuration management. E.g. by having a > repo with salt/ansible/... VM

Re: [sagemath-admins] Re: [sage-devel] Re: http://trac.sagemath.org vs https://trac.sagemath.org

On Wed, Jun 8, 2016 at 2:53 PM, William Stein wrote: > Of some relevance -- Harald Schilly was recently in the process of > putting a CloudFlare 'pro subscription' in front of all *.sagemath.org > domains, for caching yes, I'm still pursuing that. The last missing piece is how

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

On Wed, Jun 8, 2016 at 5:10 AM, leif wrote: > Jeroen Demeyer wrote: >> On 2016-06-08 00: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

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

> You can work around it by always requesting a bool around > symbolic equations. > It = your problem, not the bug -- 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 an

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

> unsigned_infinity is Infinity False > Infinity is +Infinity True I agree this should be designed better by giving complex oo a different print string like UnsignedInfinity. sage: limit(1/x, x=0) == unsigned_infinity True This is a bug because it should show an equation. Good catch! You can

Re: [sagemath-admins] Re: [sage-devel] Re: http://trac.sagemath.org vs https://trac.sagemath.org

Of some relevance -- Harald Schilly was recently in the process of putting a CloudFlare 'pro subscription' in front of all *.sagemath.org domains, for caching and anti-DDOS protection, etc. CloudFlare provides that they terminate for all sites that they proxy. However it's obviously good (but

[sage-devel] Re: Sage infrastructure repository + GitHub cleanup

Some of those repos are out of date, too. If in doubt check with whats actually on the trac VM. Really we need a better (any!) configuration management. E.g. by having a repo with salt/ansible/... VM configuration or dockerfiles etc. Having a VM thats being prodded by a dozen different admins

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

(Argh. If my phrase "typed Infinity" is unclear: I meant "Infinity when typed by the user at the prompt or in a cell," not "typed" in a programming language sense.) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group

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

OK, a bit more work & two things cleared up. This was just dumb on my part: > limit(1/x, x=0) is unsigned_infinity That should definitely be False, no disagreement there. I had misunderstood the meaning of the word "is". (Insert political joke here.) Further, this behavior actually makes

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

Thank you! Still, the following behavior is awfully confusing to me: > unsigned_infinity Infinity > unsigned_infinity is Infinity False > Infinity is +Infinity True > limit(1/x, x=0) is unsigned_infinity False > (limit(1/x, x=0) == +Infinity).full_simplify() 1 I'd think the the answers after the

Re: [sage-devel] Re: http://trac.sagemath.org vs https://trac.sagemath.org

Le mercredi 8 juin 2016 12:53:38 UTC+2, Erik Bray a écrit : > > On Wed, Jun 8, 2016 at 6:34 AM, mmarco > wrote: > > I volunteered some time ago to set up a letsencrypt certificate in the > wiki. > > I didn't include trac server in that move because there was already the

Re: [sage-devel] Re: http://trac.sagemath.org vs https://trac.sagemath.org

On Wed, Jun 8, 2016 at 6:34 AM, mmarco wrote: > I volunteered some time ago to set up a letsencrypt certificate in the wiki. > I didn't include trac server in that move because there was already the > option for https, but I agree it would be better to make it https only. That

[sage-devel] Re: http://trac.sagemath.org vs https://trac.sagemath.org

I volunteered some time ago to set up a letsencrypt certificate in the wiki. I didn't include trac server in that move because there was already the option for https, but I agree it would be better to make it https only. -- You received this message because you are subscribed to the Google

[sage-devel] Sage infrastructure repository + GitHub cleanup

Hi, sorry for yet another thread. Actually this is two separate topics but they came up in the same context. There are a lot of files related to sage's website infrastructure that would be nice to keep track of better than rummaging around on servers and making occasional full disk backups. I'm

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

Erik Bray wrote: > On Tue, Jun 7, 2016 at 12:04 PM, Nathan Dunfield wrote: >>> 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

[sage-devel] http://trac.sagemath.org vs https://trac.sagemath.org

Hi all, It occurs to me that trac.sagemath.org has http and https configurations. Is there a reason for this? On the http site even authentication is handled in the clear. The https site, however, has an expired certificate. Two questions: a) Why both sites? Why not just https? b) Who is

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

On Tue, Jun 7, 2016 at 12:04 PM, Nathan Dunfield wrote: >> 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. > > >

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

Jeroen Demeyer wrote: > On 2016-06-08 00: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

Re: [sage-devel] sage infrastructure at UW

On Tue, Jun 7, 2016 at 1:27 PM, 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 >

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

On 2016-06-08 10:32, mmarco wrote: Would it work just to create a temporary directory through the tempfile module? These are datafiles which are meant to be persistent. So I think that ~/.sympow (or $DOT_SAGE/sympow) would be better choices. -- You received this message because you are

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

Would it work just to create a temporary directory through the tempfile module? El miércoles, 8 de junio de 2016, 6:38:34 (UTC+2), François escribió: > > > > On 8/06/2016, at 10:14, William Stein > wrote: > > > > On Tue, Jun 7, 2016 at 6:12 PM, Francois Bissey > >

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

> On 8/06/2016, at 19:52, Jeroen Demeyer wrote: > > On 2016-06-08 00: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 >>>

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

On 2016-06-07 18:04, Nathan Dunfield wrote: Specifically, if you look at the top of a Cython-generated C file, there is what looks to be a JSON string encoding the metadata. Right, although I don't know if this is used by anything. In any case, this might still not be enough since the

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

On 2016-06-08 00: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

[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