[sage-devel] Re: manifolds.utilities.py: ExpressionNice()

[Richard_L]

Thank you. I missed that in the examples. Is there documentation listing 
all Manifold.options? I cannot find one with the documentation search. 

On Saturday, November 18, 2017 at 3:40:41 PM UTC-8, Eric Gourgoulhon wrote:
>
> HI,
>
> Le samedi 18 novembre 2017 23:55:35 UTC+1, Richard_L a écrit :
>>
>> Applying ExpressionNice() to an expression containing partial derivatives 
>> cleans up the presentation, suppressing the display of function arguments 
>> in the partial derivatives. However, zeroth order derivatives (i.e., the 
>> function alone) are not cleaned up. 
>> I think it would be useful to extend the cleanup to zeroth order. 
>>
>
> This is not by default, but you can have it: it suffices to type
>
> Manifold.options.omit_function_arguments=True
>
> cf. the documentation at 
> http://doc.sagemath.org/html/en/reference/manifolds/sage/manifolds/utilities.html
>
> Best wishes,
>
> Eric.
>
>

-- 
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 email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] ask.sagemath

[kcrisman]

On Saturday, November 18, 2017 at 5:52:13 PM UTC-5, Samuel Lelievre wrote:
>
> The conclusion from Erik Bray's issue report seems to be that if a user
> posts an answers containing a url but this user's karma is less than the
> threshold to post links, then the answer is blocked from being submitted.
> Instead, shouldn't it be added to the moderation queue? Or would that
> make the moderation queue explode? Are such events logged, so we
> get an idea of how many such post submissions are blocked?
>

I think it would not add appreciably to the moderation queue.  If Safari 
hadn't removed RSS support (for a second time) I'd be moderating like 
crazy, but now I have to remember. 

-- 
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 email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: manifolds.utilities.py: ExpressionNice()

[Eric Gourgoulhon]

HI,

Le samedi 18 novembre 2017 23:55:35 UTC+1, Richard_L a écrit :
>
> Applying ExpressionNice() to an expression containing partial derivatives 
> cleans up the presentation, suppressing the display of function arguments 
> in the partial derivatives. However, zeroth order derivatives (i.e., the 
> function alone) are not cleaned up. 
> I think it would be useful to extend the cleanup to zeroth order. 
>

This is not by default, but you can have it: it suffices to type

Manifold.options.omit_function_arguments=True

cf. the documentation at 
http://doc.sagemath.org/html/en/reference/manifolds/sage/manifolds/utilities.html

Best wishes,

Eric.

-- 
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 email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] manifolds.utilities.py: ExpressionNice()

[Richard_L]

Applying ExpressionNice() to an expression containing partial derivatives 
cleans up the presentation, suppressing the display of function arguments 
in the partial derivatives. However, zeroth order derivatives (i.e., the 
function alone) are not cleaned up. 
I think it would be useful to extend the cleanup to zeroth order. Other 
opinions?

-- 
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 email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


long_expr
Description: Binary data

Re: [sage-devel] ask.sagemath

[Samuel Lelievre]

The conclusion from Erik Bray's issue report seems to be that if a user
posts an answers containing a url but this user's karma is less than the
threshold to post links, then the answer is blocked from being submitted.
Instead, shouldn't it be added to the moderation queue? Or would that
make the moderation queue explode? Are such events logged, so we
get an idea of how many such post submissions are blocked?

-- 
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 email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] mpir-3.0.0 on skylake (OSX only?) problem, see and review #24085

[Dima Pasechnik]

I've made #24085 a blocker, as people reporting the same issue on 8.1.rc2.
Could please people suffering from this bug please test
https://trac.sagemath.org/ticket/24085 and say here or on the ticket 
whether this does
the job? (Review the ticket too, naturally).

-- 
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 email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Sage 8.0 Build Error on MacOS, [mpir-3.0.0.p0] Error building MPIR.

[Dima Pasechnik]

On Saturday, November 18, 2017 at 8:42:48 PM UTC, Michael Frey wrote:
>
> This is still broken ins Sage 8.1.rc2 with the same error.  Should I post 
> a new thread?
>

