doctesting will fail but building is OK, if dangerous if you are not sandboxed
one way or another.
François
> On 8/03/2017, at 18:59, John H Palmieri wrote:
>
> Although it's not a good idea to build Sage as root. I think it is likely to
> fail -- someone please correct me if I'm wrong.
--
Y
Although it's not a good idea to build Sage as root. I think it is likely
to fail -- someone please correct me if I'm wrong.
John
On Tuesday, March 7, 2017 at 6:37:33 PM UTC-8, François wrote:
>
> Not at all. It has to do with sage’s python including this patch
>
> https://github.com/sagema
I've been working on an old ticket, #18138
(https://trac.sagemath.org/ticket/18138), regarding the Mathematica
interface. Here's a quick summary of the ticket:
- Starting with Mathematica 9, the command line front end shipped with
Mathematica no longer works with pexpect.
- The short-t
Not at all. It has to do with sage’s python including this patch
https://github.com/sagemath/sage/blob/master/build/pkgs/python2/patches/sys_path_security-issue_16202.patch
it is something that Dima mentioned earlier in the thread.
François
> On 8/03/2017, at 15:24, Gere Mia wrote:
>
> Does thi
Does this have something to do with my building Sage as root?
On Tuesday, March 7, 2017 at 7:23:40 PM UTC-7, Gere Mia wrote:
>
> Now I get this error regarding installing package pip-8.1.2.p1:
>
>> sys:1: RuntimeWarning: not adding directory '' to sys.path since it's not
>> owned by a trusted use
Now I get this error regarding installing package pip-8.1.2.p1:
> sys:1: RuntimeWarning: not adding directory '' to sys.path since it's not
> owned by a trusted user.
> Untrusted users could put files in this directory which might then be
> imported by your Python code. As a general precaution f
I'm pretty sure src/sage/env.py and version.py is imported during build by
some scripts to figure out directory locations. The ipython_kernel.install
is imported once to install the ipython kernel.
On Tuesday, March 7, 2017 at 7:20:15 PM UTC+1, John H Palmieri wrote:
>
> If I run "make" in Sage,
No, it's not part of Slackware. It's something a made. It probably isn't a
good idea. I didn't know about MAKEOPTS. Putting that in /etc/make.conf
sounds like the proper way of doing it. thanks
On Tuesday, March 7, 2017 at 1:39:11 PM UTC-7, François wrote:
>
> On 08/03/17 09:35, Gere Mia wrote:
On 08/03/17 09:35, Gere Mia wrote:
> Both of you are right. My make is really a bash script/alias for "make
> -j4", so that might have messed things up. I thought I tried using a
> non-"-j" make, and it didn't work, but "MAKE='make -d' ./sage -p
> tachyon" built it successfully. thank you
>
I don
Both of you are right. My make is really a bash script/alias for "make
-j4", so that might have messed things up. I thought I tried using a
non-"-j" make, and it didn't work, but "MAKE='make -d' ./sage -p tachyon"
built it successfully. thank you
--
You received this message because you are su
On Monday, March 6, 2017 at 6:24:15 AM UTC-6, jplab wrote:
>
>
>> Le lundi 6 mars 2017 05:12:29 UTC+1, Travis Scrimshaw a écrit :
>>>
>>> Are you not able to do it by putting the tikz code in a .. MATH:: block?
>>>
>>>
>> Haven't tried! Will do!
>>
>
> Actually, after a second thought, I do not
If I run "make" in Sage, it creates some *.pyc files in src/sage:
$ find src/sage -name "*.pyc" -print
./__init__.pyc
./env.pyc
./misc/__init__.pyc
./misc/lazy_import_cache.pyc
./misc/package.pyc
./repl/__init__.pyc
./repl/ipython_kernel/__init__.pyc
./repl/ipython_kernel/install.pyc
./version.pyc
Dear Sage developers,
This is a reminder about the approaching deadline for the CICM
conference (March 15: abstracts; March 22: final submission). I
attended this conference last year, and enjoyed it very much (see my
blog post [1]). It's a natural location for exposing and advertising
som
Hi all,
The first official Jupyter conference will be held on August 22-25th 2017
in New York City.
If you have an intriguing case study, deep technical knowledge to share
about Jupyter's internals, a useful extension, or a provocative idea for
new development, we'd love to hear from you.
The
Apart from a possible unusual version of make could you
try
MAKE=“make -d” ./sage -p tachyon
That will generate a lot of output but there could be a clue
as to why it tries to go in a folder - which is totally abnormal.
François
> On 7/03/2017, at 06:35, Gere Mia wrote:
>
> I get this build e
Just a guess: do you have a broken/unusual version of Make?
I would suggest to try upgrading to the latest version of GNU Make and
try again.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emai
16 matches
Mail list logo
