[sage-devel] Re: Trying to resume work

Use ssh instead of https: git remote remove trac git remote add trac g...@trac.sagemath.org:sage.git On Saturday, January 16, 2016 at 12:30:43 PM UTC+1, Simon King wrote: > > Hi! > > Recently, I was unable to work for some reasons, one of them being a crash > of my laptop. I now have a new

Re: [sage-devel] Re: Trac - internal error

On Fri, 15 Jan 2016, Volker Braun wrote: The trac vm disk was full again.  df -h | mail -s "Disk usage report" some.addr...@somewhere.net to cron.weekly? Kind of poor man's Nagios, but better than nothing. -- Jori Mäntysalo

Re: [sage-devel] Re: plateform specific implantation

On Fri, Jan 15, 2016 at 03:36:23PM -0800, Travis Scrimshaw wrote: > In the interest of speed, to avoid calls to `sys,platform`, I would make > foo a (module level) @lazy_attribute or @cached_function. IMO a full class > is a lot more than you need. First of all, in my usecase, those are only

Re: [sage-devel] incremental migration to github?

On Saturday, January 16, 2016 at 11:47:25 AM UTC+1, Jeroen Demeyer wrote: > > On 2016-01-16 08:15, Ralf Stephan wrote: > > Another useful thing is that everything on trac is in one git tree. > I > > can do "git fetch" and have all tickets ready to check out without > any > >

Re: [sage-devel] incremental migration to github?

On 2016-01-16 14:29, Ralf Stephan wrote: https://gist.github.com/piscisaureus/3342247 Sorry, but something which involves manually editing config files is not "easily checkout a pull request". But at least it works. -- You received this message because you are subscribed to the Google

[sage-devel] Re: Trying to resume work

Dear Volker, Am Samstag, 16. Januar 2016 13:33:45 UTC+1 schrieb Volker Braun: > > Use ssh instead of https: > > git remote remove trac > git remote add trac g...@trac.sagemath.org:sage.git > > Thanks, it did work! Now there only remains to convince my landlord to enable ssh in the WiFi that he

Re: [sage-devel] incremental migration to github?

On 2016-01-16 08:15, Ralf Stephan wrote: Another useful thing is that everything on trac is in one git tree. I can do "git fetch" and have all tickets ready to check out without any hassle. I don't know if you can easily checkout a pull request from github. Of course you can.

Re: [sage-devel] incremental migration to github?

On Friday, January 15, 2016 at 7:45:23 PM UTC+1, vdelecroix wrote: > > I only see a potential increase of the number of pull > requests. Which would actually be bad since we have a lot of pending tickets. > You're assuming that tickets are still pending only because of the number of tickets.

Re: [sage-devel] incremental migration to github?

On 2016-01-16 08:15, Ralf Stephan wrote: On the other hand you can unsubscribe from each of these branches of conversation. Also, since a new code branch is a separate pull request the old branch stays visible until it's explicitly closed. It's up to you to add # links if you want. Moreover,

Re: [sage-devel] Re: plateform specific implantation

IMHO this is still far from the best way of doing such things - namely, wrap whatever platform-specific you must do with semaphores in a special class, so that the code where they are used does not do any platform-specific things at all. Otherwise platform-specific code would proliferate like

[sage-devel] Re: sagetex failed to build

This answers my question, although the question doesn't match the message I saw. http://doc.sagemath.org/html/en/faq/faq-usage.html#when-i-try-to-use-latex-in-the-notebook-it-says-it-cannot-find-fullpage-sty On Saturday, January 16, 2016 at 12:49:28 PM UTC-8, Buck Evan wrote: > > I'm trying

Re: [sage-devel] forked ppl interface

In the meantime I discovered https://pypi.python.org/pypi/pyparma On 17/01/16 00:49, William Stein wrote: Awesome example!! On Saturday, January 16, 2016, Vincent Delecroix <20100.delecr...@gmail.com> wrote: Hello, For information. I just succeeded in making the interface to PPL as a

Re: [sage-devel] Re: plateform specific implantation

On Saturday, January 16, 2016 at 1:08:08 AM UTC-8, fhivert wrote: > > On Fri, Jan 15, 2016 at 03:36:23PM -0800, Travis Scrimshaw wrote: > > In the interest of speed, to avoid calls to `sys,platform`, I would make > > foo a (module level) @lazy_attribute or @cached_function. IMO a full > class

Re: [sage-devel] forked ppl interface

Awesome example!! On Saturday, January 16, 2016, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > Hello, > > For information. I just succeeded in making the interface to PPL as a > standalone Python package ([1] and [2]). Hopefully there was not much work > needed! It is currently mostly a

