[sage-devel] Re: State of Sage Wiki and Support

Thu 2016-09-01 01:45:19 UTC+2, saad khalid wrote on sage-support: > Hey everyone: Hey! Thanks for raising these points. I thought this discussion could get more contributions on sage-devel, so I moved it here. All please reply only on sage-devel to keep the discussion in one place. > It's

[sage-devel] Fwd: State of Sage Wiki and Support

Le jeudi 1 septembre 2016 01:45:19 UTC+2, saad khalid a écrit : > > Hey everyone: > > It's seemed to me lately that the state of the documentation is kinda all > over the place and dated. I've been having increasing trouble recently with > finding the documentation for functions online,

Re: [sage-devel] Jupyter notebook by default?

Nice! That's even better that it works out-of-the-box! Jason On Fri, Sep 9, 2016 at 6:06 PM Volker Braun wrote: > > > > > On Friday, September

Re: [sage-devel] sage -br rebuilds things that were not changed

+1 That would save on time and confusion. On Friday, September 9, 2016 at 3:20:54 PM UTC-7, William wrote: > > On Fri, Sep 9, 2016 at 3:08 PM, Volker Braun > wrote: > > Whenever you switch to a branch with a different working set you change > > timestamps of modified

[sage-devel] Re: 404 in Sage Installation Guide

Paul Masson wrote: > There does not appear to be a "README.txt" file for Windows installation > in either the main SageMath repository or the website repository. If > such a file ever existed, it's long gone. I even checked at archive.org > for a backup copy, but since the robots.txt file has been

Re: [sage-devel] sage -br rebuilds things that were not changed

On Fri, Sep 9, 2016 at 3:08 PM, Volker Braun wrote: > Whenever you switch to a branch with a different working set you change > timestamps of modified files. Git does not track timestamps. Updated > timestamps cause recompilation. So... instead of using timestamps, maybe

Re: [sage-devel] sage -br rebuilds things that were not changed

Whenever you switch to a branch with a different working set you change timestamps of modified files. Git does not track timestamps. Updated timestamps cause recompilation. On Saturday, September 10, 2016 at 12:03:36 AM UTC+2, Paul Masson wrote: > > A little over a week ago I made a new

Re: [sage-devel] sage -br rebuilds things that were not changed

On 2016-09-10 00:03, Paul Masson wrote: Why would recythonizing be necessary when only changing the same file on the same branch? You are not changing just one file. When you checkout a new branch, a lot of files get changed. When you checkout the old branch again, a lot of files get changed

Re: [sage-devel] Jupyter notebook by default?

On Friday, September 9, 2016 at 2:53:29 PM UTC+2, kcrisman wrote: > > Sorry for the necropost, but I couldn't find any other canonical place to > mention this: > >

Re: [sage-devel] sage -br rebuilds things that were not changed

A little over a week ago I made a new branch from 7.4.beta2 for Trac 21370. I initially ran make on this branch. For the last week, I have made changes to one file, graphs/graph_plot.py, for that ticket. For the last week, every time I run sage -b after modifying that one file, the process

Re: [sage-devel] sage -br rebuilds things that were not changed

On 2016-09-09 23:34, Paul Masson wrote: I'm a bit confused by your answer, because I've been seeing the same sort of behavior. For the last week I've been rebuilding a branch based on 7.4.beta2. With minor changes to one file, sage -b has been running very quickly. Today I made one minor change

Re: [sage-devel] sage -br rebuilds things that were not changed

I'm a bit confused by your answer, because I've been seeing the same sort of behavior. For the last week I've been rebuilding a branch based on 7.4.beta2. With minor changes to one file, sage -b has been running very quickly. Today I made one minor change and the recythonizing kicked in. In

[sage-devel] Re: 404 in Sage Installation Guide

There does not appear to be a "README.txt" file for Windows installation in either the main SageMath repository or the website repository. If such a file ever existed, it's long gone. I even checked at archive.org for a backup copy, but since the robots.txt file has been blocking the /mirror/

[sage-devel] Re: 404 in Sage Installation Guide

Fri 2016-09-09 00:16:36 UTC+2, leif: > > The link to README.txt ("Be sure to read the file ..." [!]) > > http://www.sagemath.org/mirror/win/README.txt > > referenced in > > > http://doc.sagemath.org/html/en/installation/binary.html#microsoft-windows > > gives a 404, for whatever reason.

Re: [sage-devel] Re: PYTHONUSERBASE?

