#18428: Error checking in sage-spkg
-------------------------------------+-------------------------------------
Reporter: vbraun | Owner:
Type: defect | Status: needs_work
Priority: major | Milestone: sage-6.7
Component: build | Resolution:
Keywords: | Merged in:
Authors: Volker Braun | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/vbraun/error_checking_in_sage_spkg|
c8c260165d07b8a07d61698241f705e9f4a53fcd
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by vbraun):
The problem with buffering is that network connections might take a while,
and the last message on the screen should be flushed to indicate what we
are doing. `PYTHONUNBUFFERED` only makes Python stdin/out unbuffered, and
we don't print() that much. So I don't see where there could be a
performance impact. Even in the worst case (passing the entire build log
through Python unbuffered, which we don't do) its unlikely to take a long
time compared to actually producing the build log.
The first INFO branch is about checking whether the tarball is already
downloaded, which is now done by sage-download file. The second INFO
branch is just printing logs, and I moved that to the relevant place.
--
Ticket URL: <http://trac.sagemath.org/ticket/18428#comment:9>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