[sage-devel] Trying to resume work

Hi! Recently, I was unable to work for some reasons, one of them being a crash of my laptop. I now have a new one, running Ubuntu. When trying git trac pull or just git pull on some ticket, I get the error: fatal: unable to access 'https://trac.sagemath.org/sage.git/': server

[sage-devel] Re: Trying to resume work

I presume your university provides VPN access, which is hopefully not blocked. Thus, first get on VPN, and then you should be able to to do anything, as the traffic will be channeled via VPN. Failing all that, I presume there is a commission that takes care of landlord stupidity, make a

Re: [sage-devel] ask.sagemath.org down?

On Sat, Jan 16, 2016 at 8:39 AM, John H Palmieri wrote: > It looks like ask.sagemath.org is down, and has been for several days. (Or > is it just me?) If it's not just me, can someone restart it? It's just you:

[sage-devel] Re: Error building branch from git clone

Thanks for the replies. I just made a fresh new clone, then checked out the branch, and tried to run make, and got a different error, this time it's: Error installing package mpfr-3.1.2.p0 And now I can't run sage. To be clear, I ran precisely the following commands: annahaensch$ git

Re: [sage-devel] ask.sagemath.org down?

Yes please! Sorry for the trouble. Vincent On 16/01/16 14:05, John H Palmieri wrote: It looks like it's fixed. I guess I should stop posting all of that spam there, then? John On Saturday, January 16, 2016 at 8:47:48 AM UTC-8, vdelecroix wrote: We are experimenting ip bans (because of

[sage-devel] Re: on adding a function to sage: logGamma

sage: log_gamma(x) log_gamma(x) sage: log_gamma(4.0) 1.79175946922805 On Saturday, January 16, 2016 at 7:35:20 PM UTC+1, Buck Evan wrote: > > It would be helpful if I could use the loggamma function with sage, both > in numerical and symbolic form. > > Some references: > > *

[sage-devel] Please review #19843

As usual, nobody reviewed changes to the (re)location error messages. I think its crucial that this goes into Sage 7 which we should get out asap. [ ] I prefer the incorrect error messages [ ] Hold it, I still want to add my pet feature to that ticket -- You received this message because you

[sage-devel] Re: Error building branch from git clone

Are you switching between Sage-6 and Sage-7 based branches? Then you need to recompile everything ("make distclean && make") On Saturday, January 16, 2016 at 5:53:45 PM UTC+1, Anna Haensch wrote: > > Thanks for the replies. I just made a fresh new clone, then checked out > the branch, and

Re: [sage-devel] ask.sagemath.org down?

We are experimenting ip bans (because of spam). I just flush one of the list. Please tell me if it is fixed. On 16/01/16 13:40, William Stein wrote: On Sat, Jan 16, 2016 at 8:39 AM, John H Palmieri wrote: It looks like ask.sagemath.org is down, and has been for

[sage-devel] ask.sagemath.org down?

It looks like ask.sagemath.org is down, and has been for several days. (Or is it just me?) If it's not just me, can someone restart it? -- John -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving

Re: [sage-devel] ask.sagemath.org down?

It looks like it's fixed. I guess I should stop posting all of that spam there, then? John On Saturday, January 16, 2016 at 8:47:48 AM UTC-8, vdelecroix wrote: > > We are experimenting ip bans (because of spam). I just flush one of the > list. Please tell me if it is fixed. > > On 16/01/16

[sage-devel] on adding a function to sage: logGamma

It would be helpful if I could use the loggamma function with sage, both in numerical and symbolic form. Some references: * https://en.wikipedia.org/wiki/Gamma_function#The_log-gamma_function * http://mathworld.wolfram.com/LogGammaFunction.html *

[sage-devel] forked ppl interface

Hello, For information. I just succeeded in making the interface to PPL as a standalone Python package ([1] and [2]). Hopefully there was not much work needed! It is currently mostly a copy/paste of the corresponding file from Sage. Best, Vincent [1] https://github.com/videlec/pplpy

Re: [sage-devel] Re: default "contours" option for implicit_plot

> On 17/01/2016, at 09:57, kcrisman wrote: > > > > Does anyone knows why the default option for “contours” is > set to “(0,0)” in implicit_plot (sage/plot/contour_plot.py line 571-572)? > Instead of being left alone to “None”. > > > I imagine that is what someone set

[sage-devel] sagetex failed to build