On 2016-09-09 18:29, leif wrote: See also https://trac.sagemath.org/ticket/21430 for a very recent, related discussion. No, it's not related at all. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop

[sage-devel] Installing sage as a kernel in the system-wide jupyter

I've found the following quite convenient and I wonder what the best place is to document this better and/or make it more robust: sage.repl.ipython_kernel.install.JUPYTER_PATH=os.environ["HOME"]+"/.ipython" sage.repl.ipython_kernel.install.SageKernelSpec.update() It installs the sage kernel

Re: [sage-devel] sage -br rebuilds things that were not changed

It seems there are some differences that were not showing up when I was checking status. On Saturday, September 10, 2016 at 1:17:31 AM UTC+9, Marco Cognetta wrote: > > One public branch is the trac ticket #21423. I just tested the turning on > and off again and it happened and then failed. It

[sage-devel] Re: PYTHONUSERBASE?

William Stein wrote: > Hi, > > I personally disagree with trying to make Sage's python and the > general environment be as isolated as possibly from each other. We > should try to interoperate with the greater Python world as much as > possible, not change things to discourage that. If you want

Re: [sage-devel] sage -br rebuilds things that were not changed

One public branch is the trac ticket #21423. I just tested the turning on and off again and it happened and then failed. It may be something weird with that branch, but it said it was up to date with the sage repo and I didn't change anything outside of the graph/generators/families.py file.

[sage-devel] Re: sage -br rebuilds things that were not changed

Jeroen Demeyer wrote: > On 2016-09-09 12:56, Marco Cognetta wrote: >> It has happened to me where I build sage, turn off my computer, turn it >> back on, and build it again. There were no changes made in the meantime >> and it still does the cythonizing step. > > Are you really sure that you

[sage-devel] PYTHONUSERBASE?

Hi, I personally disagree with trying to make Sage's python and the general environment be as isolated as possibly from each other. We should try to interoperate with the greater Python world as much as possible, not change things to discourage that. If you want total isolation, use Docker, don't

Re: [sage-devel] Jupyter notebook by default?

> A bit more robust in escaping: > >> >>> Thanks. I don't know enough about the Jupyter nb to know whether there is an easy way to get it to render HTML output - perhaps %%html , which would seem to me to be what is asked for but I don't use it myself. -- You received this message because

[sage-devel] Re: Project: LatticeWithIsometry

Dear Dima, sorry for taking such a long time to answer your question. I'd say it could do a lot of stuff involving over and sublattices. But then it seems like Alex is counting orbits. You'd have to build on top of my code to achieve that. For my purposes it sufficed to consider a single

Re: [sage-devel] Jupyter notebook by default?

A bit more robust in escaping: try: from html import escape # python 3.x except ImportError: from cgi import escape # python 2.x from IPython.display import HTML def table(data): rows = [["%s"%escape(str(i)) for i in data[0]]] rows.extend([["%s"%escape(str(i)) for i in row] for

Re: [sage-devel] Jupyter notebook by default?

I don't think we have a good table-printing function built into IPython. A simple one is probably pretty straightforward: try: from html import escape # python 3.x except ImportError: from cgi import escape # python 2.x from IPython.display import HTML def table(data): rows =

Re: [sage-devel] Jupyter notebook by default?

Sorry for the necropost, but I couldn't find any other canonical place to mention this: https://ask.sagemath.org/question/34782/how-to-render-html-or-latex-tables-in-jupyter-notebook/ Likely this is a fairly easy hook thing or the pretty_print issue but thought it should be here for

[sage-devel] Re: Weekend workshop BIRS: SageMath development related to K3 surfaces (March 2016)

Thank you Frédéric. I wasn't aware of that package. It seems quite interesting. On Thursday, September 8, 2016 at 5:08:32 PM UTC+2, Frédéric Chapoton wrote: > > Maybe the authors/users of the Chow package for sage would be interested ? > Probably not Sorger, who is busy being currently head of

Re: [sage-devel] sage -br rebuilds things that were not changed

On 2016-09-09 12:56, Marco Cognetta wrote: It has happened to me where I build sage, turn off my computer, turn it back on, and build it again. There were no changes made in the meantime and it still does the cythonizing step. Are you really sure that you remember this correctly? Turning off

[sage-devel] Re: What is "do_system"?