please try the branch on https://trac.sagemath.org/ticket/24085 

-- 
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 email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Build of Sage 8.0 from Source failed on OpenSuse Tumbleweed (gcc-5.4.0 build failed)

[François Bissey]

8.1 will have gcc 7.2.0.

> On 19/11/2017, at 11:15, foolish...@gmail.com wrote:
> 
> Based on the error message and a bit of a search, I think it may be related 
> to https://gcc.gnu.org/viewcvs/gcc?view=revision=249731, which 
> states:
> "Use ucontext_t not struct ucontext in linux-unwind.h files.
> Current glibc no longer gives the ucontext_t type the tag struct
> ucontext, to conform with POSIX namespace rules."
> 
> The fixes that spring to mind are upgrading to a recent gcc release (assuming 
> gcc has a fix) or patching the sage -installed gcc-5.4.0 version. 
> 
> Is this a known issue with a fix?  If not, I'd need a bit of education on how 
> to try to test and submit a patch.
> 
> With best regards:
> 
> Billl 
> 
> On Saturday, November 18, 2017 at 2:04:43 PM UTC-8, fooli...@gmail.com wrote:
> 
> Hello All:
> 
> I have a fairly new laptop and am using OpenSuse Tumbleweed (bleeding edge 
> version) to get an appropriate kernel for device support reasons, gcc-5.4.0 
> failed to build, could a very new g++/gcc compiler be the cause?  In any 
> case, please find the indicted gcc-5.4.0.log attached.
> 
> ~/tools/sage-8.0> gcc --version
> gcc (SUSE Linux) 7.2.1 20171020 [gcc-7-branch revision 253932]
> Copyright (C) 2017 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> ~/tools/sage-8.0> g++ --version
> g++ (SUSE Linux) 7.2.1 20171020 [gcc-7-branch revision 253932]
> Copyright (C) 2017 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> When I tried to build my sage 8.0 on it and got the following message:
> 
> /home/FoolishEwe/tools/var/tmp/sage/build/gcc-5.4.0/gcc-build/./gcc/xgcc 
> -B/home/FoolishEwe/tools/var/tmp/sage/build/gcc-5.4.0/gcc-build/./gcc/ 
> -B/home/FoolishEwe/tools/x86_64-unknown-linux-gnu/bin/ 
> -B/home/FoolishEwe/tools/x86_64-unknown-linux-gnu/lib/ -isystem 
> /home/FoolishEwe/tools/x86_64-unknown-linux-gnu/include -isystem 
> /home/FoolishEwe/tools/x86_64-unknown-linux-gnu/sys-include-g -O2 -O2  -g 
> -O2 -DIN_GCC-W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual 
> -Wno-format -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  
> -isystem ./include   -fpic -mlong-double-80 -g -DIN_LIBGCC2 -fbuilding-libgcc 
> -fno-stack-protector   -fpic -mlong-double-80 -I. -I. -I../.././gcc 
> -I../../../src/libgcc -I../../../src/libgcc/. -I../../../src/libgcc/../gcc 
> -I../../../src/libgcc/../include -I../../../src/libgcc/config/libbid 
> -DENABLE_DECIMAL_BID_FORMAT -DHAVE_CC_TLS  -DUSE_TLS -o unwind-c.o -MT 
> unwind-c.o -MD -MP -MF unwind-c.dep -fexceptions -c 
> ../../../src/libgcc/unwind-c.c -fvisibility=hidden -DHIDE_EXPORTS
> In file included from ../../../src/libgcc/unwind-dw2.c:401:0:
> ./md-unwind-support.h: In function 'x86_64_fallback_frame_state':
> ./md-unwind-support.h:65:47: error: dereferencing pointer to incomplete type 
> 'struct ucontext'
>sc = (struct sigcontext *) (void *) _->uc_mcontext;
>^
> /home/FoolishEwe/tools/var/tmp/sage/build/gcc-5.4.0/gcc-build/./gcc/xgcc 
> -B/home/FoolishEwe/tools/var/tmp/sage/build/gcc-5.4.0/gcc-build/./gcc/ 
> -B/home/FoolishEwe/tools/x86_64-unknown-linux-gnu/bin/ 
> -B/home/FoolishEwe/tools/x86_64-unknown-linux-gnu/lib/ -isystem 
> /home/FoolishEwe/tools/x86_64-unknown-linux-gnu/include -isystem 
> /home/FoolishEwe/tools/x86_64-unknown-linux-gnu/sys-include-g -O2 -O2  -g 
> -O2 -DIN_GCC-W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual 
> -Wno-format -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  
> -isystem ./include   -fpic -mlong-double-80 -g -DIN_LIBGCC2 -fbuilding-libgcc 
> -fno-stack-protector   -fpic -mlong-double-80 -I. -I. -I../.././gcc 
> -I../../../src/libgcc -I../../../src/libgcc/. -I../../../src/libgcc/../gcc 
> -I../../../src/libgcc/../include -I../../../src/libgcc/config/libbid 
> -DENABLE_DECIMAL_BID_FORMAT -DHAVE_CC_TLS  -DUSE_TLS -o emutls.o -MT emutls.o 
> -MD -MP -MF emutls.dep -fexceptions -c ../../../src/libgcc/emutls.c 
> -fvisibility=hidden -DHIDE_EXPORTS
> make[6]: *** [../../../src/libgcc/shared-object.mk:14: unwind-dw2.o] Error 1
> make[6]: *** Waiting for unfinished jobs
> make[6]: Leaving directory 
> '/home/FoolishEwe/tools/var/tmp/sage/build/gcc-5.4.0/gcc-build/x86_64-unknown-linux-gnu/libgcc'
> make[5]: *** [Makefile:15842: all-stage1-target-libgcc] Error 2
> make[5]: Leaving directory 
> '/home/FoolishEwe/tools/var/tmp/sage/build/gcc-5.4.0/gcc-build'
> make[4]: *** [Makefile:19705: stage1-bubble] Error 2
> make[4]: Leaving directory 
> '/home/FoolishEwe/tools/var/tmp/sage/build/gcc-5.4.0/gcc-build'
> make[3]: *** [Makefile:902: all] Error 2
> make[3]: Leaving directory 
> 

