On 2011-11-26 17:07, William Stein wrote:
> Alternative:
> ln -s sage-sage sage
> (or a 1 liner script with a comment)
Fine for me and probably even a better solution. And create that
symbolic link during installation of sage_scripts.
--
To post to this group, send an email to sage-devel@goo
On Nov 26, 2011 2:30 AM, "Jeroen Demeyer" wrote:
>
> Proposal:
>
> 1) In sage-env, do not add $SAGE_ROOT to the $PATH.
> 2) Rename local/bin/sage-sage to local/bin/sage
>
Alternative:
ln -s sage-sage sage
(or a 1 liner script with a comment)
Advantages:
. People and patches don't have to
Solved by using r""" instead of """
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sage
Proposal:
1) In sage-env, do not add $SAGE_ROOT to the $PATH.
2) Rename local/bin/sage-sage to local/bin/sage
Reason:
The python 2.7.2 package checks whether hg is available and runs hg
during the build process. Now imagine you have a system-wide Sage
install. Then hg is found in /usr/local/bi