Hi Jeroen, hi Leif, On 2016-09-09, Jeroen Demeyer wrote: >>> Obviously yes: >>> >>> #include >>> remove(const char *pathname); >> >> For files, unlink(). > > Depends on what kind of systems you want to support. remove() is C89 > while unlink() is POSIX. Doing this and

Re: [sage-devel] sage -br rebuilds things that were not changed

It has happened to me where I build sage, turn off my computer, turn it back on, and build it again. There were no changes made in the meantime and it still does the cythonizing step. Also, I have had branches that are identical (except for a new file that does not have any dependencies to be

[sage-devel] Re: What is "do_system"?

Hi Jeroen, On 2016-09-09, Jeroen Demeyer wrote: > Depends on what kind of systems you want to support. remove() is C89 > while unlink() is POSIX. Does one of the commands work on all platforms supported by SageMath? If not: What to do to make it work on all platforms?

[sage-devel] Re: What is "do_system"?

Hi Jeroen, On 2016-09-09, Jeroen Demeyer wrote: > On 2016-09-09 08:23, Simon King wrote: >> Is there a cleaner/less costly way to remove a file? > > Obviously yes: > > #include > remove(const char *pathname); Nice, thank you! Cheers, Simon -- You received this

[sage-devel] Re: Poisson algebra module

On Thursday, September 8, 2016 at 5:58:37 PM UTC, Peter Banks wrote: > > > > On Monday, September 5, 2016 at 3:30:53 PM UTC+1, Travis Scrimshaw wrote: > >> >>>- The class KontsevichGraph is a subclass of DiGraph; however, it >>>would only ever be used in calculating the Star product of

Re: [sage-devel] patchbot sage4 fails with permission denied

On 2016-09-09 10:20, Daniel Krenn wrote: On #21204 (with 7.4.beta3) as well as on #21205 (with 7.4.beta4) patchbot Gentoo Base System/2.2/x86_64/3.2.1-gentoo-r2/sage4 fails building with [widgetsnbextension-1.2.6] OSError: [Errno 13] Permission denied: '/home/worker/.jupyter' This is

[sage-devel] patchbot sage4 fails with permission denied

On #21204 (with 7.4.beta3) as well as on #21205 (with 7.4.beta4) patchbot Gentoo Base System/2.2/x86_64/3.2.1-gentoo-r2/sage4 fails building with [widgetsnbextension-1.2.6] OSError: [Errno 13] Permission denied: '/home/worker/.jupyter' -- You received this message because you are

[sage-devel] Re: sage -br rebuilds things that were not changed

Jeroen Demeyer wrote: > On 2016-09-09 08:43, Marco Cognetta wrote: >> However, if I change to a >> new branch that has no changes which would necessitate recythonizing >> code, it will go through the cythonizing step again. > > What makes you think that there are no changes which would

Re: [sage-devel] Re: What is "do_system"?

On 2016-09-09 09:47, leif wrote: Jeroen Demeyer wrote: On 2016-09-09 08:23, Simon King wrote: Is there a cleaner/less costly way to remove a file? Obviously yes: #include remove(const char *pathname); For files, unlink(). Depends on what kind of systems you want to support. remove() is

[sage-devel] Re: What is "do_system"?

Jeroen Demeyer wrote: > On 2016-09-09 08:23, Simon King wrote: >> Is there a cleaner/less costly way to remove a file? > > Obviously yes: > > #include > remove(const char *pathname); For files, unlink(). -leif -- You received this message because you are subscribed to the Google Groups

Re: [sage-devel] Re: What is "do_system"?

On 2016-09-09 08:23, Simon King wrote: Is there a cleaner/less costly way to remove a file? Obviously yes: #include remove(const char *pathname); -- 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 -br rebuilds things that were not changed

On 2016-09-09 08:43, Marco Cognetta wrote: However, if I change to a new branch that has no changes which would necessitate recythonizing code, it will go through the cythonizing step again. What makes you think that there are no changes which would necessitate recythonizing? Cython does

[sage-devel] sage -br rebuilds things that were not changed

Hello, I have been writing some code for sage and have encountered the following problem. When running ./sage -br, it goes through a long cythonizing step every time, even on files that have not been changed. I have played around with it a little and if I run ./sage -br, wait for it to finish

[sage-devel] Re: What is "do_system"?

Hi Leif, On 2016-09-09, leif wrote: > No, it's presumably really (in) the C library function system() [1], in > Python os.system(). (I doubt you abuse it to write to or read from files.) *I* don't. But it seems that the third party code I'm using does. There, I see the