#11162: print warning if no C compiler found
---------------------------+------------------------------------------------
Reporter: jhpalmieri | Owner:
Type: enhancement | Status: needs_info
Priority: minor | Milestone: sage-4.7.2
Component: scripts | Keywords:
Work_issues: | Upstream: N/A
Reviewer: | Author: John Palmieri
Merged: | Dependencies:
---------------------------+------------------------------------------------
Comment(by jhpalmieri):
Okay, so when do we need to print an error?
- when running `sage -ba`
- when running `sage -b` if a Cython file has been modified
- when running `sage --cython ...`
- when running `sage --upgrade ...`
- when running `sage -i ...` or `sage -f ...`
- while running sage, when attaching a pyx or spyx file
- while running the sage notebook, when evaluating a `%cython` block
Anything else?
It seems like it might actually be less intrusive if you print a warning
once, the first time Sage is run, than if you raise an error whenever any
of these are attempted. It also looks more complicated to write a patch
to catch all of the possible cases.
But I don't have a strong opinion about this. I agree with the "minor"
priority for this ticket...
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11162#comment:11>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