I'm trying to compile sage from source, and I'm stuck on this step currently. ``` Compiled with zlib 1.2.8; using zlib 1.2.8 Compiled with poppler version 0.24.5 This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian) restricted \write18 enabled. entering extended mode

[sage-devel] Re: default "contours" option for implicit_plot

> > > > Does anyone knows why the default option for “contours” is > set to “(0,0)” in implicit_plot (sage/plot/contour_plot.py line 571-572)? > Instead of being left alone to “None”. > > I imagine that is what someone set it to long ago either in copying from something else or because it

[sage-devel] Re: on adding a function to sage: logGamma

I apologize. Resolved as "RTFM". On Saturday, January 16, 2016 at 10:46:33 AM UTC-8, Volker Braun wrote: > > sage: log_gamma(x) > log_gamma(x) > sage: log_gamma(4.0) > 1.79175946922805 > > > On Saturday, January 16, 2016 at 7:35:20 PM UTC+1, Buck Evan wrote: >> >> It would be helpful if I could

[sage-devel] Error testing package cython-0.23-3

Should I not attempt to build with testing? I've exported SAGE_CHECK=yes`, which is mentioned in the README and looked like a good idea. The cause seems to be gcc segfaulting during tests of cython compilation. ``` [1/1] Cythonizing

Re: [sage-devel] Error testing package cython-0.23-3

On 2016-01-16 20:15, Buck Evan wrote: The cause seems to be gcc segfaulting during tests of cython compilation. A broken GCC? Let me guess... Debian? You can rebuild Sage with the environment variable SAGE_INSTALL_GCC=yes That will install a properly working GCC. -- You received this message

Re: [sage-devel] Error testing package cython-0.23-3

It passed on subsequent `make`. It's good enough for now, for me. Yes it's a Debian (Ubuntu 14.04.3). On Saturday, January 16, 2016 at 11:41:57 AM UTC-8, Jeroen Demeyer wrote: > > On 2016-01-16 20:15, Buck Evan wrote: > > The cause seems to be gcc segfaulting during tests of cython >

Re: [sage-devel] Re: "Möbius": to 'mobius' or to 'moebius'?

> > > > +1 really do this. > > Last week at the Sage booth at the Joint Mathematics Meetings, I had > the steady depressing stream of complainers come by and say to me "I > switched from Sage back to Mathematica because I upgraded Sage and the > upgrade broke my code." Even deprecations

[sage-devel] How can I know if Jupyter is running?

To adapt to the soon-to-be-default Jupyter notebook in Sage, I’m updating the Mac app to launch either SageNB or Jupyter depending on a preference. Unfortunately, I can’t figure out how to determine if Jupyter is already running at all, let alone in a given directory or on what port. I can

[sage-devel] Re: sagetex failed to build

Notably, avoiding installing the documentation for this package reduces the download size from 400MB(!) to 9MB. sudo apt-get install --no-install-recommends texlive-latex-extra On Saturday, January 16, 2016 at 4:09:54 PM UTC-8, Buck Evan wrote: > > This answers my question, although the

[sage-devel] Re: sagetex failed to build

While that got rid of the previous error, there's something else wrong here: I'm going to assume nobody else compiles with SAGE_CHECK=yes, and I shouldn't either. ``` Plot 3 Plot 4 Code block begin...end Plot 5 Code block begin...sys:1: DeprecationWarning: The use of coeffs() is now deprecated

Re: [sage-devel] How can I know if Jupyter is running?

On Sat, Jan 16, 2016 at 8:53 PM, Ivan Andrus wrote: > To adapt to the soon-to-be-default Jupyter notebook in Sage, I’m updating the > Mac app to launch either SageNB or Jupyter depending on a preference. > Unfortunately, I can’t figure out how to determine if Jupyter is

[sage-devel] Re: sagetex failed to build

Running testsuites has additional dependencies, so using SAGE_CHECK is not for everybody. On Sunday, January 17, 2016 at 1:23:14 AM UTC+1, Buck Evan wrote: > > While that got rid of the previous error, there's something else wrong > here: > > I'm going to assume nobody else compiles with

Re: [sage-devel] Re: plateform specific implantation

> Oops, I misread your code. I'm not used to seeing python code in a class > definition other than defining methods. Sorry. However that clarifies why > you are putting it into a class. Actually, it would have been the same outside a class, with the enclosing module playing the role of the

Re: [sage-devel] Re: plateform specific implantation

On Sat, Jan 16, 2016 at 05:55:01AM -0800, Dima Pasechnik wrote: > IMHO this is still far from the best way of doing such things - namely, > wrap whatever platform-specific you must do with semaphores in a special > class, so that the code where they are used does not do any > platform-specific