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

On Friday, January 15, 2016 at 7:45:23 PM UTC+1, vdelecroix wrote: > > And I agreed with something in the post: just > pay attention to people who are clearly willing to do the job. > Right. No one in this thread has even looked at the original questions, apparently. I was explicitly not proposin

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

On Monday, January 11, 2016 at 8:25:32 PM UTC+1, Jeroen Demeyer wrote: > > What I mostly dislike about github is that "issues" and "pull requests" > are different things. I very much prefer the trac model where you create > a ticket, discuss things, then have multiple people work together on a >

[sage-devel] Re: plateform specific implantation

On Friday, January 15, 2016 at 3:36:24 PM UTC-8, 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. > > According to https://docs.python.or

[sage-devel] Re: plateform specific implantation

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. Best, Travis On Friday, January 15, 2016 at 8:49:40 AM UTC-8, Volker Braun wrote: > > THats fine (except that you sho

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

Hi, 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”. The value “(0,0)” causes a lot of doctest failures when moving from matplotlib 1.5 to 1.5.1 (not yet a ticket for that, s

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

On 15/01/16 15:29, William Stein wrote: On Friday, January 15, 2016, Jeroen Demeyer wrote: On 2016-01-15 16:00, William Stein wrote: Why Python moved to github: http://www.snarky.ca/the-history-behind-the-decision-to-move-python-to-github < http://www.snarky.ca/the-history-behind-the-decis

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

On Friday, January 15, 2016, Jeroen Demeyer wrote: > On 2016-01-15 16:00, William Stein wrote: > >> Why Python moved to github: >> >> >> http://www.snarky.ca/the-history-behind-the-decision-to-move-python-to-github >> < >> http://www.snarky.ca/the-history-behind-the-decision-to-move-python-to-git

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

On 2016-01-15 16:00, William Stein wrote: Why Python moved to github: http://www.snarky.ca/the-history-behind-the-decision-to-move-python-to-github It seems to boil down to "we use GitHub because everybody use

[sage-devel] Re: plateform specific implantation

THats fine (except that you should use new-style classes) On Friday, January 15, 2016 at 5:34:35 PM UTC+1, fhivert wrote: > > Dear all, > > I'd like to have a class with a method with some implementation internal > that > differ if the os is MacOS of anything else. > > Context > ===

[sage-devel] plateform specific implantation

Dear all, I'd like to have a class with a method with some implementation internal that differ if the os is MacOS of anything else. Context === I'm Fixing #13580 "Parallel map reduce on SearchForest" where I'm writing code to parallelize some specific computation. In the internal, I ne

[sage-devel] Re: Trac - internal error

The trac vm disk was full again. Some of the apache2 logs weren't named *.log so logrotate wouldn't actually rotate them. I changed them to all end in .log Also, I reduced logrotate from 52 down to 10 (weeks worth) to prevent this in the future. On Friday, January 15, 2016 at 3:37:58 PM UTC

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

Same here: http://trac.sagemath.org/ticket/19667 S. * Johan S. R. Nielsen [2016-01-15 16:40:37]: > Same thing here, #19251. > > Johan > > david.lu...@inria.fr writes: > > > Hello, > > > > Same thing with some of tickets: #19653, #19666, #19722, #19422 and #19623 > > > > David > > > > Le vend

[sage-devel] Re: Trac - internal error

Same thing here, #19251. Johan david.lu...@inria.fr writes: > Hello, > > Same thing with some of tickets: #19653, #19666, #19722, #19422 and #19623 > > David > > Le vendredi 15 janvier 2016 15:37:58 UTC+1, Clemens Heuberger a écrit : >> >> Trac detected an internal error: >> >> OSError: [Errno

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

Why Python moved to github: http://www.snarky.ca/the-history-behind-the-decision-to-move-python-to-github On Monday, January 11, 2016, William Stein wrote: > On Mon, Jan 11, 2016 at 11:39 AM, Volker Braun > w

[sage-devel] Re: Trac - internal error

Hello, Same thing with some of tickets: #19653, #19666, #19722, #19422 and #19623 David Le vendredi 15 janvier 2016 15:37:58 UTC+1, Clemens Heuberger a écrit : > > Trac detected an internal error: > > OSError: [Errno 2] No such file or directory: '/tmp/tmp7BmVNV' > > The action that triggered

[sage-devel] Trac - internal error

Trac detected an internal error: OSError: [Errno 2] No such file or directory: '/tmp/tmp7BmVNV' The action that triggered the error was: GET: /ticket/19306 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop

[sage-devel] multi-user jupyter(hub)

If you want to play around with jupyterhub but are scared by the dependencies, I wrote a script to bootstrap it locally (no silly global installations of npm packages): https://github.com/vbraun/run-jupyter-hub Run JupyterHub / Jupyter Self-contained dependencies for