> On Dec 1, 2016, at 15:15 , Volker Braun wrote:
>
> As always, you can get the latest beta version from the "develop" git branch.
> Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
Built from tarball on macOS 10.11.6 w/o problems. Testing
On Fri, Dec 02, 2016 at 03:14:24AM -0800, Emmanuel Charpentier wrote:
[...]
> Dumb dentist's idea : the spkg-install script might *move* the relevant
> file in some appropriate location under SAGE_LIB and symlink it in the
> source tree, thus more or less transparently ensuring availability at
>
Le vendredi 2 décembre 2016 02:06:29 UTC+1, François a écrit :
>
> Can please people stop using files in SAGE_SRC at runtime and people
> stop reviewing such things positively unless there is absolutely no
> choices.
>
Indeed. Reading the rest of the thread so far show that it's important.
B
On Fri, Dec 2, 2016 at 2:06 AM, François Bissey
wrote:
> Can please people stop using files in SAGE_SRC at runtime and people
> stop reviewing such things positively unless there is absolutely no
> choices.
>
> In sage/plot/plot3d/base.pyx we have line 410 and after:
> from sage.env import
On 02/12/16 14:47, Paul Masson wrote:
I see many instances of SAGE_SRC in the source code but not so many of
SAGE_LIB. I'm also not finding any documentation for SAGE_LIB. How are
people supposed to know what is considered the proper use of the two
locations?
How many of the package that you ha
Re-reading your answer again, if you don't want it along side the .py
files you'll have to install it in something like local/share/sage.
You could put it in its own folder under src/ext/ and it would installed
automatically by the current mechanic. But you would have to change
SAGE_SRC to someth
I am testing a patch. Basically you really want the html file
to be installed like the other python files. Then you can use
SAGE_LIB which really is the top level of "site-packages" instead of
SAGE_SRC. This is what I am testing right now
diff --git a/src/sage/plot/plot3d/base.pyx b/src/sage/plot/
François, I'm responsible for this but need more information. It was
recommended by one of my reviewers that I keep an HTML template for
Three.js support separate from the Python code and the template must be
accessible at runtime. For this first version it's sitting in the source
code next to
Can please people stop using files in SAGE_SRC at runtime and people
stop reviewing such things positively unless there is absolutely no
choices.
In sage/plot/plot3d/base.pyx we have line 410 and after:
from sage.env import SAGE_SRC
filename = os.path.join(SAGE_SRC, 'sage',