Re: [sage-devel] Build of Sage 8.0 from Source failed on OpenSuse Tumbleweed (gcc-5.4.0 build failed)

[François Bissey]

Why is sage trying to build gcc-5.4.0 when you have 7.2.1? Are you missing 
gfortran?
Building an older version of gcc with a newer one like this usually leads to 
trouble.

François

> On 19/11/2017, at 08:23, foolish...@gmail.com wrote:
> 
> 
> Hello All:
> 
> I have a fairly new laptop and am using OpenSuse Tumbleweed (bleeding edge 
> version) to get an appropriate kernel for device support reasons, gcc-5.4.0 
> failed to build, could a very new g++/gcc compiler be the cause?  In any 
> case, please find the indicted gcc-5.4.0.log attached.
> 
> ~/tools/sage-8.0> gcc --version
> gcc (SUSE Linux) 7.2.1 20171020 [gcc-7-branch revision 253932]
> Copyright (C) 2017 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> ~/tools/sage-8.0> g++ --version
> g++ (SUSE Linux) 7.2.1 20171020 [gcc-7-branch revision 253932]
> Copyright (C) 2017 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> When I tried to build my sage 8.0 on it and got the following message:
> 
> /home/FoolishEwe/tools/var/tmp/sage/build/gcc-5.4.0/gcc-build/./gcc/xgcc 
> -B/home/FoolishEwe/tools/var/tmp/sage/build/gcc-5.4.0/gcc-build/./gcc/ 
> -B/home/FoolishEwe/tools/x86_64-unknown-linux-gnu/bin/ 
> -B/home/FoolishEwe/tools/x86_64-unknown-linux-gnu/lib/ -isystem 
> /home/FoolishEwe/tools/x86_64-unknown-linux-gnu/include -isystem 
> /home/FoolishEwe/tools/x86_64-unknown-linux-gnu/sys-include-g -O2 -O2  -g 
> -O2 -DIN_GCC-W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual 
> -Wno-format -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  
> -isystem ./include   -fpic -mlong-double-80 -g -DIN_LIBGCC2 -fbuilding-libgcc 
> -fno-stack-protector   -fpic -mlong-double-80 -I. -I. -I../.././gcc 
> -I../../../src/libgcc -I../../../src/libgcc/. -I../../../src/libgcc/../gcc 
> -I../../../src/libgcc/../include -I../../../src/libgcc/config/libbid 
> -DENABLE_DECIMAL_BID_FORMAT -DHAVE_CC_TLS  -DUSE_TLS -o unwind-c.o -MT 
> unwind-c.o -MD -MP -MF unwind-c.dep -fexceptions -c 
> ../../../src/libgcc/unwind-c.c -fvisibility=hidden -DHIDE_EXPORTS
> In file included from ../../../src/libgcc/unwind-dw2.c:401:0:
> ./md-unwind-support.h: In function 'x86_64_fallback_frame_state':
> ./md-unwind-support.h:65:47: error: dereferencing pointer to incomplete type 
> 'struct ucontext'
>sc = (struct sigcontext *) (void *) _->uc_mcontext;
>^
> /home/FoolishEwe/tools/var/tmp/sage/build/gcc-5.4.0/gcc-build/./gcc/xgcc 
> -B/home/FoolishEwe/tools/var/tmp/sage/build/gcc-5.4.0/gcc-build/./gcc/ 
> -B/home/FoolishEwe/tools/x86_64-unknown-linux-gnu/bin/ 
> -B/home/FoolishEwe/tools/x86_64-unknown-linux-gnu/lib/ -isystem 
> /home/FoolishEwe/tools/x86_64-unknown-linux-gnu/include -isystem 
> /home/FoolishEwe/tools/x86_64-unknown-linux-gnu/sys-include-g -O2 -O2  -g 
> -O2 -DIN_GCC-W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual 
> -Wno-format -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  
> -isystem ./include   -fpic -mlong-double-80 -g -DIN_LIBGCC2 -fbuilding-libgcc 
> -fno-stack-protector   -fpic -mlong-double-80 -I. -I. -I../.././gcc 
> -I../../../src/libgcc -I../../../src/libgcc/. -I../../../src/libgcc/../gcc 
> -I../../../src/libgcc/../include -I../../../src/libgcc/config/libbid 
> -DENABLE_DECIMAL_BID_FORMAT -DHAVE_CC_TLS  -DUSE_TLS -o emutls.o -MT emutls.o 
> -MD -MP -MF emutls.dep -fexceptions -c ../../../src/libgcc/emutls.c 
> -fvisibility=hidden -DHIDE_EXPORTS
> make[6]: *** [../../../src/libgcc/shared-object.mk:14: unwind-dw2.o] Error 1
> make[6]: *** Waiting for unfinished jobs
> make[6]: Leaving directory 
> '/home/FoolishEwe/tools/var/tmp/sage/build/gcc-5.4.0/gcc-build/x86_64-unknown-linux-gnu/libgcc'
> make[5]: *** [Makefile:15842: all-stage1-target-libgcc] Error 2
> make[5]: Leaving directory 
> '/home/FoolishEwe/tools/var/tmp/sage/build/gcc-5.4.0/gcc-build'
> make[4]: *** [Makefile:19705: stage1-bubble] Error 2
> make[4]: Leaving directory 
> '/home/FoolishEwe/tools/var/tmp/sage/build/gcc-5.4.0/gcc-build'
> make[3]: *** [Makefile:902: all] Error 2
> make[3]: Leaving directory 
> '/home/FoolishEwe/tools/var/tmp/sage/build/gcc-5.4.0/gcc-build'
> 
> real6m53.989s
> user36m54.370s
> sys3m22.096s
> 
> Error installing package gcc-5.4.0
> 
> Please email sage-devel (http://groups.google.com/group/sage-devel)
> explaining the problem and including the log file
>   /home/FoolishEwe/tools/sage-8.0/logs/pkgs/gcc-5.4.0.log
> Describe your computer, operating system, etc.
> If you want to try to fix the problem yourself, *don't* just cd to
> 

Re: [sage-devel] Re: Sage 8.0 Build Error on MacOS, [mpir-3.0.0.p0] Error building MPIR.

[Michael Frey]

This is still broken ins Sage 8.1.rc2 with the same error.  Should I post a 
new thread?

-- 
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 email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Patchbot and its trust issues

[Vincent Delecroix]

On 16/11/2017 11:32, Erik Bray wrote:

On Wed, Nov 15, 2017 at 10:00 AM, David Loeffler
 wrote:

I'd like to request opinions on whether we should get rid of the "Trusted
Authors" check in the Sage patchbot.

At present, the patchbot won't test a ticket unless all of the names in the
Trac "Authors" field have had at least one ticket previously merged.
Presumably the intention of this is to prevent people uploading git branches
with malicious code that will hijack the patchbot servers. But the "Authors"
field is a free text field; there's nothing to stop anybody with a trac
account uploading a git branch with author set to "William Stein", or
"Mickey Mouse" for that matter. So this feature provides zero actual
security against attacks, and only serves to make life more difficult for
legitimate users -- and, worse still, it specifically targets new
contributors who we want at all costs to encourage.

So I would advocate getting rid of the "Trust" feature -- or at least
adjusting it so it runs the ticket if any of the authors are trusted (rather
than all of them). What do others here think of this idea?

(I spotted this while reviewing ticket 19169, where the authors are a group
of first-time Sage contributors from Sage Days 69 in 2015. The ticket has
been languishing in needs-review purgatory for most of the intervening 2
years, and the fact that it didn't have a green light from the patchbot
probably contributed to that.)


+1 please consider opening an issue at https://github.com/sagemath/sage-patchbot


Indeed.


I believe it's already possible to configure a patchbot to allow
"untrusted" authors, but it's not the default.  You're right that the
"feature" makes no sense.


Not exactly. You can have a custom "white list".


The only way to run a patchbot anything remotely "securely" is to be
running it on an isolated VM.  A lot of the other defaults for the
patchbot (such as not testing package updates) are similarly false
security, as we discussed here a few days ago.


The real problem is that the patchbot would have to find the tarball! We 
do not have a canonical place for them.


--
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 email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Is the sage tree moveable or sessile ?

[Emmanuel Charpentier]

Thank you, Jeroen. This will be corrected.

--
Emmanuel Charpentier

Le samedi 18 novembre 2017 09:54:01 UTC+1, Jeroen Demeyer a écrit :
>
> On 2017-11-18 09:22, Emmanuel Charpentier wrote: 
> > You *should* be able to move the sage-x.y.z/ directory anywhere you 
> > want. If you copy the sage script or make a symbolic link to it, you 
> > should modify the script to reflect this (as instructed at the top 
> of 
> > the script). It is best if the path to Sage does not have any spaces 
> in 
> > it. 
>
> This is no longer true. 
>

-- 
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 email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Is the sage tree moveable or sessile ?

[Jeroen Demeyer]

On 2017-11-18 09:22, Emmanuel Charpentier wrote:

You *should* be able to move the sage-x.y.z/ directory anywhere you
want. If you copy the sage script or make a symbolic link to it, you
should modify the script to reflect this (as instructed at the top of
the script). It is best if the path to Sage does not have any spaces in
it.


This is no longer true.

--
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 email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Is the sage tree moveable or sessile ?

[Emmanuel Charpentier]

I sem to remember that the Sage tree can (or, at least, should) no longer 
be moved after building.

However, we still document the relocation of this tree in the README.md 
fike :

You *should* be able to move the sage-x.y.z/ directory anywhere you  
want. If you copy the sage script or make a symbolic link to it, you  
should modify the script to reflect this (as instructed at the top of  
the script). It is best if the path to Sage does not have any spaces in  
it.


Being in the process of revising the installation docs (re :Trac#24107 
), I wonder if we should keep this 
paragraph, which is a misdirection if the Sage tree is now sessile...

Advice ?

--
Emmanuel Charpentier

-- 
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 email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.